Few things are more irritating than a driver installer that refuses to install. You downloaded the right file, double-clicked, and were rewarded with “NVIDIA Installer cannot continue” and a dead-end dialog. On Windows 11 24H2 this error has gotten more common: the OS build checks are stricter, Windows Update loves to install its own display driver at the worst moment, and laptop GPUs with custom device IDs trip the installer’s hardware validation.

The key insight is that “cannot continue” is not one error — it’s the installer’s way of saying a precondition failed. The message is deliberately vague: NVIDIA lumps a dozen different precondition failures into one dialog, so treat this guide as a checklist of blockages to clear rather than a single error to decode. The usual suspects: leftover debris from a previous install, the wrong package variant (desktop vs. notebook), Windows Update holding the device lock, or an OEM-blocked GPU that needs the laptop vendor’s driver. We’ll clear them in order of likelihood, and by the end the installer will have nothing left to complain about. Once it installs cleanly, consider doing future updates as a proper clean install of NVIDIA drivers to avoid repeat failures — and if the driver installs but then crashes, the display driver TDR guide is the next step.

Why this happens

  • Leftover files from a previous install. A half-removed driver — registry keys, INF cache entries, stray DLLs — makes the new installer fail its consistency checks.
  • Wrong package variant. The desktop GeForce driver doesn’t include every mobile GPU device ID; laptop chips need the Notebook variant or the vendor’s package.
  • Windows Update is installing a driver simultaneously. The OS holds a device lock while its own driver install runs, and the NVIDIA installer aborts instead of waiting.
  • The GPU is OEM-locked. Some laptop vendors restrict their GPUs to vendor-signed driver packages; the generic NVIDIA installer detects the lock and refuses.
  • Corrupted download. A truncated or corrupted installer package fails integrity checks that surface as the generic “cannot continue” message.
  • Antivirus or controlled folder interference. Security software can block the installer from writing driver files or registry keys mid-installation.
  • The 24H2 build isn’t recognized. Very new 24H2 cumulative builds can briefly outrun the installer’s OS compatibility table until NVIDIA publishes an updated package.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Download the exact right package

Half of these failures are the wrong file.

  1. Go to the NVIDIA driver download page and select GeForce, your exact GPU series, Notebook (not desktop) as the product type, and Windows 11 as the OS.
  2. Compare the file size with the listed size after downloading — a short file means a truncated download; re-download on a stable connection.
  3. Right-click the installer > Run as administrator.
  4. If it still fails, note the exact failure point — we’ll use DDU next.
  5. If the download page doesn’t list your GPU at all, your chip may be an OEM-only variant with a custom device ID — skip straight to Fix 4 and use the laptop vendor’s driver, which is guaranteed to include it.

Fix 2: Clean out the old driver with DDU

Remove the debris the installer is choking on.

  1. Download DDU (Display Driver Uninstaller) and the new NVIDIA package before you start.
  2. Boot into Safe Mode (Settings > System > Recovery > Advanced startup > Troubleshoot > Startup Settings).
  3. Run DDU, select GPU / NVIDIA, and choose Clean and restart.
  4. After reboot, immediately run the NVIDIA installer as administrator before Windows Update can install its own driver.

Fix 3: Stop Windows Update from interfering

Break the device lock.

  1. Go to Settings > Windows Update and Pause updates for a week.
  2. Disconnect from Wi-Fi/Ethernet during the install so Windows can’t fetch a driver mid-process.
  3. Open Device Manager and confirm the display adapter isn’t mid-install (no progress indicators, no warning icons actively changing).
  4. Run the installer again. Reconnect and unpause updates after it succeeds.

Fix 4: Try the laptop vendor’s driver

For OEM-locked mobile GPUs, the vendor package is the answer.

  1. Go to your laptop maker’s support page — Dell Support , HP’s support site, or Lenovo Support — and find the NVIDIA driver for your exact model.
  2. Uninstall the current NVIDIA driver via Settings > Apps > Installed apps first.
  3. Install the vendor’s package; it carries the OEM signature and device IDs the generic installer lacks.
  4. Once stable, you can usually move back to NVIDIA’s notebook drivers for future updates.
  5. If the vendor’s package is several versions behind NVIDIA’s current release, install it anyway to confirm the installer path works — you can then update to the newer NVIDIA notebook driver using the clean install method.

Fix 5: Disable antivirus and controlled folder access temporarily

Rule out security software blocking the install.

  1. Temporarily disable third-party antivirus (or Windows Security’s real-time protection) for the duration of the install.
  2. Check Windows Security > Virus & threat protection > Ransomware protection — turn off Controlled folder access temporarily if it’s on.
  3. Run the installer as administrator again.
  4. Re-enable everything immediately after the install completes.

Fix 6: Install via Device Manager with extracted files

Bypass the installer’s precondition checks entirely.

  1. Run the NVIDIA installer until it extracts (or use 7-Zip to extract the .exe) — find the extracted folder, usually under C:\NVIDIA\DisplayDriver\.
  2. In Device Manager, right-click your display adapter > Update driver > Browse my computer for drivers.
  3. Point it at the extracted folder’s Display.Driver subfolder and install.
  4. This method skips the wrapper’s hardware/OS checks and installs the .inf directly — it works when the wrapper is the problem, not the driver.

Closing

“NVIDIA Installer cannot continue” is the installer telling you something else is in the way — wrong package, leftover debris, a Windows Update lock, or an OEM restriction. Clear those preconditions and the installer stops complaining. And once you’re running again, make clean installs your habit: they’re the single best prevention for installer failures on the next driver update.

Frequently asked questions

What does 'NVIDIA Installer cannot continue' actually mean?
It’s the installer’s generic failure message when a pre-installation check fails — most commonly that the driver package doesn’t recognize your GPU or OS build, that a previous driver installation is in a broken half-installed state, or that Windows’ own driver installation is locking the device. The message hides the specific cause, so the fix is to remove the blockage: clean out the old driver with DDU, download the exact right package, and reinstall.
Why won't the NVIDIA installer recognize my laptop's GPU?
Laptop GPUs often use custom device IDs that the standard desktop driver package doesn’t list, which is why NVIDIA’s installer sometimes rejects mobile chips — especially on newer 24H2 builds. The fix is to download the Notebook (laptop) driver variant from the NVIDIA driver download page rather than the desktop one, or use the driver from your laptop vendor, whose package is guaranteed to include your GPU’s ID.
Is it safe to use DDU to remove NVIDIA drivers?
Yes, when used as directed: boot into Safe Mode, run DDU’s ‘Clean and restart’ for NVIDIA, and install the new driver immediately after rebooting. DDU is the standard tool technicians use because it removes the registry entries and leftover files that cause ‘cannot continue’ errors. Don’t run it casually — only when a normal uninstall has failed — and never interrupt it mid-clean.
Can Windows Update break the NVIDIA installer?
Yes. If Windows Update is simultaneously installing its own display driver, it holds a lock on the GPU device that makes the NVIDIA installer fail its checks. Pause Windows updates, disconnect from the network during the install if needed, and make sure no GeForce Experience or NVIDIA app update is running in the background at the same time.