There is a particular kind of frustration in watching Windows Update download an update successfully, reach the install phase, and then fail — every single time. On ASUS laptops this pattern is common enough to have its own rhythm: the download completes, the percentage climbs during installation, and then the update reverts with a generic “failed to install” message and no useful explanation.

The crucial distinction is that the download works and the install does not. That tells you the network, the update servers, and the basic Windows Update machinery are fine. The failure is happening locally, during the phase where Windows validates the payload, stages files, and commits changes to the running system. On ASUS machines the usual suspects are corrupted staged files, conflicting ASUS utilities, incompatible drivers, or damaged system files. The fixes below attack them in the order a technician would.

Why this happens

  • Corrupted staged update files. The download completed but files were damaged in transit or on disk, so installation validation fails.
  • ASUS utility conflicts. Armoury Crate, MyASUS, and ASUS Live Update can lock system files or drivers that the installer needs to replace.
  • Incompatible or outdated drivers. The update’s driver validation step rejects the install if a critical ASUS driver is too old or corrupted.
  • Damaged component store. Corruption in WinSxS means the installer cannot assemble the final system image.
  • Third-party antivirus blocking. Real-time protection can intercept the installer’s file operations and abort the commit phase.
  • Insufficient disk space. The install phase needs working room beyond the download size; a full disk fails the commit.
  • Pending operations from earlier failures. Each failed attempt leaves pending file operations that can interfere with the next try.

How to fix it

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

Fix 1: Identify the failing update and its error code

Do not treat all failures the same. The KB number and error code point at the right repair.

  1. Open Settings > Windows Update > Update history and find the failed update — note its KB number and any error code.
  2. If there is a code like 0x80070002 or 0x80070005, look it up specifically: our guides to error 0x80070002 on ASUS and error 0x80070005 on ASUS target those exactly.
  3. Note whether it is a cumulative update, a driver update, or a feature update — driver updates failing usually means the ASUS driver itself is the problem, and skipping it in favor of a direct manufacturer install is the fix.
  4. Check the date of the first failure. Months of backlog suggest starting with the servicing stack (see Fix 6).

Fix 2: Run the Windows Update troubleshooter

The automated troubleshooter resets services and re-registers update components — quick, safe, and occasionally all you need.

  1. Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. Click Run next to Windows Update and accept every fix it proposes.
  3. Restart the laptop and retry the update.
  4. If the troubleshooter reports it could not fix the problem, continue to Fix 3 — manual cache clearing covers what the troubleshooter misses.

Fix 3: Clear the update cache and reset components

When staged files are corrupted, no amount of retrying helps. Wipe the staging area and let Windows rebuild it.

  1. Open Command Prompt as administrator.
  2. Stop the services: net stop wuauserv, net stop bits, net stop cryptsvc.
  3. Rename the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart the services: net start wuauserv, net start bits, net start cryptsvc. Then go to Settings > Windows Update, check for updates, and retry the install from a clean cache.

Fix 4: Pause ASUS utilities and antivirus during the install

ASUS background software and third-party antivirus are the two most common install-phase blockers on these machines.

  1. In Task Manager’s Startup apps, temporarily disable Armoury Crate, MyASUS, and ASUS Live Update entries; stop their services in services.msc too.
  2. If you use third-party antivirus, pause its real-time protection for the duration of the install.
  3. Retry the update with both paused. If it installs, the conflict is confirmed — update your ASUS apps afterward (outdated versions cause the repeat failures), then re-enable everything.
  4. Consider whether you need the third-party antivirus at all: Windows Security is solid, and one fewer kernel-level conflict means fewer failed installs.

Fix 5: Repair system files with DISM and SFC

If the install phase fails validation, the underlying Windows image may be damaged. Repair it before the next attempt.

  1. In an administrator Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth (15–30 minutes).
  2. Follow with sfc /scannow until it reaches 100%.
  3. Restart and retry the update. If both tools report repairs, the odds are good this was the blocker.
  4. For persistent component-store damage, our guide to running DISM RestoreHealth shows how to feed DISM repair files from a Windows ISO.

Fix 6: Free disk space and check drive health

The install phase needs staging room, and a failing drive corrupts staged files. Check both.

  1. Open Settings > System > Storage and ensure at least 20 GB free on C:. Run Disk Cleanup with Clean up system files to remove old update backups.
  2. In an administrator Command Prompt, run chkdsk C: /f to scan for file-system errors (schedule it for the next restart if prompted).
  3. Check drive health with wmic diskdrive get status — a non-OK result means the hardware itself is the root cause.
  4. Keep the charger connected and disable sleep during the retry: Settings > System > Power & battery.

Fix 7: Install the update manually from the Update Catalog

When Windows Update’s install phase keeps failing, bypass it with a direct package install.

  1. Search the Microsoft Update Catalog for the failing update’s KB number.
  2. Download the x64 package and double-click the .msu file to install it directly.
  3. Restart when prompted, then verify in Settings > Windows Update > Update history that it shows as installed.
  4. If the manual install also fails, an in-place upgrade is the remaining option: download the Windows 11 ISO from Microsoft’s download page , run setup.exe, and choose Keep personal files and apps.

Closing

A Windows update that downloads but will not install on an ASUS laptop is a local problem with a local fix — corrupted staging, conflicting ASUS utilities, or damaged system files, in roughly that order of likelihood. Clear the cache, quiet the ASUS software, repair the image, and install manually if needed. Once updates install cleanly, keep things that way by updating your ASUS apps and drivers regularly — our driver update guide covers the safe order — and if downloads themselves start hanging instead of installs, see our guide to updates stuck downloading on Windows 11 .

Frequently asked questions

Why do Windows updates fail to install on ASUS laptops specifically?
ASUS laptops carry extra manufacturer software — Armoury Crate, MyASUS, ASUS Live Update — that competes with Windows Update for system resources and can lock files the installer needs. Combined with ASUS-specific drivers that occasionally lag behind Windows requirements, this creates more install-time conflicts than on a clean Windows install. Updating ASUS software first removes most of these conflicts.
Should I keep retrying a failed update or stop and fix something first?
Stop and fix something first. Blindly retrying the same failed update rarely works because the underlying condition — corrupted cache, bad driver, full disk — has not changed. Each failed attempt also adds to the pending-operations queue, which can make the eventual fix harder. Work through the diagnostic steps below once, then retry from a clean state.
Will failed updates damage my ASUS laptop?
No. Failed installs are non-destructive by design — Windows validates the update before committing it, and if validation fails, nothing changes. The danger is not the failed update but the backlog it creates: months of skipped security patches leave the machine exposed. Your files and programs are completely safe during a failed install.
How do I know which specific update is failing?
Open Settings, go to Windows Update, then click Update history. Failed updates show a red failure notice with the update name, KB number, and usually an error code. The KB number is the key detail — it lets you search for the exact update in the Microsoft Update Catalog or look up its specific error code for targeted fixes.