Windows 11 Update Stuck at 0% or 100%? 10 Safe Fixes (2026)
A Windows 11 update stuck at 0%, 99%, or 100% is not always frozen. Windows may still be downloading, verifying a package, preparing a rollback path, or servicing protected files after a restart. The correct fix depends on the stage shown in Windows Update and the error code in Update history.
This guide starts with reversible checks, then moves to the Windows Update cache, Microsoft repair commands, error-specific actions, and Windows 11’s built-in repair reinstall. It does not require a registry cleaner, driver pack, unofficial ISO, or third-party “PC repair” program.
Quick Answer
Keep the PC powered, wait if Windows is still showing activity, and restart normally when the desktop is available. Then check the connection and free storage, run Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run, and note the failed update’s error code. If it still fails, clear the Windows Update cache, run DISM followed by SFC, and use Fix problems using Windows Update → Reinstall now only as the final repair.
Is This the Right Guide?
Use this guide if…
- Windows Update remains on Downloading or Installing at one percentage.
- The same quality or feature update fails repeatedly.
- You see “Pending restart,” “Retry,” or a Windows Update error code.
- Windows still opens normally and you can reach Settings.
Use another path if…
- Windows no longer starts or enters a recovery loop.
- The drive makes unusual noises or disappears from the firmware.
- The PC is managed by work or school update policies.
- A feature update is simply not being offered to the device.
Before You Start
Do not force the PC off merely because the percentage has paused. A full-screen “Working on updates” phase can take much longer than the download shown in Settings. If disk, CPU, or network activity continues, Windows may still be working.
Do not interrupt an active installation
If Windows is installing updates before sign-in, keep the device powered. A forced shutdown during protected-file servicing can create a startup or recovery problem. Seek help if the machine has remained completely unresponsive for hours rather than repeatedly forcing it off.
First, Identify Where the Update Stops
Open Settings → Windows Update and read the status beside the update. Next, open Update history and select the failed entry. Copy its KB number and complete error code before changing anything.
| Status | What may be happening | Best starting point |
|---|---|---|
| Downloading at 0% | The transfer is waiting, the connection is restricted, or update services have not started correctly. | Connection, restart, troubleshooter |
| Downloading at 99% or 100% | Windows may be verifying the package or preparing it for installation. | Wait, then check storage and cache |
| Installing at 0% | A prerequisite or earlier pending operation may need a restart. | Normal restart and Update history |
| Installing at 99% or 100% | Component servicing, driver work, or cleanup may still be running. | Wait; repair only after an actual failure |
| Feature update is absent | The rollout may not have reached the device, or a compatibility safeguard may apply. | Check Windows release health; do not bypass a hold |
1Wait Safely, Then Restart Normally
Why this comes first: update percentages do not move continuously. Verification and component cleanup can appear idle even when Windows is still working.
If the desktop is available, wait while the status or system activity continues to change.
Save your work and choose Start → Power → Restart. A restart completes pending servicing operations more reliably than a normal shutdown on systems using Fast Startup.
After sign-in, open Settings → Windows Update → Check for updates.
If the same update fails again, open Update history and record the error code.
The pending operation completes, or Windows Update returns a specific error that identifies the next safe action.
2Remove Connection and Hardware Blockers
Why this helps: Microsoft lists unstable connectivity, unnecessary external hardware, and incompatible drivers or software among common causes of upgrade and installation failures.
Confirm that normal websites open. If possible, use a stable Ethernet or trusted Wi-Fi connection.
Disconnect a VPN or proxy temporarily. Reconnect it after Windows Update finishes.
Disconnect nonessential USB storage, memory cards, printers, docks, scanners, and other accessories. Keep the keyboard, mouse, display, internet, and power connected.
Open Settings → Time & language → Date & time. Enable automatic time and time zone, then select Sync now.
Try Windows Update again.
Reconnect accessories one at a time after the update completes. Do not continue to component repairs after the problem is solved.
3Free Space on the Windows Drive
Why this helps: Windows needs temporary space to download, unpack, install, and recover from an update. Feature upgrades usually need more working space than a monthly quality update.
Open Settings → System → Storage.
Select Cleanup recommendations and review each category before deleting anything.
Empty the Recycle Bin only after confirming that it contains nothing important.
Move large personal files to another trusted drive if the Windows drive is almost full.
Restart and check for updates again.
Do not delete system folders manually
Do not remove WinSxS, recovery partitions, or unknown folders under C:\Windows. Use Windows Storage and Cleanup recommendations.
4Run the Windows Update Troubleshooter
Why this helps: Microsoft recommends the built-in troubleshooter before manual component repair. On current Windows 11 releases, it may use the Get Help app to run diagnostics.
Open Settings → System → Troubleshoot → Other troubleshooters.
Find Windows Update and select Run.
Allow Get Help or the troubleshooter to complete its checks and apply recommended changes.
Restart Windows even if the tool says it made no changes.
Return to Windows Update and select Check for updates.
The tool corrects a service or configuration problem, or narrows the failure to a more specific error.
5Check Update History and Safeguard Holds
Why this matters: a feature update that is not offered is different from a quality update that repeatedly fails. Microsoft can apply compatibility safeguards to affected drivers, apps, or devices.
Open Settings → Windows Update → Update history and note the failed update’s KB and code.
Open the official Windows release health hub.
Select your installed Windows 11 version and review current known issues.
If Windows says a feature update is not ready for the device, wait for Microsoft or the hardware vendor to remove the safeguard.
Do not force a feature update past a known hold
A safeguard is intended to prevent a documented compatibility problem. Update the affected driver or app through its official vendor and wait for Windows Update to offer the release normally.
6Clear the Windows Update Cache
Why this helps: an incomplete or corrupted package in C:\Windows\SoftwareDistribution can make Windows retry the same failed download. Microsoft includes cache cleanup in its Windows Update troubleshooting guidance.
Press Win + R, type services.msc, and press Enter.
Find Windows Update, right-click it, and select Stop.
Open File Explorer and go to C:\Windows\SoftwareDistribution.
Delete the contents inside SoftwareDistribution. Do not delete the Windows folder or unrelated folders.
Return to Services, right-click Windows Update, and select Start.
Restart and check for updates.
Windows rebuilds its update working cache. This does not remove your documents or uninstall updates that are already installed.
7Repair Windows With DISM and SFC
Why this helps: Windows Update depends on a healthy component store and protected system files. Microsoft’s current System File Checker guidance runs DISM first, followed by SFC.
Search for Command Prompt, right-click it, select Run as administrator, and approve the User Account Control prompt. A standard Command Prompt does not have enough permission for these repairs.
1. Repair the Windows component store
DISM.exe /Online /Cleanup-Image /RestoreHealth2. Verify protected system files
sfc /scannowRun DISM and wait for it to finish.
Run SFC only after DISM completes.
Restart Windows.
Try the failed update again and check whether the error code changes.
DISM reports that the restore operation completed successfully, and SFC reports either no integrity violations or that damaged files were repaired.
8Match the Error Code to the Cause
Why this matters: clearing a cache will not fix every driver or storage error. Use the complete code instead of applying random repair scripts.
| Error | Common direction | Best first action |
|---|---|---|
| 0x8007000d | Update files or cache corruption | Clear the cache; run DISM and SFC |
| 0x800705b4 | The update took too long or was interrupted | Restart, stabilize the connection, retry |
| 0x80240034 | Incomplete update or connection interruption | Check the connection and rebuild the cache |
| 0x80073712 | A required update file is damaged or missing | Run DISM, then SFC |
| 0x80070422 | Windows Update service is disabled or stopped | Run the troubleshooter and check the service |
| 0x80070020 | Another process is using required files | Restart and close unnecessary background apps |
| 0x800F0922 | Connection, storage, or servicing-partition issue | Disconnect VPN, free space, then investigate the exact update |
| 0xC1900101 | Driver compatibility during an upgrade | Disconnect extra hardware and use manufacturer drivers |
For a driver-related failure, obtain BIOS, chipset, storage, graphics, and network updates only from the PC, motherboard, or device manufacturer. Avoid third-party driver packs.
9Install One Failed KB From Microsoft
Use this only when: one specific quality update fails while Windows Update otherwise works. This is not the preferred way to force a blocked feature upgrade.
Copy the exact KB number from Windows Update → Update history.
Search for it in the official Microsoft Update Catalog.
Choose the package matching your Windows version and architecture, such as x64 or ARM64.
Download and run the Microsoft package, then restart.
Stop if the package is unclear
Do not download update packages from file-sharing sites. If you cannot confidently match the version and architecture, skip this method and use the repair reinstall below.
10Reinstall the Current Windows Version as a Repair
Why this is last: it downloads and reinstalls the current Windows version to repair system files and components. Microsoft states that the option preserves apps, files, and settings, but it takes longer and should follow the simpler fixes.
Back up important files and connect the PC to power and the internet.
Open Settings → System → Recovery.
Under Fix problems using Windows Update, select Reinstall now.
Confirm the restart preference and allow the download and repair installation to finish.
Restart, then open Windows Update and check again.
If Reinstall now is missing
The option can be unavailable on an older Windows 11 build or a work/school-managed device. Do not substitute Reset this PC without understanding its consequences.
Windows repairs the servicing components while preserving installed apps, personal files, and settings.
What If Windows No Longer Starts?
Do not keep repeating cache or command repairs if Windows cannot reach the desktop. Use the Startup & Recovery path instead. In Windows Recovery Environment, begin with Startup Repair. If the failure started immediately after an update, the Advanced options screen may also offer Uninstall Updates.
Stop when data or hardware is at risk
If the storage drive disappears, reports hardware errors, makes unusual noises, or the PC asks for a BitLocker recovery key you do not have, stop. Protect the data and contact the device administrator, manufacturer, Microsoft, or a qualified technician.
When to Stop Troubleshooting
- Stop after the update installs successfully; extra repairs add unnecessary risk.
- On a work or school PC, contact the administrator before clearing caches or installing a package manually.
- If several unrelated updates fail after DISM, SFC, and the repair reinstall, investigate storage health and system logs rather than repeating the same steps.
- If the error belongs to a known issue, wait for Microsoft’s resolution instead of forcing the update.
Prevent the Same Problem Next Time
- Keep reasonable free space on the Windows drive.
- Restart after updates instead of leaving a pending restart for weeks.
- Use manufacturer support pages for BIOS and drivers.
- Avoid update-blocking scripts, registry cleaners, modified Windows images, and unofficial repair tools.
- Keep a current backup of documents, photos, and recovery information.
- Check Windows release health before deploying an optional preview or feature update on an essential PC.
Build a Useful Next-Step Report
If no published guide matches the final error, use Request a Guide and include only non-sensitive details:
- Windows version and OS build.
- The exact KB number and complete error code.
- Whether the status says Downloading or Installing.
- Which steps above completed successfully.
- The exact DISM or SFC result, without personal paths or account details.
For a correction to this article, use Contact Us. Never submit passwords, product keys, BitLocker recovery keys, private logs, or personal files.
Frequently Asked Questions
Why is my Windows 11 update stuck at 100%?
Can I turn off the PC during an update?
Does clearing SoftwareDistribution delete personal files?
Should I run DISM or SFC first?
Will “Fix problems using Windows Update” erase my apps?
Why is a Windows 11 feature update not appearing?
Official Microsoft Sources
Article Review
Reviewed: August 13, 2026
Scope: Windows 11 Settings paths, Windows Update cache guidance, DISM/SFC order, common Microsoft error-code direction, release-health safeguards, and the built-in repair reinstall.
Editorial rule: safer and reversible checks appear before administrator commands or recovery reinstall. No third-party download is required.
Comments
Post a Comment