Windows update stuck on pending restart notification on a laptop screen
June 28, 2026

Windows Update Stuck on Pending Restart: How to Fix It

Post By Administrator Microsoft Windows, Windows Troubleshooting , , , , ,

If your PC is showing Windows Update stuck on ‘Restart Required’ — and that message refuses to go away no matter how many times you reboot — you’re not alone. This is one of the most common Windows frustrations, and it has several reliable fixes. Below you’ll find a structured, escalating approach: start with the quick wins, move to deeper repair tools, and learn exactly when a clean install is the genuinely faster option.

Why Does a Windows Update Get Stuck?

Diagram of four common causes of a Windows update stuck error

Before throwing commands at your PC, it helps to understand what’s actually going wrong. A pending restart fix usually stalls for one of four reasons:

  • Corrupted system files — an existing file-level error prevents the update from writing correctly.

  • Stuck Windows Update cache — the SoftwareDistribution folder holds stale or partially downloaded update data.

  • Conflicting pending operations — a previous update, driver install, or repair left an incomplete transaction in the registry.

  • Component registration errors — core Windows Update DLLs become unregistered after a crash or failed patch.

Each fix below targets one or more of these causes. Work through them in order — most users resolve the Windows Update loop at step two or three.

Step 1: Force a Proper Restart (Not Just ‘Restart’)

A standard Start menu restart can be intercepted by apps requesting to delay shutdown, which silently cancels the pending update. Instead, force a clean shutdown:

  1. Press Win + X and open Windows PowerShell (Admin) or Terminal (Admin).

  2. Type shutdown /r /f /t 0 and press Enter.

  3. The /f flag force-closes all apps; /t 0 removes any delay.

Give Windows up to 20 minutes after the reboot — some cumulative updates genuinely need that long to apply. Only move to the next step if the ‘Restart Required’ message returns immediately after a full reboot.

Step 2: Run System File Checker (SFC)

DISM and SFC commands fixing Windows update stuck pending restart issue

The System File Checker scan is often the fastest way to clear an update won’t install situation caused by file corruption. It compares every protected OS file against a known-good reference and replaces any that are damaged.

  1. Open Terminal or Command Prompt as Administrator.

  2. Run: sfc /scannow

  3. Wait for 100% completion — do not close the window. The scan typically takes 5–15 minutes.

  4. Check the result line. If it reports “Windows Resource Protection found corrupt files and repaired them”, restart and re-check Windows Update.

If SFC reports corruption it could not repair, escalate immediately to DISM in Step 3 before trying anything else.

Step 3: Use DISM to Repair the Component Store

DISM (Deployment Image Servicing and Management) reaches deeper than SFC — it repairs the Windows component store that SFC itself draws from. According to Microsoft’s official troubleshooting documentation, running DISM before retrying a failed update resolves the majority of component-level installation failures.

  1. In an elevated Terminal, run: DISM /Online /Cleanup-Image /CheckHealth

  2. If issues are detected, run: DISM /Online /Cleanup-Image /RestoreHealth

  3. This command downloads healthy component data from Windows Update directly, so you need an internet connection. It can take 15–30 minutes.

  4. Once complete, run sfc /scannow again, then restart.

Step 4: Reset Windows Update Components

If you’re still in a Windows Update loop after SFC and DISM, the update agent itself — its cache folders, registered DLLs, and service state — needs a full reset. This is the pending restart fix that resolves the largest share of stubborn cases.

Manual method (full control):

  1. Open an elevated Command Prompt and stop the update services:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver

  2. Rename the cache folders so Windows rebuilds them fresh:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\catroot2 catroot2.old

  3. Restart the services:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver

  4. Reboot and check Windows Update again.

Automated method: Microsoft provides a Reset-WindowsUpdate.ps1 PowerShell script that performs all of the above steps automatically. Search for it on Microsoft’s Q&A pages (learn.microsoft.com) to download the official version.

Step 5: Run the Built-In Windows Update Troubleshooter

Common Windows update won't install error codes explained in a checklist

The built-in troubleshooter won’t always solve a windows update stuck situation on its own, but it can flag specific error codes that guide your next move. In Windows 11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run. In Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Note any error code the troubleshooter reports — codes like 0x80070020, 0x800f0922, or 0x8007001F each point to a different underlying cause and can be searched directly on learn.microsoft.com for targeted guidance.

Reading the Error Codes: What They Actually Mean

When an update won’t install and Windows shows a hex code, it’s telling you exactly which subsystem failed. Here are the most common ones:

  • 0x800f0922 — insufficient space in the System Reserved partition, or a VPN/proxy blocking update servers.

  • 0x80070020 — a file needed by the update is locked by another process (often antivirus).

  • 0x8007001F — hardware-level I/O error; run chkdsk C: /f /r from an elevated prompt.

  • 0x80240034 — Windows Update database is corrupted; the component reset in Step 4 is the fix.

For a deep-dive into the 0x800f0922 error specifically, see our guide on fixing the Windows 11 update 0x800f0922 error.

When a Clean Install Is the Fastest Pending Restart Fix

Escalating through five troubleshooting steps takes time. There is a point — usually when DISM itself fails to restore health, when the component store is too damaged to repair, or when you’ve already spent over two hours — where a clean install genuinely saves time rather than costs it. Indicators that you’re there:

  • DISM /RestoreHealth returns error 0x800f081f even with a network connection.

  • The Windows Update loop persists after a full component reset and two reboots.

  • Event Viewer (eventvwr.msc) shows repeated CBS or WUSA errors across multiple update attempts.

  • System stability is poor beyond just updates — random crashes, sluggish Explorer, frequent app errors.

A clean install does mean re-activating Windows. If you’re on Windows 11 and your licence is a digital entitlement tied to your Microsoft account, reactivation is automatic after reinstalling. If you hold a retail key, keep it somewhere safe before you wipe. If you need a new or replacement licence, Windows 11 Pro Retail keys from ShopKeyOnline are delivered instantly by email from €17.95 and include official Microsoft download links so you can build a clean install USB straight away.

Preventing the Windows Update won’t install Loop in Future

Once you’ve cleared the current Windows Update stuck situation, a few habits keep it from recurring:

  • Don’t force-power-off during updates. If an update says ‘Working on updates — don’t turn off your PC’, wait it out. A hard shutdown mid-update is the single biggest cause of component corruption.

  • Keep at least 10 GB free on your system drive. Updates need staging space; a near-full drive will stall every time.

  • Pause updates before travel, not mid-download. A half-downloaded update left for days can corrupt its own temporary files.

  • Run SFC monthly as maintenance. Catching small file corruptions before they compound prevents the cascading failures that cause a full update won’t install scenario.

And if you ever want to roll back a specific update that caused new problems rather than solving them, our guide on safely removing a Windows Update patch walks through the rollback process step by step.

FAQ

Why does my PC keep showing ‘Restart Required’ even after I restart?

This usually means the update partially applied but failed to finalise — either because of a corrupted system file that blocked the final write, or because the Windows Update service encountered an error it didn’t report clearly. Running sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth and a fresh restart resolves this in the majority of cases. If it persists, the component reset in Step 4 clears the stale pending-operations flag from the registry.

Is it safe to use a Windows Update reset script from the internet?

Only use the official Reset-WindowsUpdate.ps1 script published on Microsoft’s own learn.microsoft.com or answers.microsoft.com pages. Third-party scripts with the same name can carry malware or make registry changes that cause further instability. When in doubt, run the manual commands in Step 4 above — they do exactly the same thing and you can see precisely what’s happening.

How long should Windows Update take after a restart?

Cumulative updates for Windows 10 or Windows 11 typically complete within 5–20 minutes of restarting, depending on the size of the patch and your storage speed. Feature updates (the large twice-yearly upgrades) can take 30–60 minutes on older hardware with a spinning hard drive. If you’re still stuck at the same percentage after 90 minutes, the update has almost certainly stalled and needs the troubleshooting steps above.

Will resetting Windows Update components delete my files?

No. Renaming the SoftwareDistribution and catroot2 folders only clears cached update data — it has no effect on your personal documents, installed applications, or settings. Windows automatically rebuilds those folders as empty directories the next time the update service starts. The only thing you lose is previously downloaded update packages, which Windows simply re-downloads on the next check.

When should I consider a clean install instead of troubleshooting?

A clean install becomes the faster option when DISM cannot restore the component store, when the update loop has persisted through at least three full troubleshooting cycles, or when the system is showing broader instability beyond just updates. A clean install on a modern SSD typically completes in under 30 minutes — often quicker than another hour of repair attempts. Make sure you have a valid Windows licence key before you begin.