How to Fix Windows Update Error 0x80070652
What error 0x80070652 means
Under the hood, 0x80070652 is the Windows Installer error ERROR_INSTALL_ALREADY_RUNNING — literally, another installation is already in progress. Windows uses a single system-wide installer lock, held by the MSI service: only one installation may hold it at a time. When Windows Update tries to install its package and finds the lock already held — by a previous update that stalled, a program installer you forgot about, or a background app updating itself — it backs off and reports 0x80070652 instead of queuing politely behind it.
In practice, the usual story is an interrupted update. A laptop that went to sleep mid-install, a restart that got delayed for days, or a forced shutdown during patching leaves a half-finished installation registered as still running. The MSI service keeps waiting for an installer that will never return, so every new update attempt collides with the ghost of the old one. Third-party antivirus and aggressive optimizer tools can make it worse by freezing installer processes mid-flight, and a corrupted update cache or damaged system files can keep the lock jammed long after the original install gave up. Your fixes should follow that same order: let anything pending finish, release the stuck lock, then repair whatever damage kept it stuck.
Common causes
- A previous update or app install that never finished: interrupted by sleep, a forced shutdown, or a crash, leaving the MSI installer lock held by an installer that is no longer really running.
- The Windows Installer (msiserver) service stuck in a busy state: a failed installation leaves the service waiting, so every new install attempt is rejected as a duplicate.
- Corrupted system files or a damaged update cache: broken installer components or a bad SoftwareDistribution folder can keep the lock jammed and block all updates.
- Third-party antivirus interfering with installers: real-time scanners can freeze installer processes mid-install, stranding the installer lock mid-flight.
- Low disk space on the system drive: with less than about 20 GB free, the installer cannot stage its files, and the half-started install hangs in the busy state instead of failing cleanly.
How to fix error 0x80070652 — step by step
Work through these fixes in order. Step 1 resolves the majority of cases on its own; step 2 handles the stubborn ones; steps 4 through 6 cover damaged components and stuck caches.
- Restart your PC and let any pending installs finish. Save your work and restart the PC normally (not Shut down, which can hibernate instead of rebooting on some systems). After logging back in, wait a few minutes before touching anything: background and half-finished installs often resume and complete during boot. Then open Settings, go to Windows Update, and click Check for updates. This alone clears 0x80070652 in most cases, because a restart releases the stuck installer lock.
- Run the Windows Update troubleshooter. Open Settings and go to Update and Security (Windows 10) or System (Windows 11), then Troubleshoot > Other troubleshooters, and click Run next to Windows Update. The troubleshooter detects stuck installer states, corrupted download caches, and stalled update services, and it resets them automatically — including releasing the MSI installer lock that causes 0x80070652.
- Find the failed update in your update history and retry it directly. Open Settings > Windows Update > Update history and look for the entry that failed with 0x80070652. Note its KB number, then go back to the Windows Update page and click Check for updates or Retry. Retrying after the troubleshooter has cleared the stuck state often succeeds, because the block was the installer lock, not the update itself.
- Repair system files with SFC and DISM. Open Command Prompt (or Terminal) as administrator and run
sfc /scannow, then wait for the scan to finish. If it reports corruption it could not fix, runDISM /Online /Cleanup-Image /RestoreHealthto repair the Windows component store, then runsfc /scannowonce more. Damaged system files and installer components are a common underlying reason the MSI lock gets stuck in the first place. - Reset the Windows Update components. Open Command Prompt as administrator and stop the update services with
net stop wuauserv,net stop bits,net stop cryptSvc, andnet stop msiserver. Then clear the caches withren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old, and restart the services withnet start wuauserv,net start bits,net start cryptSvc, andnet start msiserver. This rebuilds the update folders and forces the Windows Installer service out of its stuck busy state. - Install the failed update from the Microsoft Update Catalog. Take the KB number from your update history, go to catalog.update.microsoft.com, search that KB number, and download the standalone installer matching your system (x64 for most PCs). Double-click it to run. Standalone installers use a different delivery path that bypasses the stuck automatic update agent entirely, so they succeed where automatic updates repeatedly fail with 0x80070652.
Did this fix it? Quick checklist
- PC restarted normally, and pending installs were given time to finish
- Windows Update troubleshooter run, with its automatic fixes applied
- SFC scan completed — no unresolved corruption (or DISM repaired it)
- Update components reset, or the KB installed standalone from the Catalog
If 0x80070652 still will not go away, check your free disk space first: open Settings > System > Storage and make sure the system drive has at least 20 GB free, since a starved installer hangs instead of failing cleanly. Next, temporarily disable any third-party antivirus, retry the update, and re-enable protection immediately afterward. As a last resort, run an in-place repair: download the Windows 11 Installation Assistant or Media Creation Tool from Microsoft, choose to upgrade this PC now, and keep your files and apps — it rebuilds the entire update system around your existing setup.
Frequently asked questions
What does error 0x80070652 mean?
Error 0x80070652 is Windows Installer error ERROR_INSTALL_ALREADY_RUNNING: another installation is already in progress. Windows Update found that a previous installer — usually an earlier update that never finished — is still holding the system-wide installer lock, so it refused to start a second installation on top of it. The underlying cause is almost always an interrupted, stuck, or incomplete previous installation rather than the current update itself.
Will restarting my PC fix error 0x80070652?
Often, yes — it is the first fix for a reason. A proper restart lets any pending or half-finished installation resume and complete, which releases the installer lock, and it gives Windows a chance to cleanly roll back an installation that is stuck. If one restart does not do it, run the Windows Update troubleshooter and then work through the component-reset steps in this guide.
Can antivirus cause Windows Update error 0x80070652?
It can contribute. Third-party antivirus can freeze or block installer processes in mid-installation, leaving the MSI service in a stuck busy state that triggers 0x80070652 on the next attempt. Temporarily disable your third-party antivirus, retry the update, and re-enable protection immediately afterward. If updates keep failing this way, check with your antivirus vendor for updates or installer exclusions.
Does error 0x80070652 affect Windows 10 and Windows 11?
Both. The error comes from the Windows Installer service, which works the same way in Windows 10 and Windows 11. Every step in this guide applies to both versions — the only differences are the menu labels (Settings > Update and Security on Windows 10, System > Windows Update on Windows 11), and both paths are noted where they differ.