Windows Update Stuck? How Long to Wait, What to Check, and How to Fix It (Windows 11 & 10)

Short answer: how long to wait

Most ‘stuck’ updates are just slow. If the disk or CPU is still active, keep waiting. Only treat the update as genuinely stuck when there is absolutely no activity for 2 to 3 hours.

The table below shows realistic times by update type and storage type, and the 60-second test after it shows how to tell slow from frozen before you try any fix.

How long should a Windows update take?

These are realistic ranges, not guarantees. Your storage type matters more than almost anything else.

Slow or stuck? The 60-second test

Do this before touching anything.

If Windows is still on the desktop while the update downloads or installs in the background, press Ctrl + Shift + Esc to open Task Manager. Open Performance and watch Disk and Ethernet/Wi-Fi for 60 seconds, then check Processes for Windows Modules Installer Worker (TiWorker.exe) and Windows Update activity.

If the PC is on the blue ‘Working on updates’ or ‘Restarting’ screen, watch the drive activity light if the machine has one and check whether the spinning dots are still animating. A static percentage with animated dots can still mean Windows is working.

Find your stage: where is the update stuck?

Different stages fail for different reasons. Match what you see before applying a fix.

• Pending download or Downloading 0% → usually a connection, proxy, VPN, or update-service problem. Check the connection, disconnect a VPN or proxy, and confirm free storage.
• Installing 0% or Installing 30% → the update may be extracting or staging large packages. Wait, but verify activity with the 60-second test.
• Installing 99% or 100% → Windows may be finalizing, configuring components, and preparing to restart. A long pause can be normal.
• Working on updates, 0% complete → this is the restart/configuration phase. Percentages can jump in large steps with long pauses.
• Restarting or a black screen with a spinner → if there is no drive activity for hours, a display or driver hang may be involved rather than an update hang. Escalate only after the waiting rule is met.
• We couldn't complete the updates. Undoing changes. → Windows is rolling back. Do not power off during the rollback unless it has clearly hung beyond the normal waiting window.

Before you do anything: protect your data

If the PC is stuck and you are about to take stronger action, protect your data and recovery path first.

1. Back up important files if you can still reach the desktop. Use an external drive or cloud storage.
2. Find your BitLocker or Device Encryption recovery key through your Microsoft account or work/school administrator. Recovery actions can trigger a recovery-key prompt.
3. Plug in the charger on a laptop. Do not troubleshoot a long update on battery power.
4. Disconnect unnecessary USB drives, docks, and external displays.

The safe fix order: least to most destructive

Work through these in order and stop as soon as the update completes.

Fix 1: Make sure it is really stuck, and wait the right amount

Apply the 60-second test above. If there is any meaningful activity, wait. Leave the PC plugged in, do not close the lid, and check again in 30 to 60 minutes.

Fix 2: Restart normally (if Windows is responsive)

If you are on the desktop and Windows Update says Restart now or Restart required, restart from the Start menu. Then open Settings → Windows Update and check for updates again. Many apparent ‘stuck’ updates are simply waiting for a reboot.

Fix 3: Run the built-in Windows Update troubleshooter

On current Windows 11 builds, start with the automated Windows Update troubleshooter in the Get Help app. Some builds also expose a troubleshooter under Settings → System → Troubleshoot → Other troubleshooters.

Run the Windows Update troubleshooter, apply any fixes it offers, restart, and check for updates again. Record what the tool reports so you have evidence if the problem continues.

1. Open Get Help and search for Windows Update troubleshooter, or use Settings → System → Troubleshoot → Other troubleshooters when that option is present.
2. Run the Windows Update diagnostics.
3. Apply any suggested fixes, restart, and check Windows Update again.

Fix 4: Free up disk space and remove blockers

Low storage is a common reason updates fail or become unreliable. Give Windows enough working room before deeper repair.

• Aim for at least 20 GB free for large feature updates and at least 10 GB for cumulative updates as a practical troubleshooting target.
• Run Settings → System → Storage → Temporary files and remove safe temporary or update-cleanup data.
• Disconnect VPNs, proxies, external drives, and unnecessary USB devices while testing.
• Temporarily pause third-party antivirus only if its vendor documents doing so for Windows Update troubleshooting, then re-enable it immediately.

Fix 5: Check date, time, and region

An incorrect clock or time zone can interfere with secure connections to Microsoft services.

1. Open Settings → Time & language → Date & time.
2. Turn on Set time automatically and Set time zone automatically.
3. Click Sync now and retry Windows Update.

Fix 6: Reset the Windows Update components (manual repair)

Use this when the same update keeps failing with the same error, or downloads never start. This resets the update cache and related services; it does not intentionally delete personal files or installed apps.

Open Command Prompt as administrator and run the commands below one at a time. Renaming the cache folders rather than deleting them keeps the change reversible.

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

• Restart the PC and check for updates again. Windows will rebuild the renamed cache folders automatically.
• If everything works, the .old folders can be removed later after you are satisfied the system is stable.
• Do not delete unrelated folders inside C:\Windows.

Fix 7: Repair system files with DISM and SFC

When error codes or symptoms point to corruption, repair the component store first and then verify system files. Microsoft documents DISM repair and SFC as part of Windows servicing troubleshooting.

RestoreHealth can pause at a percentage for a while. Do not cancel it simply because the percentage has stopped moving.

If DISM cannot find the required source files, use a clean source that matches the installed Windows version and follow Microsoft's documented /Source guidance. Restart after both tools finish and retry Windows Update.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

• Common corruption-related codes include 0x80073712, 0x800f081f, and 0x80070002, but error-code meanings should be confirmed against current Microsoft documentation.
• Run DISM before SFC when following this repair path.

Fix 8: Install the update manually

When Windows Update repeatedly fails on one specific update, install that update directly instead of retrying the same broken path.

1. Note the KB number from Settings → Windows Update → Update history.
2. Search that KB number at the Microsoft Update Catalog.
3. Choose the package matching the Windows version and architecture, such as x64 or ARM64.
4. Run the downloaded .msu package and restart when prompted.

Fix 9: Use Recovery to uninstall the update or roll back

If the PC will not finish booting after the update, use Windows Recovery Environment (WinRE) and choose the least destructive recovery option that matches the evidence.

1. After the normal waiting period, trigger Windows Recovery Environment if it does not appear automatically. Repeated failed starts can cause Windows to enter WinRE; avoid unnecessary hard shutdowns when the system is still actively working.
2. Go to Troubleshoot → Advanced options.
3. Choose Uninstall Updates and remove the latest quality update first. If that does not help, consider the latest feature update.
4. Use System Restore if a suitable restore point exists.
5. Use Startup Repair when the boot path itself appears damaged.

Fix 10: Repair install (keep files and apps)

If repeated failures persist after the targeted fixes above, an in-place upgrade (repair install) can reinstall Windows while preserving personal files and apps when the installer offers that option.

1. Download the current Windows ISO from Microsoft's official software download page.
2. Mount the ISO by double-clicking it in File Explorer.
3. Run setup.exe from the mounted drive.
4. Choose Keep personal files and apps when prompted, then follow the installer.

Last resort: Reset this PC or clean install

Use reset or a clean installation only after repair options fail and your backup, license information, and recovery keys are secured. Reset this PC → Keep my files is less destructive than a clean install, but a clean install erases the system drive's existing Windows installation and application environment.

Windows Update error codes: what they actually mean

Searching the exact code plus your Windows version usually gives a more targeted path than searching the generic ‘Windows Update stuck’ message. The meanings below are general troubleshooting guidance and should be confirmed against current Microsoft documentation for the specific build.

• If your code is not listed, search the exact code plus your Windows version and favor Microsoft Support, Microsoft Learn, and Microsoft Q&A over random ‘driver updater’ pages.

What not to do

An update can look frozen while it is still staging, verifying, or configuring files. The safest troubleshooting path is to preserve the evidence and change as little as possible at each step.

• Do not hard-power-off during active disk activity.
• Do not download ‘update fixer’ tools from unknown sites.
• Do not delete files inside C:\Windows at random. Use only the deliberate cache-reset steps described above.
• Do not disable Windows Update permanently to avoid the problem.
• Do not run Reset this PC as your first step.

Windows 10 vs Windows 11: what changes

The core troubleshooting logic is similar, but menu paths differ. For example, Windows 10 used Update & Security while Windows 11 uses Windows Update under Settings.

Windows 10 reached end of support on October 14, 2025. Devices that are enrolled in Microsoft's Extended Security Updates program can continue receiving eligible security updates, while standard support and free feature updates are no longer available.

Some PCs cannot run Windows 11 because of hardware requirements such as TPM 2.0, Secure Boot, and supported processor requirements. A feature-update failure can therefore be a compatibility block rather than a corrupted installation.

How to prevent stuck updates

A few simple maintenance habits reduce the chance that a Windows update will appear to freeze or fail.

• Keep 20 GB or more free on the system drive as a practical headroom target for larger updates.
• Install updates when you can leave the PC plugged in and powered on.
• Keep BIOS/UEFI and key storage, chipset, and graphics drivers current from the PC or component manufacturer.
• Keep a recent backup. It turns a recovery problem into an inconvenience rather than a data-loss event.
• If you use a VPN or proxy, disconnect it before large update operations when troubleshooting connectivity issues.
• Avoid stacking multiple restart-pending installs back to back.

When it might be hardware, not software

If updates fail repeatedly across clean installs, or the PC also freezes, crashes, corrupts files, or responds very slowly to disk operations, the problem may be hardware rather than Windows.

• SSD/HDD health → use the drive maker's diagnostics or inspect SMART data. A failing drive can stall on writes and look like a stuck update.
• Memory → run Windows Memory Diagnostic or MemTest86 when random install failures suggest RAM instability.
• Overheating → laptops that throttle heavily during long installs can take far longer or crash.
• Power → a failing battery, adapter, or power supply can cause shutdowns during installation.

Related Windows guides

Use the broader Windows troubleshooting pillar when the symptom is not clearly limited to updates. These pages cover the adjacent failure modes most likely to overlap with update problems.

Frequently asked questions

These answers cover the most common decisions people face when an update appears frozen.