Error 0x8024200D means the update installer stalled — it began, stopped making progress, and Windows Update eventually stopped waiting. On a Lenovo laptop the giveaway is a progress bar freezing at the same percentage on every attempt: the installer is stuck on one specific operation and never recovers.

A stalled installer differs from a refused one. Nobody told it to stop; it simply ran out of road. If installs are being refused because another one is already running, the 0x80246007 download-manager guide addresses that instead.

The remedies clear whatever the installer is choking on. Clean boots and peripheral removal eliminate the usual stall points; the manual install at the end bypasses the hung code path entirely.

Why this happens

  • A flaky peripheral driver: USB devices and docks load drivers during installation. A single misbehaving device can leave the installer waiting forever for a response that never comes.
  • Third-party hooks in the install process: Overlays, updaters, and security tools that inject into install operations can deadlock the installer mid-step.
  • A corrupted installer cache: Damaged staging files can send the installer into a loop or a wait state it never exits.
  • A drive that reads too slowly: A disk retrying bad sectors repeatedly makes the installer look hung while it waits on I/O that takes minutes per read.
  • A huge update on modest hardware: What resembles a hang is sometimes extreme slowness — a large feature update on a spinning drive or weak CPU can sit at one percentage for a very long time.
  • Services interfering mid-install: Services that restart or clash during the install window can stall the sequencing the installer expects.
  • Install instructions that contradict the payload: When the update metadata disagrees with the files, the installer can wait for a step that never becomes possible.

How to fix it

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

Fix 1: Strip the environment with a clean boot, then retry

Background software is the most common thing an installer trips over. Third-party updaters, overlays, plus driver utilities can lock the files and services the installer needs, and a clean boot — Windows with Microsoft services only — removes every one of them as a suspect in a single move, no uninstalls required.

  1. Run msconfig from the Win + R dialog and go to the Services tab.
  2. Tick the Hide all Microsoft services box, then click Disable all.
  3. Switch everything off in Task Manager’s Startup apps tab.
  4. Reboot, retry the update, then switch the startup items back on.

Fix 2: Unplug every unnecessary peripheral

USB devices, docks, external monitors, and SD cards all load drivers while the update installs, and any flaky one can stall or crash the installer. Lenovo docks and USB-C hubs are frequent offenders here. Reducing the laptop to charger-only removes the entire category of suspects. Lenovo’s official support site also lists dock firmware updates that resolve exactly these stalls.

  1. Power the laptop fully off.
  2. Detach every USB device, dock, external display, and SD card — the power adapter stays.
  3. Boot up and retry the update with a bare machine.
  4. Plug devices back in one by one to expose the culprit.

Fix 3: Demolish the stale update folders and rebuild

A hung installer’s half-written staging area will hang the next attempt in exactly the same place. Kill the services, rename the folders, restart the services: Windows then recreates both directories empty. The new folders carry clean permissions and no trace of the half-written state that hung the installer.

  1. Open a Command Prompt as administrator — right-click Start, pick Terminal (Admin).
  2. Bring the services to a halt: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Give both folders new names: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old plus ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart all four services with net start, then look for updates again.

Fix 4: Make sure no other installer is running

Windows permits a single trusted installer operation at a time. If another update, a Store app update, or an MSI installer is working in the background, your update is correctly refused until that one finishes. The remedy is patience plus verification — not force.

  1. Check Settings, Windows Update for an update that’s actively installing.
  2. In Task Manager, hunt for msiexec.exe or TiWorker.exe using CPU.
  3. Allow any running installation to complete fully, then reboot.
  4. Retry the update once the system is idle.

Fix 5: Rule out the drive with a chkdsk scan

An installer waiting on a struggling drive is indistinguishable from a hung one. Bad sectors force repeated read retries, each costing the installer minutes of apparent inactivity. A full disk check finds the defective regions and relocates data away from them, so the installer stops waiting on I/O that never arrives.

  1. Open an elevated Command Prompt.
  2. Launch chkdsk C: /f /r, approving the scan at next boot.
  3. Reboot and allow the full scan to run — big drives can need an hour.
  4. Attempt the update again after a clean disk check.

Fix 6: Install the update by hand from the Update Catalog

The automatic installer’s code path is what hung; a standalone installer takes a different one. Downloading the update as an .msu from the Microsoft Update Catalog and running it directly often sails past whatever stalled the automated attempt.

  1. Grab the failing update’s KB number via Settings, Windows Update, Update history.
  2. Query the Microsoft Update Catalog with that KB number and open the entry.
  3. Pull the x64 edition matching the Windows 11 build.
  4. Double-click the .msu, follow the prompts, and restart when instructed.

Fix 7: Reinstall Windows over itself with an in-place upgrade

When the installer hangs through every environmental fix, the install machinery itself is the suspect. An in-place upgrade rebuilds Windows in place while keeping your files and apps, trading all system files, services, and update machinery for fresh copies — deep corruption that individual tools cannot reach gets rebuilt wholesale. Back up beforehand anyway: safe does not mean risk-free.

  1. Pull the Windows 11 media creation tool straight from Microsoft’s download page.
  2. Open it, select Upgrade this PC now, and keep your files and apps.
  3. Wait for the installer to finish — the laptop restarts several times.
  4. After setup, run Windows Update to catch what the repair image missed.

Closing

A hung installer is almost always waiting on something outside itself — a device, a program, a struggling drive — rather than broken internally. Strip the environment down, give the update a clean run, and the same package that stalled for hours typically completes in minutes. If the failure is a component mismatch rather than a stall, the 0x800F0988 component-mismatch guide is the guide you need.

Frequently asked questions

What does error 0x8024200D mean?
It means WU_E_UH_INSTALLERHUNG: the update handler launched the install, the installer stopped responding, and Windows Update eventually abandoned the wait. A progress bar frozen at the identical percentage on repeated attempts is the telltale sign. The installer is typically stalled on an external dependency — a misbehaving peripheral, a deadlocking third-party hook, corrupted staging data, or a drive struggling with reads.
How long should I wait before calling it hung?
Allow a stalled install at least an hour past the point where visible progress stopped — longer for feature updates on slow drives, since some phases genuinely show no movement while working. But when both the percentage and disk activity stay frozen for over an hour, or every retry stalls at the same point, it is hung rather than slow. Zero disk and CPU activity from the installer in Task Manager confirms the hang.
Can I just kill the hung installer?
You can end the installer process in Task Manager, but do it once and reboot before retrying — killing it mid-write can leave partial state the next attempt must clean up. Never cut power while the installer holds the system in a servicing state; a graceful restart after ending the process is far safer. Then apply the clean-boot fix so the next attempt does not stall the same way.
Why does it always hang at the same percentage?
Because the installer runs the same script every time and stalls at the same operation — usually one driver installation, a particular file copy, or a single device enumeration step. That repeatability is diagnostically valuable: note the percentage, check the update logs for what executes at that stage, and you will usually identify the exact device or component behind the stall.