This is Windows Update refusing the operation outright — not failing at it, but declining to attempt it at all. The distinction matters: failures get retried, refusals need the underlying condition resolved first. Some aspect of the current session forbids the install — another installation occupying the floor, or a user context missing the rights the operation requires.

On 24H2 laptops the story usually has two suspects. Either a second installation is active behind the scenes — Microsoft Store, Office, a driver package — or the update was launched from a non-administrator context missing install privileges. Two swift checks divide the diagnosis: is another install running, or is this about permissions?

The fix follows the diagnosis. Clear the conflict or elevate the session, and the refusal lifts. Guessing wrong here costs real time — waiting out a phantom session that will never finish, or elevating when a Store update was the actual blocker — so the two minutes of diagnosis pay for themselves many times over.

Why this happens

  • A second install is underway. The installer engine permits a single session at once; a background one obstructs yours.
  • Standard-user session. Certain install operations require elevation beyond what the current session holds.
  • Installer session wedged. As with its cousin 0x80070652, a crashed session may grip the lock indefinitely.
  • Store apps mid-update. The Microsoft Store refreshing apps behind the scenes ties up the installer.
  • Office Click-to-Run mid-update. Background Office updates clutch installer locks for extended periods.
  • A driver installer runs at startup. Vendor utilities that install drivers at boot can collide with the update window.
  • Pending restart blocks new installs. An update awaiting reboot can forbid further installations until it completes. Check for the telltale pending-restart icon in Settings > Windows Update before assuming a deeper problem.

How to fix it

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

Fix 1: Track down the conflict or the rights gap

Two swift checks divide the diagnosis: is another install running, or is this about permissions?

  1. Launch Task Manager and watch for msiexec.exe, setup.exe, Store activity, or Office updates in motion.
  2. Check whether your account is an administrator: Settings > Accounts > Your info.
  3. If something is installing, go to Fix 2. If you are a standard user, go to Fix 3. If neither — nothing installing, and you are an administrator — the session itself is wedged, and Fix 4 is your starting point.

Fix 2: Let the other installation finish

Where the block is legitimate, waiting is the remedy — meddling with a live installer breeds worse trouble than patience. Use the waiting time productively: note which program is installing, because repeat collisions with the same updater suggest a scheduling conflict worth fixing permanently.

  1. Let the other installation finish completely.
  2. Once signed in, allow a few minutes for startup installations to calm down.
  3. Pick Restart over Shut down, letting pending installer tasks finish across the reboot.
  4. Retry the update once the coast is clear and confirm the refusal is lifted.

Fix 3: Install from an elevated administrator account

A rights-starved session is fixed by elevation — standard-user sessions strike this code on operations demanding administrator install rights.

  1. Log out, then log back in under an administrator account.
  2. Head to Windows Update and execute the install within the administrator session.
  3. Should the everyday account remain standard, the diagnosis is confirmed — have the PC’s administrator perform updates.

Fix 4: Dislodge a stuck session via clean boot

Where no install is visible yet the block endures, a phantom session grips the lock. Clean-booting starts Windows minus the third-party installers behind these phantom sessions.

  1. Press Win + R and enter msconfig; under the Services tab, tick Hide all Microsoft services and press Disable all.
  2. Within Task Manager’s Startup tab, switch off all startup entries, then reboot.
  3. Execute Windows Update while clean-booted, then confirm the install proceeds.
  4. Re-enable everything afterward via the same dialogs.

Fix 5: Let the auto troubleshooter try

The troubleshooter detects stuck sessions and permission misconfigurations, applying automatic repairs that are always safe to try first.

  1. Raise Settings and hike to System > Troubleshoot > Other troubleshooters.
  2. Liberate the Windows Update entry and tail its prompts.
  3. Reboot the laptop and try once more.

Fix 6: Reset the Windows Update components

A corrupted engine state can produce phantom session blocks that mimic a busy installer. A full reset clears that state and restores normal session handling.

  1. Quell the services: net stop wuauserv, net stop bits, net stop cryptsvc.
  2. Sequester the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Reanimate the services: net start wuauserv, net start bits, net start cryptsvc.
  4. Poll for updates.

Fix 7: Install the package manually from the Catalog

A manual install from an administrator session sidesteps both the session restrictions and the stuck locks. The Microsoft Update Catalog stocks every cumulative release, so the exact package you need is one search away.

  1. Record the KB number from Update history.
  2. Obtain the correct x64 Windows 11 package from the Catalog.
  3. Right-click the downloaded .msu and choose Run as administrator.

Closing

Session refusals yield to session fixes: clear the conflict or elevate the context, and the install proceeds. Remember the distinction this error teaches — a busy installer versus a forbidden session — because the two demand opposite responses, and confusing them wastes the afternoon. Should installs subsequently fail for unrelated reasons, the 24H2 update-error catalog deciphers them, and the troubleshooter guide takes care of the automated checks. Microsoft’s Windows support hub documents install permissions. And if this error becomes a monthly ritual, audit what runs at startup — something in your boot sequence is racing Windows Update for the installer lock.

Frequently asked questions

What does error 0x80240016 mean?
WU_E_INSTALL_NOT_ALLOWED: the requested operation is not permitted in the current session state — most often because another installation is in progress, or because the user context lacks the rights for the operation. It is broader than a busy-installer code: the session itself is the problem.
How is this different from 0x80070652?
0x80070652 means the installer engine is busy with another session. 0x80240016 reaches wider — the operation is forbidden in this session outright, which includes permission problems. A standard-user account hitting an operation that needs administrator install rights produces exactly this code.
I'm the only user. Why would I lack rights?
Being the only human is not the same as running elevated. Standard user accounts — common on family or work laptops — cannot perform install operations that need administrator rights. Signing into an administrator account, or having the PC’s administrator run the update, resolves it.
The block keeps returning after I wait. What then?
When no install is visible but the block persists, a ghost session holds the lock — a crashed installer that never released it. A clean boot eliminates the third-party installers that create these ghosts, and the manual Catalog install sidesteps the session restrictions entirely.