Fix System Repair Pending Reboot Error

The “system repair pending which requires reboot” error appears when Windows has a pending repair operation that needs a restart to finish, but the restart either fails or the operation gets stuck. The fix is to either complete the reboot properly, clear the pending state, or repair the Windows Update components—and this article walks through each method in order.

What Causes the Pending Repair State

Windows marks a repair as “pending” when it has staged changes that must be applied during the next boot. This happens most often after a Windows Update, a .NET Framework installation, or a system file repair (like sfc /scannow or DISM). The system sets a flag in the registry that tells the boot process to finish the operation. If the reboot is interrupted, the flag stays, and every subsequent attempt to install or repair anything is blocked with the same message.

Common triggers include:

• Windows Update that downloaded but didn’t install completely
• A failed .NET Framework update
• An interrupted dism /online /cleanup-image /restorehealth command
• Third-party software that modifies system files and then requests a restart

First: Let Windows Finish the Reboot

Before doing anything drastic, try a clean restart. Sometimes the pending operation just needs a normal reboot that isn’t interrupted by fast startup or a stuck app. Go to Start > Power > Restart (not Shut down, because Windows 10 and 11 use fast startup by default, which can skip the pending operation). If the restart works, the error disappears. If it doesn’t, move on to the next step.

Use the Pending.xml Rename Method

Windows keeps a list of pending operations in a file called Pending.xml located in C:\Windows\WinSxS. Renaming this file clears the pending flag. This is a common fix, but it can leave the system in an inconsistent state, so only do it after you’ve tried a normal reboot.

1. Boot into Safe Mode (hold Shift while clicking Restart, then go to Troubleshoot > Advanced Options > Startup Settings).
2. Open Command Prompt as administrator.
3. Type cd C:\Windows\WinSxS and press Enter.
4. Type ren Pending.xml Pending.old and press Enter.
5. Restart normally.

If the file doesn’t exist, the pending state may be stored in the registry instead. In that case, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager. Look for a value called PendingFileRenameOperations and delete it. Back up the registry first, and be careful—this can cause issues if the operation was important.

Repair Windows Update Components

If the pending state is tied to a failed Windows Update, you need to reset the update components. This is more thorough than renaming Pending.xml and often fixes the root cause. Run these commands in an elevated Command Prompt, one at a time:

1. net stop wuauserv (stops Windows Update)
2. net stop cryptSvc (stops cryptographic services)
3. net stop bits (stops Background Intelligent Transfer)
4. net stop msiserver (stops Windows Installer)
5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
6. ren C:\Windows\System32\catroot2 catroot2.old
7. net start wuauserv, net start cryptSvc, net start bits, net start msiserver

This resets the update cache and forces Windows to re-download updates. After that, restart and try installing updates again.

Run DISM and SFC in the Right Order

Corrupted system files can also cause a stuck pending state. The correct order is to run DISM first, then SFC. DISM repairs the system image that SFC relies on. In an elevated Command Prompt:

1. dism /online /cleanup-image /restorehealth
2. After it finishes, sfc /scannow

If DISM fails because of the pending state, you may need to use the /startcomponentcleanup option or run it from the Windows Recovery Environment. In some cases, you can use dism /online /cleanup-image /startcomponentcleanup to clear superseded components that might be blocking the repair.

When to Use System Restore or Startup Repair

If the above steps don’t work, the pending state might be a symptom of a deeper issue. System Restore can roll back to a point before the pending operation was created. Boot into Safe Mode or the Recovery Environment and choose System Restore. Pick a restore point from before the error started.

Startup Repair is another option. From the Recovery Environment, go to Troubleshoot > Advanced Options > Startup Repair. This scans for issues that prevent Windows from booting correctly and can clear stuck states. It doesn’t affect personal files, but it may remove recently installed updates.

What If Nothing Works?

If all fixes fail, the last resort is to reset Windows or reinstall it. A reset keeps your personal files but removes installed apps and settings. Go to Settings > Update & Security > Recovery > Reset this PC (Windows 10) or Settings > System > Recovery > Reset this PC (Windows 11). Choose “Keep my files” to avoid data loss. This will almost certainly clear the pending state because it rebuilds the system files from scratch.

Before resetting, back up your data to an external drive. Also, consider creating a system image or a full backup so you can restore if the reset doesn’t solve the problem.

Frequently Asked Questions

Is it safe to delete Pending.xml?

Generally yes, but it can leave the system with partially applied updates. Only do it after trying a normal reboot and a clean boot. If you’re not comfortable with it, use the Windows Update reset method instead, which is safer.

Why does the error appear even after a reboot?

Fast startup can skip the pending operation. Use Restart instead of Shut down, or disable fast startup in Control Panel > Power Options > Choose what the power buttons do. If that doesn’t help, the pending operation itself is corrupted.

Can I ignore the error and continue using my PC?

You can, but Windows Update and some installers will keep failing. The longer you wait, the more updates pile up, and the system may become unstable. It’s best to fix it before installing anything else.

Will this fix delete my files?

No. None of the steps in this article delete personal files. The only step that might is the last-resort reset, and even then you can choose to keep your files.

Does this error happen on Windows 7 or 8?

Yes, the same error can occur on older versions. The steps are similar, but the menu names differ slightly. On Windows 7, use the System Recovery Options from the installation disc. The Pending.xml method and DISM/SFC commands work the same.

Related

• Transfer SMS from Sony to iPhone: Full Guide
• Fix iTunes Error 5105 on Windows: Request Cannot Be Processed
• Learn Raspberry Pi on Your Computer First