Interactive Troubleshooter

Published: Sep 2, 2026

Windows 12 Update Loop: Fix Without Data Loss

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Diagnose and resolve infinite update reboot loops in Windows 12 caused by corrupted cache, driver conflicts, or broken system files. Complete interactive recovery guide to restore your PC safely without losing personal data.

Full Diagnostic Tree & Step-by-Step Overview

What exact screen or behavior is your Windows 12 PC stuck on during the update loop?

Stuck at a percentage screen (e.g., 'Updating... 35%') or 'Undoing changes' on boot
Repeatedly reboots before reaching the desktop or crashes with a BSOD during boot
Boots into desktop, but repeatedly prompts to restart to update and fails every time

How long has the update screen been frozen or cycling?

Frozen at a specific percentage or 'Undoing changes' for over 1-2 hours
Cycles endlessly through 'Preparing Automatic Repair' after failing the update

Purge SoftwareDistribution & Catroot2 Cache in Safe Mode

Solution:

Root Cause: Corrupted SoftwareDistribution & Catroot2 Cache

When Windows 12 downloads or stages an update payload, corrupted installation files or interrupted network downloads can lock the installer service into an unresolvable staging loop during startup.

Step-by-Step Fix:

1.Force Hard Reset into Advanced Startup:

Hold down the Power button for 10 seconds to force shut down your PC.

Power on, and as soon as the Windows logo appears, press and hold the Power button again to interrupt boot.

Repeat this 3 times until the Preparing Automatic Repair screen appears.

Select Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.

Press 4 or F4 to boot into Safe Mode.

2.Clear the SoftwareDistribution & Catroot2 Cache:

Press Win + X and open Terminal (Admin) or Command Prompt (Admin).

Stop the core update services by executing:

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

Rename the update cache folders to force Windows to rebuild them:

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

Restart the stopped services:

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

3.Reboot and Resume Normal Boot:

Restart your PC normally. Windows 12 will generate clean update folders and exit the loop without impacting personal files.

Revert Pending Update Actions via WinRE Command Prompt

Solution:

Root Cause: Pending Transaction Lock in Component Store (CBS)

An interrupted system update leaves pending flags in the Boot Configuration Data (BCD) and Component-Based Servicing (CBS) queue, forcing WinRE into an endless Automatic Repair loop.

Step-by-Step Fix:

1.Access WinRE Command Prompt:

Interrupt boot 3 times using the Power button to trigger Automatic Repair.

Navigate to Troubleshoot > Advanced options > Command Prompt.

2.Remove Pending Update Executions via DISM:

Identify your main OS drive letter by typing dir C: or dir D:.

Execute the following DISM command to revert pending update actions:

cmd
     dism /image:C:\ /cleanup-image /revertpendingactions

*(Replace C: with your actual OS drive letter if different)*.

3.Rebuild Boot Configuration Data (BCD):

Run the following boot repair commands sequentially:

cmd
     bootrec /fixmbr
     bootrec /fixboot
     bootrec /rebuildbcd

4.Exit and Reboot:

Type exit and click Continue to Windows 12.

Does the PC throw a specific error code or crash during the reboot sequence?

BSOD error like PAGE_FAULT_IN_NONPAGED_AREA or INACCESSIBLE_BOOT_DEVICE during boot
Infinite restart loop without any BSOD or visible error screen

Roll Back Conflicting Drivers or Uninstall Recent Cumulative Update

Solution:

Root Cause: Incompatible Third-Party Driver or Security Kernel Conflict

A low-level driver or third-party security software installed immediately prior to the Windows 12 update causes a kernel panic (BSOD) during post-update device initialization.

Step-by-Step Fix:

1.Boot into Safe Mode with Networking:

Force restart 3 times to enter Automatic Repair.

Go to Troubleshoot > Advanced options > Startup Settings > Restart.

Press 5 or F5 to select Safe Mode with Networking.

2.Uninstall Recent Cumulative Update Package:

Open Settings > Windows Update > Update history > Uninstall updates.

Locate the most recent Quality or Cumulative Update and click Uninstall.

3.Roll Back Recent Hardware Drivers:

Right-click the Start menu and select Device Manager.

Expand Display adapters or Storage controllers.

Right-click the primary device, select Properties, switch to the Driver tab, and click Roll Back Driver.

4.Restart System Normally:

Reboot your PC to verify the BSOD loop is resolved.

Perform Offline SFC and DISM Component Store Repair

Solution:

Root Cause: System File Corruption & POQ Queue Lock

The Component-Based Servicing (CBS) engine failed to register update transactions, leaving orphaned Primitive Operations Queue (POQ) entries that trigger a reboot before system initialization finishes.

Step-by-Step Fix:

1.Open WinRE Command Prompt:

Trigger Automatic Repair via 3 forced power-offs.

Navigate to Troubleshoot > Advanced options > Command Prompt.

2.Run Offline SFC & DISM Repairs:

Verify your Windows drive letter (typically C:).

Execute the System File Checker targeting offline system directories:

cmd
     sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

Execute DISM component store repair:

cmd
     dism /image:C:\ /cleanup-image /restorehealth

3.Reboot the System:

Type exit and click Continue to boot normally into Windows 12.

What happens when you manually attempt to complete or stop the update from Settings?

Windows Update throws error codes like 0x800f0922 or 0x80070002 in Settings
Update downloads and installs to 100%, but fails upon required reboot

Reset Windows Update Components and Network Sockets

Solution:

Root Cause: Corrupted Windows Update Database & Socket Mismatch

Windows Update background services (wuauserv, CryptSvc, BITS) have encountered internal database sync mismatches, causing persistent download/apply failures while logged in.

Step-by-Step Fix:

1.Run Built-in Update Troubleshooter:

Go to Settings > System > Troubleshoot > Other troubleshooters.

Locate Windows Update and click Run.

2.Reset Network Sockets and IP Stack:

Open Terminal (Admin).

Execute the following commands sequentially:

cmd
     netsh winsock reset
     netsh int ip reset
     ipconfig /flushdns

3.Re-register Core Update DLL Files:

In the same admin terminal, execute:

cmd
     regsvr32.exe /s atl.dll
     regsvr32.exe /s urlmon.dll
     regsvr32.exe /s mshtml.dll

4.Restart PC:

Reboot your system and check for updates again in Settings.

Free System Reserved Space and Perform In-Place Upgrade

Solution:

Root Cause: Insufficient System Reserved / EFI Partition Space

Windows 12 updates require unallocated space in the System Reserved / EFI system partition to extract bootloader updates. If full, the installation rolls back after reboot.

Step-by-Step Fix:

1.Clean Up System Update Storage:

Press Win + R, type cleanmgr, select drive C:, and click OK.

Click Clean up system files.

Check Windows Update Cleanup, Temporary Windows Installation Files, and Delivery Optimization Files.

Click OK to purge cached installer data.

2.Perform an In-Place Upgrade via Windows 12 ISO:

Download the official Windows 12 Media Creation Tool or ISO from Microsoft.

Right-click the ISO file and select Mount.

Run setup.exe inside the virtual drive.

Select Keep personal files and apps when prompted.

This replaces corrupted OS files and completes the update without deleting personal data.

Related Diagnostic Guides

Windows 11 Wi-Fi Connected but No Internet? How to Fix It

Google Account Suspicious Activity? How to Check for Unknown Devices

Microsoft Account Hacked? How to Recover and Secure Your Account

Fast Charging Not Working? How to Check USB PD and Quick Charge Support

Laptop Using Integrated Graphics Instead of Dedicated GPU? Here's How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website