Error 0x80240016 means the update operation you requested is not allowed in the current state — something else is installing, the system is in a restricted state, or the request itself is invalid. Your Lenovo laptop is not broken; it is refusing the operation for a reason. The refusal is usually protective: Windows will not start an update while another installer holds the lock, or while the system is mid-reboot-sequence. If installs hang rather than being refused, the 0x80244010 server-trips guide covers that symptom. The fixes identify what is blocking the operation and clear it. Patience plus verification resolves most cases; the resets handle stuck states.

Why this happens

  • Another installation in progress: The single-installer rule refuses concurrent operations — a background update, Store install, or MSI setup holds the lock.
  • Operation requested during shutdown sequence: Update operations initiated while Windows is preparing to shut down or restart are refused.
  • Non-administrator context: Some update operations require elevation; without it, the operation is not allowed.
  • Stuck installer state: A crashed install can leave the ‘busy’ flag set, so every subsequent operation is refused indefinitely.
  • Windows Update paused by policy: Group or MDM policies can forbid update operations, producing refusals that look like errors.
  • Corrupted update client state: A damaged client can misreport its own state, refusing operations that should be legal.
  • Pending reboot lock: Until a pending reboot completes, certain servicing operations are correctly refused.

How to fix it

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

Fix 1: Wait for the other installer to finish

With 0x80240016, this step earns its place early, since the error usually means the requested update operation is not allowed right now. Windows allows only one trusted installer operation at a time. If another update, a Store app update, or an MSI installer is running in the background, your update is correctly refused until that one completes. The fix is patience plus verification, not force.

  1. Open Settings, Windows Update, and check whether another update is actively installing.
  2. Open Task Manager and look for msiexec.exe or TiWorker.exe consuming CPU.
  3. Let any in-progress installation finish completely, then restart the laptop.
  4. Retry your update once the system is idle.

Fix 2: Reset the Windows Update components

This fix matters for 0x80240016 because the error generally means the requested update operation is not allowed right now. When downloads or install states get corrupted, the updater keeps tripping over its own leftovers. Stopping the update services and renaming the SoftwareDistribution and catroot2 folders forces Windows to rebuild them cleanly, with fresh permissions and no stale pending operations. Resetting components clears the stuck installer flags behind most persistent refusals — the procedure is documented in Microsoft’s official Windows support hub .

  1. Open an elevated Command Prompt (right-click Start, choose Terminal (Admin)).
  2. Stop the services: run net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver.
  3. Rename the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart the four services with net start, then check for updates again.

Fix 3: Verify the update services are running

For 0x80240016 — which typically means the requested update operation is not allowed right now — this step removes a frequent blocker. Windows Update depends on several background services, and if any of them is disabled or stuck, installs fail. Tweaking tools and aggressive debloating scripts sometimes turn these off. A quick check in the Services console rules this out in under a minute.

  1. Press Win + R, type services.msc, and press Enter.
  2. Check Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and Windows Installer.
  3. Set each startup type to Automatic (or Manual for Windows Installer) and start any that are stopped.
  4. Retry the update after all four services are running.

Fix 4: Perform a clean boot, then retry

Since 0x80240016 usually means the requested update operation is not allowed right now, this fix targets one of the most likely causes. Background programs — updaters, overlays, driver utilities — can lock files or services the update installer needs. A clean boot starts Windows with only Microsoft services running, which isolates whether a third-party program is the culprit without uninstalling anything.

  1. Press Win + R, type msconfig, and open the Services tab.
  2. Tick Hide all Microsoft services, then click Disable all.
  3. Open Task Manager’s Startup apps tab and disable everything listed.
  4. Restart, retry the update, then re-enable your startup items afterward.

Fix 5: Pause and resume updates to clear the queue

With 0x80240016, this step earns its place early, since the error usually means the requested update operation is not allowed right now. The update queue itself can get into a wedged state where a half-finished operation blocks everything behind it. Pausing updates for a short period, then resuming, forces the queue to rebuild and often unblocks the stuck install.

  1. Open Settings, then Windows Update.
  2. Click Pause updates and choose 1 week.
  3. Restart the laptop while updates are paused.
  4. Return to Windows Update, click Resume updates, and retry the install.

Fix 6: Run the Windows Update troubleshooter

This fix matters for 0x80240016 because the error generally means the requested update operation is not allowed right now. The built-in troubleshooter is the fastest way to clear a stuck update state, because it checks the update services, resets pending operations, and repairs common configuration problems automatically. It takes about two minutes and fixes a surprising number of failures without any command-line work. The built-in troubleshooter detects policy blocks and stuck states automatically.

  1. Open Settings, then go to System and click Troubleshoot.
  2. Choose Other troubleshooters and find Windows Update in the list.
  3. Click Run, let the scan finish, and apply every fix it suggests.
  4. Restart the laptop, then go back to Windows Update and retry the install.

Fix 7: Repair system files with SFC

For 0x80240016 — which typically means the requested update operation is not allowed right now — this step removes a frequent blocker. Corrupted Windows system files can break the update installer in subtle ways, and the System File Checker exists specifically to find and replace them. It scans every protected file against a known-good copy and repairs anything damaged, which removes a whole class of update failures.

  1. Open an elevated Command Prompt or Terminal (Admin).
  2. Type sfc /scannow and press Enter, then wait for the scan to finish.
  3. If it reports that it repaired files, restart the laptop.
  4. Retry the update install after the restart completes.

Closing

Refused operations are Windows enforcing its own safety rules — usually correctly. Identify the blocker, let it finish or clear the stuck flag, and the refused operation proceeds on retry. Persistent refusals after a clean reboot deserve the component reset. If the failure becomes a server timeout instead, the 0x8024401C request-timeout guide is the next step.

Frequently asked questions

What does error 0x80240016 mean?
It means WU_E_INSTALL_NOT_ALLOWED: the requested update operation is not permitted in the current system state. The most common reason is another installation already holding the single-installer lock, but it also appears when operations are requested during shutdown, without required elevation, under a prohibiting policy, or against a stuck installer state from a crashed previous install.
I am an administrator — why is it not allowed?
Because the restriction is usually about system state, not your privileges. The single-installer lock applies to administrators too, and a pending reboot or shutdown sequence refuses operations regardless of who asks. Elevation matters only for the subset of operations that require it. Check Task Manager for in-progress installers and reboot to clear pending states before assuming a permissions problem.
Could my company's policy cause this?
Yes. MDM or group policies can restrict which update operations are allowed, defer them, or route them to internal servers — and refusals surface as errors like this. A ‘managed by your organization’ notice in Windows Update settings is the tell. On a personal device, check for leftover policies from previous management; on a work device, the IT department owns this configuration.
How is this different from 0x80070652?
They are siblings: both involve the single-installer rule. 0x80070652 specifically means another installation is actively running, while 0x80240016 is the broader ‘operation not allowed’ that also covers policy blocks, wrong system state, and stuck flags. If you can see another installer running, treat it as 0x80070652 and wait; if nothing is visibly installing, work the stuck-state fixes here.