Skip to content
WinBookUnofficial

Windows Update stuck or rolling back: read the logs before deleting folders

Verified 2 min read

Diagnose Windows 11 26H2 update failures with update history, WindowsUpdate.log, CBS/DISM logs and the common 0x800… codes, without destructive folder deletion.

Tested onPro (26H2) · Build 26300.9457 · x64
E1
Build
26300.9457
Edition
Pro (26H2)
Architecture
x64
Support
Documentation (E1)
Evidence
E1Official documentation
Verified
2026-10-28
Page type
Troubleshoot

The short answer

Section titled “The short answer”

Do not start by deleting SoftwareDistribution and catroot2. First identify which update, which stage and which error code failed.

A stuck update is usually one of:

  • a download/cache problem;
  • a servicing-stack/component-store problem;
  • a driver/firmware conflict;
  • not enough free disk space;
  • a policy/WSUS/Intune conflict.

The logs tell you which.

1. Record the state

Section titled “1. Record the state”
Terminal window
winver
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
Get-WinEvent -LogName System -MaxEvents 100 |
  Where-Object ProviderName -match 'WindowsUpdate|Servicing'

Also check Settings → Windows Update → Update history for the failed KB and error code.

2. Read the right logs

Section titled “2. Read the right logs”
Log What it answers
Windows Update history Which KB/error code
%windir%\Logs\WindowsUpdate Download/install orchestration
CBS.log Component servicing failures
DISM.log Image servicing operations
Event Viewer → System Reboots, service crashes, disk errors
Get-WindowsUpdateLog Merges ETW into a readable log

Get-WindowsUpdateLog writes to the desktop by default; it can take a minute. Read the tail and search for the failed KB/error code.

3. Common patterns

Section titled “3. Common patterns”
Symptom Likely area First move
0x800f081f Component store/source missing DISM /RestoreHealth with a source
0x80070070 Disk space Free space, then retry
0x80070643 Installer/.NET/servicing Check the specific KB notes
0x8024xxxx Download/WSUS/network Check proxy/WSUS/policy
Reboot loop after update Driver/firmware or incomplete servicing WinRE, uninstall latest update
Stuck at “Downloading 0%” Network/cache Check proxy/DNS first

Do not treat one code as one universal fix. The same code can have different causes on different builds.

4. Safe repair order

Section titled “4. Safe repair order”
  1. Free at least 20–30GB on C:.
  2. Reboot, retry once.
  3. Run the Windows Update troubleshooter.
  4. DISM /Online /Cleanup-Image /CheckHealth, then /ScanHealth, then /RestoreHealth if needed.
  5. sfc /scannow after DISM.
  6. Retry the update.
  7. Only then reset the update cache.

5. If it rolls back every time

Section titled “5. If it rolls back every time”
  • Note the exact KB and whether it is a cumulative, .NET or driver update.
  • Check the KB’s known-issues section.
  • Remove third-party AV/anti-cheat temporarily only if the vendor documents a conflict.
  • Check free space and file-system health (chkdsk /scan).
  • If the machine cannot boot, use WinRE → Uninstall Updates / System Restore.

Sources