Error 0x80240016 (WU_E_INSTALL_NOT_ALLOWED) means Windows Update tried to start an install or uninstall operation while another one was already in progress. Windows allows only one servicing operation at a time, so the second attempt is refused outright with this code. It is the update-engine equivalent of two people trying to use the same single-occupancy restroom.

On Dell laptops the competing operation is often invisible: a Dell SupportAssist driver install, a Microsoft Store app update, or a previous Windows Update session stuck in a half-finished state. Sometimes the ‘other operation’ is Windows Update itself — a background phase still running from an earlier check. The error is usually transient, but when it sticks around across restarts, something is genuinely wedged.

The approach is straightforward: let legitimate operations finish, kill stuck ones, and make sure only one updater runs at a time. The steps below escalate from patience to a full component reset. If you are dealing with a related symptom instead, see the 0x80070652 already-running error and the 0x80080005 service error .

Think of Windows servicing as a single-occupancy workshop: only one job runs at a time, and 0x80240016 is the ‘occupied’ sign. Most of the time the other job is legitimate and finishes on its own — a Store update, a Dell driver install, an earlier update phase. The fixes below escalate sensibly from patience, to closing the competing apps, to clearing a genuinely stuck operation, so you intervene exactly as much as the situation requires.

Why this happens

  • Genuine concurrent update Store, Office, or Dell updaters running simultaneously.

  • Stuck previous update session an earlier operation never signaled completion.

  • Dell background utilities installing drivers SupportAssist or Dell Update mid-install.

  • Pending restart blocking new operations Windows queues operations behind a reboot that never happened.

  • Corrupt update state flags the engine thinks an operation is running when none is.

  • Two admin tools racing running Windows Update while Dell Command Update runs.

  • Scheduled task triggering updates an automated task colliding with your manual check.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Wait, restart properly, and retry

Legitimate concurrent operations finish on their own. Patience is a legitimate fix here rather than passivity: the competing operation is usually a genuine update doing genuine work, and ten quiet minutes after a proper Restart lets it finish and release the servicing lock on its own. Resist opening Task Manager or the Store during the wait; launching more updaters while one is finishing is how a transient queue becomes a genuine conflict.

  1. Save work and do a full Restart from the Start menu.

  2. After sign-in, wait 10 minutes without opening updaters.

  3. Open Settings > Windows Update and retry.

  4. If the code persists, continue — something is stuck.

Fix 2: Close competing updater apps

Make sure only one updater is active. Work through the suspects in order of likelihood: Dell’s updaters first since they run automatically, then the Microsoft Store’s app updates, then any installer window you might have left open and forgotten about. Dell’s tools sometimes schedule their own update checks on login, so the collision you hit today can recur tomorrow unless you stagger their schedules.

  1. Close Dell SupportAssist, Dell Command Update, and Dell Update.

  2. Pause Microsoft Store app updates (Store > Settings).

  3. Check Task Manager for setup or installer processes and end stuck ones.

  4. Retry Windows Update alone.

Fix 3: Run the Windows Update troubleshooter

Detects and clears stuck operation states. The troubleshooter looks specifically for operations stuck in the ‘in progress’ state and clears them, which is a more precise intervention than the general resets used for other error codes. If the troubleshooter reports no issues yet the error persists, the stuck state is likely in a competing app rather than Windows Update itself — return to Fix 2.

  1. Settings > System > Troubleshoot > Other troubleshooters.

  2. Run the Windows Update troubleshooter.

  3. Apply fixes, restart, and retry.

Fix 4: Clean boot to isolate the conflict

Finds the third-party process holding the operation lock. If the update succeeds in the clean-boot state, re-enable your services in small groups and retest; the group that brings the error back contains the program that was holding the lock.

  1. msconfig: hide all Microsoft services, disable the rest.

  2. Disable all startup items via Task Manager.

  3. Restart and run Windows Update in the clean state.

  4. Re-enable everything afterward.

Fix 5: Reset Windows Update components

Clears the corrupt state flags claiming an operation is running. This reset wipes the engine’s memory of every in-flight operation flag, which is the definitive cure when the ‘another operation is running’ state has become detached from any real operation.

  1. Elevated prompt: stop wuauserv, cryptSvc, bits, msiserver.

  2. Rename SoftwareDistribution and catroot2 to .old.

  3. Restart the four services.

  4. Retry the update.

Fix 6: Check for a stuck pending restart

A phantom pending reboot can block all new operations. A machine that has been ‘waiting to restart’ for days will queue every new servicing operation behind that phantom reboot, so clearing the backlog starts with the restart itself.

  1. Check Settings > Windows Update for ‘Restart required’ and restart if shown.

  2. In regedit, inspect HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations — a huge stale list can indicate stuck servicing; do not delete blindly.

  3. Restart and retry.

Fix 7: DISM and SFC for engine damage

If the engine itself is damaged, repair it. Engine-level damage is the least likely cause of this code, which is why these repairs sit last; reach for them only when the conflict survives restarts, clean boots, and component resets.

  1. Elevated prompt: DISM /Online /Cleanup-Image /RestoreHealth.

  2. Then sfc /scannow.

  3. Restart and retry Windows Update.

Closing

Error 0x80240016 is Windows Update’s polite refusal to do two things at once. Give the legitimate operation time to finish, clear the stuck ones, and the refused update will run cleanly on the next attempt. For official guidance, see Microsoft’s Windows update support hub . One operation at a time is the rule Windows enforces; now you know how to spot the operation hogging the workshop and clear it.

Frequently asked questions

What does 0x80240016 mean?
WU_E_INSTALL_NOT_ALLOWED: an install or uninstall operation was attempted while another servicing operation was already in progress. Windows permits only one at a time, so the second is rejected with this code. The competing operation might be a Store app update, a Dell driver install, or a stuck earlier session. Letting the first operation finish — or clearing it if stuck — allows the refused one to proceed.
How is this different from 0x80070652?
They are cousins: 0x80070652 is the Windows Installer (MSI) reporting another installation running, while 0x80240016 is the Windows Update engine itself refusing a concurrent servicing operation. The fixes overlap heavily. In practice the distinction rarely changes what you do — find the competing or stuck operation, let it finish or clear it, and retry. Both codes mean Windows refused to do two installs at once.
Should I stop Dell SupportAssist permanently?
No — it is useful for drivers and diagnostics. Just avoid running it at the same moment as Windows Update. Let one finish before starting the other. SupportAssist handles Dell-specific driver and firmware updates that Windows Update does not cover well, so removing it would cost you more than it saves. The conflict only happens during the rare overlap; a little scheduling avoids it entirely.
Why does restarting fix it sometimes?
A proper restart lets pending servicing operations commit and clears in-memory state flags. Many ‘stuck operation’ states exist only in RAM and vanish on reboot. The update engine tracks running operations partly in memory; when that tracking gets wedged, a restart wipes the slate clean. Use Restart from the Start menu rather than Shutdown, so Fast Startup does not preserve the stuck state.