sodcalculator

10 Tech How-To

Failure Configuring Windows Updates Reverting Changes Error Fixed

Guide 10-12233 · Updated · Step by step

Yes, the “Failure configuring Windows updates. Reverting changes” error can be fixed, usually by clearing the Windows Update cache, running the built-in DISM and SFC repair tools, or temporarily disabling third-party antivirus software. This guide walks through the most effective fixes in order, from least to most invasive, so you can get your PC booting and updating normally again.

What Causes This Error?

This error appears when Windows tries to install updates but fails partway through, then rolls back the changes. It typically happens after a reboot, and the system may loop through “Configuring updates” and “Reverting changes” several times before landing on the login screen. Common causes include:

  • Corrupted update files or a damaged Windows Update database
  • Conflicts with third-party antivirus or security software
  • Insufficient disk space for the update to install
  • Outdated or incompatible drivers, especially storage or graphics drivers
  • System file corruption from a previous failed update or crash

Understanding the root cause helps you choose the right fix—most users resolve it with the first few steps below.

Before You Start: Boot into Safe Mode

Some fixes require you to be at a normal Windows desktop. If the error loop prevents that, boot into Safe Mode:

  1. Restart your PC. When the Windows logo appears, press and hold the power button to force shutdown. Repeat this 3 times.
  2. On the third restart, Windows should enter the Recovery Environment. Choose Troubleshoot → Advanced options → Startup Settings → Restart.
  3. After restart, press 4 or F4 to boot into Safe Mode.

Once in Safe Mode, you can run the following commands and tools with minimal interference from background processes.

Fix 1: Run DISM and SFC

Corrupted system files are a leading cause of update failures. The Deployment Imaging Service and Management Tool (DISM) repairs the Windows image, and the System File Checker (SFC) fixes corrupted system files. Run both in order:

  1. Open Command Prompt as administrator (right-click Start → Command Prompt (Admin) or Windows PowerShell (Admin)).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth. This may take 15–30 minutes. Do not close the window.
  3. Once DISM finishes, run sfc /scannow. This also takes time.
  4. Restart your PC and try updating again.

If DISM reports an error, you may need to specify a valid repair source. In most cases, the online repair works. If not, you can try using the Windows installation media as a source, but that is more advanced.

Fix 2: Clear the Windows Update Cache

Sometimes the downloaded update files are corrupted. Clearing the cache forces Windows to re-download them. This is safe and often resolves the issue:

  1. Open Command Prompt as administrator.
  2. Stop the update services by running these commands one by one:
    • net stop wuauserv
    • net stop cryptSvc
    • net stop bits
    • net stop msiserver
  3. Rename the SoftwareDistribution folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  4. Rename the catroot2 folder: ren C:\Windows\System32\catroot2 catroot2.old
  5. Restart the services by running the same commands with net start instead of net stop.
  6. Restart your PC and try Windows Update again.

This clears the downloaded update files and the update database, so Windows starts fresh.

Fix 3: Temporarily Disable Antivirus and Third-Party Security Software

Antivirus programs can interfere with update installation, especially if they lock system files. To test this:

  1. Right-click the antivirus icon in the system tray and choose Disable or Pause protection.
  2. Try installing the updates again.
  3. If it works, re-enable the antivirus immediately.

If disabling helps, consider adding an exception for Windows Update folders or switching to a different security tool. Windows Defender (built-in) rarely causes this issue, so the culprit is usually a third-party product.

Fix 4: Free Up Disk Space

Windows updates need several gigabytes of free space. If your system drive is nearly full, updates may fail. Use the Disk Cleanup tool:

  1. Open This PC, right-click your system drive (usually C:), and select Properties.
  2. Click Disk Cleanup, then Clean up system files.
  3. Check all categories, especially Windows Update Cleanup and Temporary files, then click OK.
  4. Consider moving personal files to another drive or an external storage device.

Aim for at least 20 GB free on the system drive for major feature updates.

Fix 5: Use the Windows Update Troubleshooter

Windows includes a built-in troubleshooter that can automatically detect and fix common update problems:

  1. Open Settings → Update & Security → Troubleshoot (or System → Troubleshoot on Windows 11).
  2. Select Windows Update and click Run the troubleshooter.
  3. Follow the on-screen instructions. It may take a few minutes.

This tool resets update components automatically and is worth trying before more drastic measures.

Fix 6: Reset Windows Update Components Manually

If the troubleshooter doesn’t work, you can manually reset all update components. This is a more comprehensive version of clearing the cache:

  1. Open Command Prompt as administrator.
  2. Run the following commands in order:
    • net stop wuauserv
    • net stop cryptSvc
    • net stop bits
    • net stop msiserver
    • ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    • ren C:\Windows\System32\catroot2 catroot2.old
    • net start wuauserv
    • net start cryptSvc
    • net start bits
    • net start msiserver
  3. Restart your PC.

This is essentially the same as Fix 2 but also resets the cryptographic services, which can help if the update signature verification fails.

Fix 7: Perform a Repair Upgrade (In-Place Upgrade)

If nothing else works, a repair upgrade reinstalls Windows while keeping your files and installed programs. This is more involved but often fixes deep system corruption:

  1. Download the Windows Media Creation Tool from Microsoft’s official website.
  2. Run the tool and select Upgrade this PC now.
  3. Follow the prompts, choosing to keep personal files and apps.
  4. The process will take an hour or more and will restart your PC several times.

This is not a full reset—it preserves your data and applications. It’s a safe last resort before a clean install.

Frequently Asked Questions

Will I lose my files if I use these fixes?

No. All the fixes above, including the repair upgrade, are designed to preserve your personal files and installed programs. Only a full reset or clean install would remove everything, and that’s not recommended unless you’ve exhausted all other options.

How long does the “reverting changes” phase take?

It can take anywhere from 5 to 30 minutes. If it’s stuck for over an hour, force a restart and boot into Safe Mode to run the repair tools. Patience is key—interrupting the process can cause more corruption.

Can I skip a problematic update?

Yes, you can pause updates for up to 35 days in Windows 10/11 (Settings → Windows Update → Pause updates). For a specific update, you can hide it using the “Show or hide updates” troubleshooter from Microsoft, but that’s a temporary workaround, not a permanent fix.

Why does this error keep happening after I fix it?

If the error recurs, the underlying cause is likely persistent—such as a failing hard drive, incompatible driver, or a hardware issue. Run chkdsk /f to check for disk errors, and update your drivers from the manufacturer’s website. If it continues, consider a repair upgrade or clean install.

Is it safe to use third-party tools to fix Windows Update?

Many third-party tools claim to fix update issues, but they can be risky. Stick to built-in tools (DISM, SFC, troubleshooter) and official Microsoft guidance. If you do use a third-party tool, ensure it’s from a reputable source and read reviews carefully.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →