Windows Update Stuck or Failing: What to Check

If Windows Update seems stuck or is taking forever, look for change: while the stage text, percentage, spinner, restart cycle, or disk activity keeps moving, Windows is still working, so keep the PC powered and wait. When you see Windows Update stuck or failing with an error code, an Undoing changes screen, or no change at all for an unusually long period, identify whether the PC is checking, downloading, installing, restarting, or rolling back, because the safe next action depends on that stage. A percentage that has not moved for a few minutes is not enough evidence that installation has failed.

Begin with the broader device and app troubleshooting guide if Windows Update is only one of several unrelated symptoms. For an isolated update problem, preserve the exact update name, error code, and last visible progress before changing anything.

Key Takeaways

• Do not force the PC off while installation progress, disk activity, or restart messages are still changing.
• Record the update name, stage, and exact error code before trying a fix.
• Back up important files and confirm access to the BitLocker recovery key before advanced repair.
• Check power, storage, network, time, and unnecessary peripherals before editing services or caches.
• Use recovery or a clean installation only after supported troubleshooting and a verified backup.

Windows Update stuck or failing, or still working?

Look at the wording on screen. Checking for updates, Downloading, Installing, Pending restart, and Undoing changes describe different processes. If Settings still responds, open Windows Update and Update history without canceling the current task. Record the update's Knowledge Base number, feature version, or driver name and any code beginning with 0x.

During a restart, a percentage may pause while Windows migrates components or configures drivers. Listen for normal fan changes and observe whether the progress text, percentage, or disk indicator changes over time. Leave a laptop connected to reliable power. Do not close its lid if that would put it to sleep.

Treat a black screen with a visible pointer, a changing spinner, or occasional restarts differently from a PC that has shown no activity for an unusually long period. There is no universal safe timeout because update size, storage speed, and hardware differ. If the manufacturer's support page gives a model-specific waiting or recovery instruction, follow that instruction.

If Windows returns to the desktop after displaying Undoing changes, the update has already failed and rolled back. That is the time to collect Update history and Event Viewer details, not to interrupt the rollback. If the machine cannot boot, stop using ordinary Windows Update steps and follow the PC maker's supported startup-recovery path.

What if Windows Update is stuck on Checking for updates?

Checking for updates and Downloading run inside Settings while you can still use the desktop, so they are not the installation that happens during a restart. For an update stuck at 0% or 100%, Microsoft's first steps are to restart the PC so other apps are not blocking the process, confirm the internet connection, and check free disk space.［1］ If the check keeps showing the same percentage, work through the connection, time, and storage checks below before assuming the installation itself is damaged.

A restart is safe at this stage because nothing is being installed yet. Save your work, choose Restart from the Start menu instead of holding the power button, then open Windows Update and check again. If you need the PC right away, Windows Update settings also let you pause updates for a limited time; this holds back downloads and installs that have not started, but it does not cancel installation work already running during a restart.

The answer changes once the screen says Windows is working on updates and asks you not to turn off the PC. At that point you cannot cleanly stop the update: let it finish or roll back as described above, and treat a PC stuck in a restart loop as a case for the manufacturer's supported recovery path.

What should you record before retrying a failed Windows Update?

Write down four facts: the Windows edition and version, the update identifier, the failure stage, and the exact error code. A monthly quality update, a hardware driver, and a major Windows feature upgrade have different compatibility risks. Do not assume that advice for one applies to the others.

Confirm that the Windows version is still supported and that the update is offered through the normal Windows Update page. Microsoft notes that support for Windows 10 ended on 14 October 2025 and recommends upgrading to Windows 11, so on a Windows 10 PC check which updates the device can still receive before treating a missing one as stuck.［2］ Managed work or school PCs may receive updates through an administrator-controlled policy. Do not remove management, change organization policies, or use consumer installation media to bypass that control.

Before advanced repair, make a current backup of irreplaceable files. Microsoft also tells users to back up personal files before its general update troubleshooting steps.［1］ On an encrypted PC, confirm that you can retrieve the BitLocker recovery key from the appropriate personal or organization account. A firmware, boot, or recovery change can request that key even when Windows normally starts without it.

Use this short evidence table to avoid random changes:

Evidence	Why it matters
Update name or KB number	Separates a cumulative update from a driver or feature upgrade
Exact error code	Points to permissions, storage, component, or compatibility guidance
Last successful update	Shows whether the service works in general
Free space on the Windows volume	Update staging and rollback both require working room
Recent hardware or driver change	Helps isolate upgrade compatibility failures

Which low-risk checks should come first?

Save open work, connect the PC to AC power, and verify that the system drive has comfortable free space. Do not calculate a universal minimum from an old article; use the space requirement shown by Windows or the current installation assistant for the exact update. If space is low, remove files you recognize or move personal data after confirming the backup. Do not delete system folders to create room.

Check that date, time, and time zone are correct. Use a stable home or office connection rather than a captive portal. If downloading never begins, test ordinary browsing and another Microsoft service, but remember that a working web page does not prove every update endpoint is reachable.

Disconnect nonessential external drives, docks, card readers, printers, and other accessories, while keeping the keyboard, mouse, display, network, and power path needed to operate the PC. Microsoft includes unnecessary external hardware among its general update checks. Keep a note of what you disconnected so it can be restored one item at a time.

Restart Windows normally after saving work, then check for updates again. A restart is appropriate when Windows is at the desktop or explicitly requests one; it is not permission to hold the power button during active installation. If several updates are offered, allow Windows to complete and restart between rounds instead of launching an unrelated installer at the same time.

Do not permanently disable the firewall or endpoint protection. If an exact vendor or Microsoft error procedure requires a temporary security-software test, first confirm how protection will be restored and keep the test limited to that procedure. Avoid generic “debloat” tools, registry cleaners, and scripts that disable update services.

How should you use the troubleshooter, history, and error code?

On current Windows 11 systems, Microsoft directs users to the automated Windows Update troubleshooter in the Get Help app.［2］ Run it once, allow it to complete, note what it reports, and restart only when requested. Repeatedly running it without recording the result makes it harder to see whether the state changed.

Open Update history and select the failed entry. Search the exact code in Microsoft Support or the device manufacturer's support site. A 0xC1900101 family error during an upgrade commonly points toward a driver path, while a permissions or component-store code needs a different response. Do not paste commands from a forum solely because the percentage looks similar.

For a major upgrade or installation error, Microsoft recommends checking the specific error code and removing nonessential hardware; upgrade guidance also distinguishes driver and compatibility failures from ordinary monthly updates.［3］ Update a driver only from Windows Update or the hardware maker's supported page for the exact model. Do not install a driver pack from an unknown mirror.

If the Store fails while Windows Update works, use the separate Microsoft Store download guide. If startup is the real symptom after a completed update, compare it with the Windows slow-startup checks. Keeping these symptoms separate prevents an app-queue or startup problem from being misdiagnosed as a broken system-update service.

When are DISM, SFC, recovery, or reinstall appropriate?

Use system-file repair only after the low-risk checks and built-in troubleshooter fail, and only while Windows can start reliably. Open an elevated terminal through the normal Windows interface, then run the current Microsoft-supported DISM repair before System File Checker. Let each command finish and save its result. Do not close the terminal because progress appears to pause.

Do not begin by deleting everything inside SoftwareDistribution, renaming component folders, or manually stopping update services. Those operations change diagnostic state and can leave services stopped if copied incorrectly. Use them only when the current Microsoft procedure for the exact error calls for them, you understand the administrator commands, and you can verify that services start again.

Recovery options belong at the end of the decision tree. Before using Startup Repair, System Restore, an in-place repair installation, Reset this PC, or clean installation, verify the backup and BitLocker recovery key. Read whether the selected option keeps apps and files, removes apps, or erases the drive. “Keep my files” is not a substitute for an independent backup.

Escalate to the PC manufacturer or Microsoft when the same supported update repeatedly fails after clean low-risk checks, when firmware or storage diagnostics report a problem, when Windows cannot complete rollback, or when the PC cannot boot. Provide the Windows version, model, update identifier, error code, recent driver or hardware changes, and the troubleshooting results.

Summary

• Identify the exact update stage and preserve the error code before changing the system.
• Wait while installation activity is changing; use a normal restart only from a stable desktop or an explicit prompt.
• Back up files and confirm the BitLocker recovery key before component repair or recovery.
• Check power, storage, network, time, peripherals, Update history, and the built-in troubleshooter in that order.
• Keep cache resets, service changes, recovery, and clean installation as controlled late-stage options.

FAQ

How long should I wait when Windows Update is stuck at one percentage?

There is no universal timeout. Keep waiting while the message, percentage, spinner, restart cycle, or storage activity changes. Use model-specific support guidance if the PC remains completely unchanged for an unusually long period.

Is it safe to force Windows off during an update?

Not while installation or rollback is visibly active. An interruption can leave Windows unable to boot. Use a forced shutdown only when the manufacturer's supported recovery procedure explicitly requires it for an unresponsive PC.

Why does Windows say “Undoing changes”?

Windows is rolling back an update that did not complete. Keep the PC powered and allow rollback to finish, then collect the failed update name and code from Update history.

Should I delete the SoftwareDistribution folder?

Not as a first step. It changes the update cache and may require administrator service commands. Use the current Microsoft procedure only when it matches the exact error and after the lower-risk checks.

Can low disk space make Windows Update fail?

Yes. Windows needs working room to download, stage, install, and potentially roll back an update. Follow the space requirement shown for the exact update and remove only data you understand.

What does a Windows Update error code tell me?

It narrows the failure category, such as permissions, storage, component repair, or driver compatibility. Record the full code and update identifier rather than searching only the percentage where progress stopped.

Should I reinstall Windows if one update fails?

No. Start with evidence collection, backups, low-risk checks, the built-in troubleshooter, and error-specific official guidance. Reinstallation is a late option because it can remove applications or data.

When should I contact the PC manufacturer?

Contact the manufacturer when firmware, storage, a model-specific driver, repeated rollback, or a boot failure is involved. Include the exact model, Windows version, update identifier, error code, and tests already completed.

Sources

1. Microsoft Support - Troubleshoot problems updating Windows — https://support.microsoft.com/en-US/Windows/Deployment/Updates-Lifecycle/troubleshoot-problems-updating-windows
2. Microsoft Support - Windows Update Troubleshooter — https://support.microsoft.com/en-us/windows/windows-update-troubleshooter-19bc41ca-ad72-ae67-af3c-89ce169755dd
3. Microsoft Support - Get help with Windows upgrade and installation errors — https://support.microsoft.com/en-us/windows/deployment/install-upgrade/get-help-with-windows-upgrade-and-installation-errors

Sources checked 4 October 2026.

Related Articles

• Device and app troubleshooting guide
• Troubleshoot slow Windows startup
• Fix persistent 100% disk usage
• New Windows 11 PC setup checklist
• Microsoft Store apps not downloading

This article provides general troubleshooting information. Follow the current instructions for your Windows version, PC model, organization, and recovery configuration before changing system components.