Save your work and restart Windows normally; after 16 hours of repeated downloading/installing cycles followed by 0%, the update workflow should be treated as stalled rather than left running indefinitely.
Microsoft currently lists no known issues for KB5132061 (OS Build 26300.9974), so this is not presently identified as a widespread fault with that update. ^1^
Recover the stalled update
- Restart normally
- Select Start > Power > Restart.
- Keep the PC connected to power.
- After signing in, open Settings > Windows Update and select Check for updates.
- Run the Windows Update troubleshooter
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Find Windows Update and select Run.
- Restart when it finishes, then return to Settings > Windows Update > Check for updates. ^2^
- Check the basic requirements
- Confirm the Internet connection works.
- Disconnect unnecessary USB drives, docks, and other external hardware.
- Ensure the system drive has at least 20 GB free for 64-bit Windows.
- Verify Settings > Time & language > Date & time has automatic time and time-zone settings enabled. ^3^
If it returns to 0% again
Clear only the downloaded Windows Update cache:
- Press Win+R, enter
services.msc, and press Enter. - Right-click Windows Update and select Stop.
- Open File Explorer and navigate to:
C:\Windows\SoftwareDistribution - Delete the contents of that folder—not the
SoftwareDistributionfolder itself. - Return to Services, right-click Windows Update, and select Start.
- Restart Windows and select Settings > Windows Update > Check for updates. ^3^
This removes cached update files, so Windows will download the package again.
If installation still fails
Record the exact error code shown under Settings > Windows Update > Update history. Error codes such as 0x800705b4, 0x80240034, or 0x8007000d distinguish timeout, incomplete-update, and cache-related cases and determine the next repair step. ^3^
For Windows 11 26H2, KB5132061 also requires an update released on or after September 22, 2026 and servicing-stack version 26100.9539 or later. If repeated attempts produce an installation error rather than remaining at 0%, that prerequisite can be checked from an administrator Command Prompt:
DISM /Online /Get-Packages | findstr /i "ServicingStack"
The returned servicing-stack package version must be 26100.9539 or later. ^1^
References