RackNerd Billboard Banner

How to Fix “There Is a System Repair Pending” Error in Windows

If you’ve tried to run SFC /scannow or DISM on your Windows PC and hit the wall with this frustrating message:

“There is a system repair pending which requires reboot to complete.”

Don’t worry—you’re not alone, and the fix is within reach. This error usually pops up when a previous repair operation didn’t finish properly. Windows gets stuck in a loop, thinking a repair is still pending—even after rebooting.

Here’s how to fix it step by step.


🔧 Solution 1: Delete the Pending.xml File

  1. Open Command Prompt as Administrator
    Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Navigate to the System32 folder cd %windir%\winsxs
  3. Delete the pending.xml file (if it exists) del pending.xml If the file is not found, that’s okay—move on to the next fix.

🔧 Solution 2: Use the Revertpendingactions Command

This command tells Windows to cancel any repair actions that are stuck in limbo.

  1. In the Command Prompt, type: dism.exe /image:C:\ /cleanup-image /revertpendingactions 🔎 Make sure *C:* is your system drive. If Windows is installed on a different drive, change the letter accordingly.
  2. Reboot your PC and try running SFC /scannow again.

🔧 Solution 3: Boot Into Windows Recovery Environment (WinRE)

If you’re locked out or the above doesn’t work:

  1. Boot from a Windows installation USB or recovery disk.
  2. Select Repair your computer > Troubleshoot > Command Prompt.
  3. Follow Solution 1 or 2 from this Command Prompt window.

✅ Bonus Tip: Run System File Checker and DISM Again

Once you’ve cleared the error, re-run:

sfc /scannow

And then:

DISM /Online /Cleanup-Image /RestoreHealth

These will check and fix any lingering corruption in your system files.


🧠 Final Thoughts

The “System Repair Pending” error is annoying, but it’s not a dead end. These fixes reset the stuck repair process and get Windows back on track. If the error keeps coming back, it might point to deeper system corruption or failing hardware—so consider a full backup and clean install if all else fails.

Got stuck? Drop a comment below, and I’ll help you troubleshoot.

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
RackNerd Billboard Banner
0
Would love your thoughts, please comment.x
()
x
Copy link