Windows Updates Stuck on Shutdown — Complete Fix Guide (2026)

If your Windows computer is stuck on shutdown showing “Working on updates, don\’t turn off your PC”, “Installing Update — Please do not power off or unplug your machine”, or “Configuring Windows Updates 3 of 3 0% Completed” — you are in the right place. This is the complete fix guide covering every known cause and solution for Windows 10 and Windows 11 in 2026.

This guide consolidates all our previous Windows Update stuck guides into one comprehensive resource. Bookmark it — it covers every scenario.

How Long Should You Wait?

Before jumping to fixes — make sure your machine is actually stuck. Large Windows Feature Updates (like Windows 10 22H2 or Windows 11 23H2) can genuinely take 30-90 minutes to install depending on your hardware.

Our rule of thumb: If your computer has shown the same percentage or the same message for more than 3 hours without any change, it is definitely stuck and you need to act. Under 30 minutes — be patient. 30 minutes to 3 hours — watch it. Over 3 hours — follow this guide.

Video Demo

Watch the video demo below which shows the SoftwareDistribution fix being carried out live. Read the full written guide below for all methods and 2026-specific details.

Step 1 — Force Shutdown Your Machine

The first thing you need to do is get back into Windows. Hold down the physical power button on your computer tower or laptop (not the monitor screen!) for around 10 seconds until it completely shuts off.

Turn it back on. One of three things will happen:

• Best case — Windows boots normally. Follow Fix 1 below before doing anything else.
• Middle case — Windows boots into Safe Mode or recovery. Follow Fix 2 below.
• Worst case — Windows will not boot at all. The update may have corrupted your installation and you may need a repair install or rebuild.

Critical: Once you are back in Windows, do NOT shut down or reboot again until you have applied one of the fixes below — you will immediately get stuck again.

Fix 1 — Reset the Windows Update SoftwareDistribution Folder

This is the fix that resolves the problem in the vast majority of cases. The SoftwareDistribution folder is where Windows downloads and tracks all updates. When this folder or its database becomes corrupt, Windows gets stuck in a loop trying to install an update that has already failed.

The solution is to stop the Windows Update service, rename the corrupt folder (so Windows cannot find it), then restart the service — Windows will automatically create a fresh clean SoftwareDistribution folder.

Open an Elevated Command Prompt

In Windows 10 or Windows 11, right click the Start button and click Windows PowerShell (Admin) or Command Prompt (Admin):

You should see a black command prompt window:

Run These Three Commands

Command 1 — Stop the Windows Update service:

net stop wuauserv

Wait for the confirmation message that the service has stopped before continuing.

Command 2 — Rename the corrupt SoftwareDistribution folder:

ren c:\windows\softwaredistribution sd.old

This renames the folder to sd.old — Windows cannot find it so it will create a fresh one. You can delete sd.old later to recover disk space but it is not urgent.

Command 3 — Restart the Windows Update service:

net start wuauserv

Windows will automatically recreate the SoftwareDistribution folder. You should now restart your computer — it will boot normally without the stuck update screen.

Important note: The next time you run Windows Update it may show an error or say updates have never been checked. This is normal — just click Check for Updates and Windows will re-download and catch up with any missing updates automatically.

Fix 2 — Rename the Pending.xml File (Configuring Updates 3 of 3 Fix)

If your machine is stuck specifically on “Configuring Update 3 of 3 0% Completed”, the cause is different. A file called pending.xml in the Windows WinSxS folder incorrectly thinks it has updates waiting to be configured when it actually doesn’t. Renaming this file forces Windows to recreate it cleanly.

You will need your Windows installation media (USB stick or DVD) to access the Recovery Console for this fix.

Steps

1. Insert your Windows USB or DVD and boot from it (you may need to change boot order in BIOS)
2. At the Windows Setup screen, click Repair your computer
3. Click Troubleshoot → Advanced Options → Command Prompt

In the Command Prompt, type the following commands one at a time pressing Enter after each:

c:
cd windows
cd winsxs
ren pending.xml pending.old

Close the Command Prompt and restart your machine. Windows will recreate a fresh pending.xml and should boot straight into Windows without the stuck update screen.

Fix 3 — Force Immediate Shutdown to Bypass Update Screen

If you are repeatedly seeing “Configuring Windows Updates — Do Not Power Off Your Computer” on every shutdown but your machine is otherwise working fine, you can force an immediate shutdown that bypasses the update screen entirely.

Open Command Prompt and run:

shutdown /s /t 0

This forces Windows to shut down immediately. Note: This bypasses the problem but does not fix it — the update will likely try again next shutdown. Use Fix 1 for a permanent solution.

Fix 4 — Enterprise Fix for IT Admins (Multiple Machines)

If you work in IT and need to push this fix out to multiple machines across your estate, here are the enterprise options.

PowerShell Remote Fix

$computers = @("PC001","PC002","PC003")
foreach ($computer in $computers) {
    Invoke-Command -ComputerName $computer -ScriptBlock {
        Stop-Service wuauserv -Force
        Rename-Item "C:\Windows\SoftwareDistribution" "C:\Windows\SoftwareDistribution.old" -ErrorAction SilentlyContinue
        Start-Service wuauserv
        Write-Host "$env:COMPUTERNAME - Fixed" -ForegroundColor Green
    }
}

Replace the computer names with your own machine names or pull them from Active Directory. See our PowerShell Active Directory management guide for how to run this against a whole OU.

SCCM / Configuration Manager

This fix can be packaged and deployed as a Script or Task Sequence step in SCCM/ConfigMgr. Create a Run Script with the PowerShell commands above and target your affected collection. We have deployed this fix to thousands of machines this way.

Group Policy

Create a Computer Startup Script in Group Policy that runs the net stop/rename/net start commands as a batch file. This will run the fix automatically on next machine startup for all machines in the targeted OU.

Which Fix Should I Use?

Frequently Asked Questions

Glossary

Still Having Problems?

If none of the above fixes resolve your issue, try the built-in Windows Update Troubleshooter — go to Settings → Update & Security → Troubleshoot → Windows Update → Run the troubleshooter.

You can also run System File Checker to check for corrupt Windows system files:

sfc /scannow

And run the DISM tool to repair the Windows component store:

DISM /Online /Cleanup-Image /RestoreHealth

Leave a comment below with your specific error message and we will do our best to help. Include which version of Windows you are running and which fix you already tried.

About The Author

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Active Directory, PowerShell, and enterprise infrastructure. He founded TechyGeeksHome in 2010 and has published over 1,500 practical guides covering real-world IT problems and solutions. When not solving IT problems, Andrew develops free Windows utilities including Ultimate Settings Panel, which has been downloaded over 850,000 times.

See author's posts