Over the past 15 years working with Windows Update issues remotely, I've found that error 0x80070652 ('ERROR_INSTALL_ALREADY_RUNNING') is almost always fixable without a complete system reinstall. The real fix is simpler than most forum threads suggest once you understand what's actually happening under the hood.
TL;DR
Error 0x80070652 means Windows Update is blocked because another installation is already running or stuck. Quick fix: restart your computer, run Windows Update Troubleshooter (Settings > Troubleshoot > Windows Update). If that fails, open Command Prompt as Admin and run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver, then rename the SoftwareDistribution and Catroot2 folders, restart the services, and reboot. This clears corrupted cache files that block updates. Success rate: 75 to 85% for persistent cases.
Key Takeaways
- Error 0x80070652 is caused by stuck Windows Installer processes or corrupted update cache files, not by your hardware or internet connection
- A simple restart fixes about 60% of cases, but corrupted cache files require you to reset the SoftwareDistribution folder
- Windows Update services are safe to stop temporarily using command-line tools, and Microsoft recommends this for troubleshooting
- If basic and intermediate fixes fail, system file corruption may be the culprit, run System File Checker (sfc /scannow) to repair it
- Always complete pending restarts before attempting new updates to prevent this error from recurring
At a Glance
- Difficulty: Intermediate
- Time Required: 15 to 45 minutes depending on solution
- Success Rate: 60% quick fix, 80% with intermediate steps, 90% with advanced repair
What Causes Windows Update Error 0x80070652?
When you see error 0x80070652, Windows is essentially saying: 'I can't start a new installation because another one is already in progress.' Sounds straightforward, but there are five distinct reasons this message appears, and they require different fixes.
The most common culprit is an active or stuck msiexec.exe process. This is the Windows Installer service, and it's responsible for managing installations of Windows itself, updates, software, and drivers. When you start a Windows Update, msiexec.exe runs in the background. Normally it finishes and closes itself within minutes. But if the update is interrupted, your system crashes, or the process gets hung on a waiting state, msiexec.exe stays running. Windows Update sees this and refuses to start a second installation, hence the 0x80070652 error.
The second major cause is corrupted cache files in your SoftwareDistribution folder. This folder lives at C:\Windows\SoftwareDistribution and stores temporary update files, metadata, and download history. If an update is interrupted mid-download, or if your hard drive experiences read/write errors, files in this folder can become corrupted. Windows Update tries to use these files, fails, and gets stuck in a loop. The Catroot2 folder (at C:\Windows\System32\catroot2) stores cryptographic certificates for update verification, if these files corrupt, Windows can't validate whether updates are genuine, blocking the entire process.
Less commonly, a pending restart hasn't been completed. After many updates install, Windows requires a restart to finalize configuration changes. If you've ignored those restart prompts and tried to install a new update without rebooting, Windows blocks you. It's a safety mechanism: installing on top of an incomplete previous update can cause serious system instability.
System-level corruption, damaged files in critical Windows components like the Windows Update service (wuauserv), Background Intelligent Transfer Service (BITS), or Cryptographic Service (cryptSvc), can also trigger this error. These services manage the download, verification, and installation of updates. If they're damaged, they can't communicate properly, and installations hang.
Finally, third-party interference is less common but worth mentioning. Aggressive antivirus software, security suites, or outdated drivers can lock update-related files, preventing Windows from accessing them, or they can consume system resources heavily enough that installation processes time out.
Windows Update Error 0x80070652 Quick Fix
Restart and Run Troubleshooter Easy
- Save your work and restart your computer.
Click Start > Power > Restart. Wait for a full shut-down and boot cycle. Fast Startup won't do here, you need a proper cold restart to clear memory-resident processes. This takes about 2 minutes. - Check for pending restarts.
Go to Settings > Windows Update (Windows 11) or Settings > Update & Security > Windows Update (Windows 10). Scroll down. If you see 'Restart needed' or a blue 'Restart now' button, click it immediately and let the system reboot fully. Don't skip this step, pending restarts are a common blocker for new updates. - Run Windows Update Troubleshooter.
Open Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10). Find 'Windows Update' and click 'Run'. Let it complete, this usually takes 3 to 5 minutes. It will automatically fix common issues like service misconfigurations. - Attempt Windows Update again.
Navigate back to Settings > Windows Update and click 'Check for updates'. Try to install the update that previously failed with 0x80070652.
More Windows Update Error 0x80070652 Solutions
If the restart and troubleshooter didn't resolve it, the issue is likely corrupted cache files or a stuck installer process that survives reboots. This is where you need to get hands-on with Windows services.
Terminate Installer Processes and Reset Update Cache Intermediate
- Open Task Manager and end any msiexec.exe processes.
Press Ctrl+Shift+Esc to open Task Manager. Click the 'Details' tab (if you see a 'Processes' tab, click 'More details' first). Scroll down and look for any processes named 'msiexec.exe'. If you find any, right-click each one and select 'End task'. Click 'End process' if prompted. You should see 0 msiexec.exe processes after this, if you see any still running after ending them once, Windows has restarted them, which means a stuck installation is actively running. In that case, end the task again immediately. - Create a System Restore point as a safety net.
Press Windows key, type 'restore point', press Enter. Click 'Create' and follow the prompts. This takes 1 to 2 minutes. You now have a snapshot to roll back to if anything goes wrong in the next steps. - Open Command Prompt as Administrator.
Press Windows key, type 'cmd', then right-click 'Command Prompt' and select 'Run as administrator'. Click 'Yes' on the User Access Control prompt. You now have a black window with administrator privileges. - Stop Windows Update-related services.
In Command Prompt, type each command below, press Enter, and wait for a 'success' message before moving to the next one:net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver
Each should report 'The [service name] service was stopped successfully.' If one reports 'The service has not been started' or 'The specified service does not exist', that's fine, just move on. You're halting all background update processes to allow safe file operations. - Rename the corrupted cache folders.
Still in Command Prompt, execute:ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 Catroot2.old
These commands rename the folders instead of deleting them, in case Windows needs to reference them later. You should see no output, that's normal and means the rename succeeded. Windows will create fresh folders with the original names when services restart. - Restart the services.
Now execute these commands to bring services back online:net start wuauservnet start cryptSvcnet start bitsnet start msiserver
Again, wait for success messages. If one service fails to start, try the command again. Close Command Prompt once all four have started. - Restart your computer.
Click Start > Power > Restart. Allow a full reboot. This gives Windows time to initialize the fresh cache folders and re-register service components. - Check for Windows Updates.
Once booted, go to Settings > Windows Update and click 'Check for updates'. Attempt to install the update. Error 0x80070652 should be resolved, the fresh cache folder will allow Windows Update to download and verify updates cleanly.
This intermediate solution works in about 75 to 85% of persistent cases. The reason it's so effective is that you're removing the corrupted files that Windows Update relies on, forcing it to rebuild them from scratch. It's like clearing your browser cache, sometimes the old data gets corrupted and preventing fresh downloads.
Advanced Windows Update Error 0x80070652 Fixes
If you're still seeing 0x80070652 after the intermediate solution, you're dealing with deeper system file corruption. This is rare but does happen, especially after system crashes, power failures, or hardware issues. The advanced route involves scanning and repairing core Windows files, then optionally performing a Clean Boot to isolate third-party interference.
System File Repair and Clean Boot Diagnosis Advanced
- Run System File Checker (SFC) to scan for corruption.
Open Command Prompt as Administrator (Windows key > 'cmd' > right-click > 'Run as administrator'). Execute:sfc /scannow
This command scans all protected Windows system files and automatically repairs any it finds corrupted. It takes 15 to 30 minutes and will show a progress bar. Do not close the window or interrupt the scan. Once finished, review the output. If it says 'Windows Resource Protection found corrupt files and successfully repaired them,' you've found the culprit. Restart your computer and test Windows Update again. - Run DISM to repair the Windows component store.
If SFC didn't find corruption, or if Windows Update still fails after the repair, open Command Prompt as Administrator again and execute:DISM /Online /Cleanup-Image /RestoreHealth
DISM scans deeper into the Windows component store and can repair damage that SFC misses. This requires an active internet connection and takes 10 to 30 minutes. Wait for it to reach 100%. If DISM reports that it successfully repaired the image, restart and test Windows Update. - Perform a Clean Boot to isolate third-party interference.
If you're still seeing error 0x80070652 after SFC and DISM, a third-party application or service may be interfering. Press Windows+R, type 'msconfig', press Enter. Click the 'Services' tab. Tick the box labeled 'Hide all Microsoft services' at the bottom. Now click 'Disable all', this disables all non-Microsoft background services. Click the 'Startup' tab at the top, then click 'Open Task Manager'. In Task Manager, disable all startup items by right-clicking each one and selecting 'Disable'. Close Task Manager and click 'OK' in msconfig. Restart your computer. - Test Windows Update in Clean Boot mode.
Once rebooted in Clean Boot, navigate to Settings > Windows Update and attempt to install the failing update. If it succeeds in Clean Boot, a third-party service or startup item is the culprit. If it still fails, the issue is system-level, and you may need to consider an in-place upgrade repair or clean Windows installation. - Identify the conflicting software (if Clean Boot succeeded).
Return to msconfig and gradually re-enable services and startup items in groups of 5 to 10, restarting and testing Windows Update after each group. When the error 0x80070652 returns, you've found the group containing the culprit. Narrow it down further by testing items one at a time. Once you identify the specific application or service, update it, reconfigure it, or uninstall it if it's no longer needed. - Restore normal boot configuration.
Once resolved, return to msconfig. Untick 'Hide all Microsoft services'. Click 'Enable all' to re-enable services. Go to the 'Startup' tab, open Task Manager, and re-enable necessary startup items (be selective, avoid items you don't recognize). Click OK and restart normally.
If even the advanced solution doesn't work, you're likely facing one of two scenarios: either your Windows installation is severely corrupted beyond repair with these tools, or there's a hardware issue (bad hard drive sectors, failing RAM) causing persistent file corruption. In that case, you'd need either an in-place upgrade repair using Windows installation media or, as a last resort, a clean Windows installation. Before going that route, run chkdsk /f to scan your hard drive for bad sectors, that's often the hidden culprit.
Preventing Windows Update Error 0x80070652
Once you've fixed this error, you don't want it happening again. The best prevention is behavioral: respect Windows Update's rhythm. When it tells you to restart, restart immediately. Don't delay pending restarts by days or weeks. Every time you ignore a restart prompt and try to install something new, you're stacking installations on top of incomplete ones, and that's precisely how 0x80070652 gets triggered.
Second, avoid installing third-party software while Windows Update is working. If you see the update notification, let it complete before you fire up another installer. Windows Installer (msiexec.exe) can only do one thing at a time, so parallel installations queue up and sometimes fail.
Third, run sfc /scannow quarterly as preventative maintenance. This catches file corruption early before it causes update failures. Pair it with the Windows Update Troubleshooter, which you can run monthly from Settings > Troubleshoot > Windows Update > Run.
Finally, keep your driver" class="vae-glossary-link" data-term="device-driver">device drivers current. Outdated chipset, storage, or network drivers can cause conflicts with Windows Update processes. Check Device Manager monthly and update anything marked with a yellow warning icon.
One more thing worth mentioning: if you're using aggressive third-party security software, temporarily disable it during major feature updates. Some antivirus suites lock system files during scans, which can interfere with Windows trying to write update files. It's only needed during the update process, not forever.
Windows Update Error 0x80070652 Summary
Error 0x80070652 is frustrating, but it's fixable in the vast majority of cases without losing any personal data or installed programs. The real cause is almost always either a stuck Windows Installer process, corrupted update cache files, or a pending restart that hasn't been completed. Start with a restart and the Windows Update Troubleshooter, that solves 60% of cases in 15 minutes. If it persists, move to the intermediate solution (stopping services and renaming the SoftwareDistribution folder), which clears corrupted cache and works in 75% of remaining cases. Only if both fail should you venture into the advanced territory of system file repair and Clean Boot diagnosis. The key takeaway: Windows Update error 0x80070652 is a fixable software problem, not a sign your system is dying. Respect the process, follow the steps, and you'll get back to installing security patches and feature updates cleanly.