Skip to main content
If a Windows Server update is stuck on “Getting Windows ready. Don’t turn off your computer” or “Working on updates”, it is usually still installing: large updates take a long time, so wait before you restart. If updates fail with an error code, free disk space on C:, repair the component store with DISM.exe /Online /Cleanup-image /Restorehealth and sfc /scannow, then reset Windows Update by stopping wuauserv, bits and cryptsvc and renaming the SoftwareDistribution and catroot2 folders.

​
Before you start

  • To see a server that is restarting, use the VNC console; RDP isn’t available during that stage. On a dedicated server, open a ticket if you need console access.
  • Take a backup or snapshot before resetting update components.

​
Cause 1: the update is still installing (stuck at restart)

Microsoft explains that this screen appears during the final restart after updates or role changes, and that “if the updates were large, the operating system needs more time to reconfigure the changes”. Check: watch the console. A percentage that still moves, or disk activity on the resource graphs, means it is working. Fix: wait. Cumulative updates can take a long time on a server with few CPU cores or little RAM.
Forcing a power off during “Working on updates” can leave Windows unbootable. Only restart from the panel if nothing has changed for several hours. If Windows then doesn’t start, see Windows Server not booting.

​
Cause 2: not enough free disk space

Check:
Errors such as 0x80071AB1 (transaction log full) point to a full drive. Fix: free space first; see free up disk space on Windows Server. Then try the update again.

​
Cause 3: the component store is corrupted

Check: the update fails with an error such as 0x80073712 (component store inconsistent), 0x800f0831 (CBS store corrupted) or 0x800f081f (source files not found). Fix: in an elevated Command Prompt:
Restart and try the update again. If DISM can’t find source files, use an ISO as described in repair Windows with SFC and DISM.

​
Cause 4: Windows Update components are broken

Check: downloads never progress, the update search never finishes, or the same update fails again after the DISM repair. Fix: reset the Windows Update components. In an elevated Command Prompt:
1

Stop the update services

2

Rename the update caches

Windows creates new, empty folders. Renaming keeps the old ones in case you need them.
3

Start the services again

4

Search for updates again

Run SConfig, choose 6 (Install updates) and 1 (All quality updates), or use Settings > Windows Update (on Windows Server 2019 and 2022: Settings > Update & Security > Windows Update).

​
Cause 5: the Windows Update service is disabled

Check: error 0x8024002E (Windows Update client service is disabled), or:
Fix: if wuauserv shows Disabled, set it back to manual start and try again:

​
How to read the update logs

Search the log for the error code you saw, for example 0x80073712.

​
How to check it worked

Run Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 3. The update you installed appears with today’s date. Windows Update in Settings shows no pending errors.

​
Frequently asked questions

​
How long should “Working on updates” take?

There is no fixed time. Microsoft only says large updates need more time. As long as the percentage or the disk activity still changes, let it run.

​
Can I delete the whole SoftwareDistribution folder?

Microsoft offers that as a last-resort reset (rd /s /q %systemroot%\SoftwareDistribution with wuauserv stopped). Try the rename method first.

​
How do I stop updates restarting the server at a bad time?

In SConfig, choose 5 (Update setting) and pick M (manual) or D (download only). See install Windows updates on Windows Server.

VPS and dedicated server guides

Every guide in this section.

Install Windows updates

SConfig, Settings and PowerShell.

Repair with SFC and DISM

Fix corruption errors.

Free up disk space

Make room for updates.

Windows Server not booting

When a restart goes wrong.
Checked against Microsoft Learn: Fix Windows Update corruptions, Additional resources for Windows Update, Troubleshoot Windows Update failures, Stuck on “Getting Windows ready” and SConfig on 4 November 2026. Commands were not tested on a live Windows server for this page.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026