Not All Updates Uninstalled? Fix It

When Windows says “not all of the updates were successfully uninstalled,” it usually means the removal process hit a snag—often a pending reboot, a corrupted update component, or a service that’s still holding onto files. This guide explains why the message appears and walks you through the reliable ways to finish the job, from using the built-in troubleshooting tools to manually clearing the update cache.

What “Not All Updates Were Uninstalled” Means

This message appears when you try to remove a Windows update (usually a cumulative or feature update) and the process doesn’t complete cleanly. The update may be partially removed—some files are gone, others remain—or the system may have rolled back to a previous state but left behind orphaned components. The most common causes are:

• A pending reboot that wasn’t performed before you tried to uninstall.
• Corrupted update cache files in the SoftwareDistribution folder.
• Windows Update service or Cryptographic service not running.
• Antivirus or third-party security software interfering with file changes.
• Insufficient disk space to complete the rollback.

In many cases, the update is actually uninstalled, but Windows still shows the error because it couldn’t clean up all the temporary files. The steps below will help you verify the status and finish the cleanup.

Why Does This Happen?

Windows updates are installed as packages that contain multiple components. When you uninstall, the system must reverse each change in a specific order. If any step fails—due to a locked file, a service hiccup, or a corrupted manifest—the entire operation is marked as incomplete. The error is Windows’ way of telling you that the uninstall didn’t fully succeed, even if the main update appears to be gone.

Another common scenario: you uninstall a cumulative update, but a later update that depends on it is still installed. Windows will refuse to remove the earlier one completely because that would break the later one. In that case, you need to uninstall the newer update first.

How to Fix It: Step-by-Step

Follow these steps in order. Stop after each one and check if the error is gone.

1. Restart your PC. A reboot clears file locks and pending operations. After restarting, go to Settings > Windows Update > Update history > Uninstall updates and try again.
2. Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters > Windows Update. Run it and follow the prompts.
3. Stop the Windows Update services and clear the cache. Open Command Prompt as administrator and run:
   net stop wuauserv
net stop cryptSvc
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
   Then restart the services with net start wuauserv, net start cryptSvc, net start bits. Try the uninstall again.
4. Use DISM and SFC to repair system files. In the same Command Prompt, run:
   DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
   Reboot and retry.
5. Uninstall in Safe Mode. Boot into Safe Mode (Settings > System > Recovery > Advanced startup), then go to Uninstall updates and remove the problematic update. Safe Mode prevents third-party software from interfering.
6. Use the Command Prompt to uninstall manually. If the update still won’t remove, find its KB number (from Update history) and run:
   wusa /uninstall /kb:KB1234567
   Replace with the actual KB number. Add /norestart if you want to reboot later.

How to Check If the Update Is Actually Gone

After a successful uninstall, the update should no longer appear in the “Installed updates” list (Control Panel > Programs > Programs and Features > View installed updates). You can also check the update history in Settings. If the update still shows as installed, the uninstall didn’t complete. If it’s gone but you still see the error, the issue is likely leftover cache—clearing the SoftwareDistribution folder as described above usually resolves it.

Common Mistakes to Avoid

• Not rebooting before uninstalling. Always restart after installing an update, even if Windows doesn’t force it.
• Uninstalling the wrong update. If you have multiple updates installed on the same day, double-check the KB number.
• Ignoring disk space. Windows needs free space to roll back. Ensure you have at least 10-15 GB free, especially for feature updates.
• Using third-party uninstallers. They can corrupt the update store. Stick to built-in methods.

When to Use System Restore or Reset

If the update won’t uninstall and your system is unstable, you have two stronger options:

• System Restore: If you have a restore point from before the update, you can roll back to it. Go to Control Panel > Recovery > Open System Restore. This removes the update and any other changes made after that point.
• Reset this PC: As a last resort, Settings > System > Recovery > Reset PC. Choose “Keep my files” to preserve personal data but reinstall Windows. This will remove all updates and give you a clean system.

Both methods are safe, but back up important files before attempting a reset.

Frequently Asked Questions

Why does the error appear even after a reboot?

A reboot clears file locks, but if the update components are corrupted or a service is stuck, the error persists. Running the Windows Update Troubleshooter and clearing the SoftwareDistribution folder usually resolves it.

Can I just ignore the error?

If the update is actually gone and your system works fine, you can ignore it. But if you see repeated errors or system instability, it’s best to fix it to avoid future update problems.

Will uninstalling an update break my other software?

Usually not, but if the update included security patches, uninstalling it may leave your system vulnerable. Only uninstall if you have a specific reason, like a driver conflict.

What if the update is a security patch—should I still uninstall it?

Security patches are important. If you must uninstall one to fix a problem, do so temporarily and then reinstall it after the issue is resolved. Use the same Uninstall updates page to reinstall.

How long should the uninstall take?

It can take anywhere from a few minutes to 30+ minutes, depending on the update size. If it takes longer than an hour, it may be stuck—force restart and try again.

Is there a way to prevent this error in the future?

Keep your system clean, ensure enough disk space, and always restart after updates. Also, avoid interrupting the uninstall process—let it finish completely.

Related

• iOS 27 Public Beta: What to Know
• 3D-Printed Porous Pills and Their Industrial Forecast
• How to Host Docker Containers on a VPS

in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2