How to Fix Windows Update Error 0x80240016

By ErrorFix · Updated October 23, 2026 · 6 min read

What error 0x80240016 means

Error code 0x80240016 is Microsoft's "install not allowed" code (WU_E_INSTALL_NOT_ALLOWED). It means Windows Update tried to install an update, but the installer engine was already busy: another installation was in progress, a previous update was left in an unfinished state, or an install attempt started while the system was shutting down. Windows allows only one installation at a time through the Windows Installer service, so the new update was refused rather than queued.

This is different from the more familiar download errors. Your files are usually fine — nothing is corrupted and nothing failed to download. The problem is a traffic jam at the install step: a lock is being held by something else, and until that something finishes or gets cleared, every new update attempt fails with the same code. The good news is that this rarely indicates a broken system. The fixes below clear the jam in a deliberate order, and you will not need to reinstall Windows.

Common causes

• Another installation is running: a program installer, a Windows Update task, or an Office/.NET update is still installing in the background and holds the installer lock.
• A previous update was interrupted: the PC was shut down or lost power mid-install, leaving the installer service in a stuck, unfinished state.
• Frozen msiexec.exe processes: leftover Windows Installer processes that never exited keep the install lock held indefinitely.
• Pending restart requirement: a previous update is waiting for a restart to complete; new installs are refused until you reboot.
• Stuck Windows Update services: the update services (wuauserv, bits, cryptSvc, msiserver) are in a bad state and report a phantom installation in progress.

How to fix error 0x80240016 — step by step

Work through these fixes in order. Most PCs install the update successfully by step 2.

1. Check for other running installations. Press Ctrl + Shift + Esc to open Task Manager and look at the Processes tab for anything that looks like an installer: entries named msiexec.exe, setup.exe, or an app's installer you recognize. If something is genuinely installing, do not kill it — let it finish completely, then go back to Settings, then Windows Update, and click Check for updates again. Rushing a second install in is exactly what triggers this error.
2. Restart your PC and retry the update. Click Start, then Power, then Restart — a full restart, not a shutdown (shutdown on modern Windows hibernates the kernel and can keep the stuck state). The restart finishes pending installs, clears installer locks, and resets the update services. Once you are back at the desktop, open Settings, go to Windows Update, and click Check for updates. If a "Restart required" notice was waiting, this step often resolves everything on its own.
3. Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and follow the prompts. The troubleshooter detects stuck installer states and phantom "installation in progress" flags, repairs them, and then asks you to retry the update. Restart your PC after it finishes before checking again.
4. End stuck installer processes. Press Ctrl + Shift + Esc to open Task Manager, switch to the Details tab, and look for msiexec.exe entries. If one has been sitting there with no CPU activity since an install you already cancelled or that was interrupted, right-click it and choose End task. Only end processes that are clearly leftover — never end an installer that is actively progressing. Close Task Manager and retry the update.
5. Reset the Windows Update components. Right-click Start and choose Terminal (Admin). Stop the four update services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Then rename the caches: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Restart the services: net start wuauserv, net start cryptSvc, net start bits, net start msiserver. This rebuilds the update pipeline and clears the stuck state that keeps reporting a phantom installation.
6. Install the pending update manually. Go to Settings, then Windows Update, then Update history, and note the KB number of the failing update. Search for that KB number on the Microsoft Update Catalog website, download the package that matches your system (x64 for most PCs), and install it by double-clicking the file. A manual install runs outside the automatic updater, so it sidesteps the stuck-install state that kept refusing the update.

Did this fix it? Quick checklist

• Windows Update installs updates without error 0x80240016
• No "another installation is in progress" or "install not allowed" message appears
• Update history shows the update as successfully installed
• The PC restarts cleanly with no pending update warnings

If the error persists after all six steps, open a Command Prompt as administrator and run DISM.exe /Online /Cleanup-image /Restorehealth followed by sfc /scannow, then restart and retry — deeply corrupted installer components can hold a permanent lock. Also avoid starting a new update while the PC is shutting down or while another app installer is running; 0x80240016 is most often a timing problem, not a broken system, so a calm retry after everything has finished usually wins.