Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

0x80240016

Microsoft Windows Update 0x80240016: installation blocked

Verified with sources1 sourceReviewed Oct 19, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Error 0x80240016 (WU_E_INSTALL_NOT_ALLOWED) means Windows Update tried to start an installation while another installation was running or a mandatory restart was pending. Wait for active installs to finish, select Update and restart, and check for updates again.

Safety first

Stop and check this first

  • Never force-power-off the computer while Windows is actively installing updates or displaying Update and restart; interrupting an active servicing transaction can leave components in a partially installed state.

Safe checks you can perform

  • Check the Start > Power menu for Update and restart or Update and shut down
  • Wait for active installations to finish and re-check Windows Update after rebooting
  • Run the Windows Update troubleshooter to clear stuck update service states

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Revert stuck pending servicing actions or reset the update cache if a reboot loop persists
  • Do not attempt this professional task: Verify administrator privileges, IUpdateInstaller state, and TrustedInstaller startup policy

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Revert stuck pending servicing actions or reset the update cache if a reboot loop persists

    What they doIf a corrupted pending transaction permanently reports a mandatory restart even after rebooting, have the administrator back up data, inspect %windir%\logs\CBS\CBS.log, and if needed run dism /Image:C:\ /Cleanup-Image /RevertPendingActions from the Windows Recovery Environment (WinRE).

    They must show youthe CBS.log entries around the failure timestamp and the clean Windows Update status after recovery.

    In writingthe exact remediation command executed, the CBS.log error line, and the post-repair update scan result.

  2. Verify administrator privileges, IUpdateInstaller state, and TrustedInstaller startup policy

    What they doHave an IT administrator sign in with Local Administrator rights, verify that custom WUA scripts check IUpdateInstaller::IsBusy and RebootRequiredBeforeInstallation before calling Install, and ensure Group Policy has not forced the TrustedInstaller service back to Manual during a pending reboot transaction.

    They must show youthe TrustedInstaller service status, any custom deployment script logs, and the successful KB installation in Update history.

    In writingthe KB number installed, the TrustedInstaller startup configuration, and the completion timestamp.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Check the Start > Power menu for Update and restart or Update and shut down

    No special tools

    Who:
    You can check this directly on your Windows 10 or Windows 11 desktop.
    How:
    Save open documents, close running applications, and select Start > Power to inspect the available power options.
    Result that matters:
    Windows displays Update and restart or Update and shut down when a previous update has staged changes that require a system reboot.
    If Update and restart appears on the Power menu, that confirms a pending mandatory restart is blocking the new installation with 0x80240016.
    If only normal Restart and Shut down options appear, that rules out a staged reboot prompt and points to another active installer process.
    Evidence to keep:
    Note the exact power menu options shown and the time you initiated the restart.

    Evidence: Windows Update error reference · Microsoft Windows Update troubleshooting

  2. Wait for active installations to finish and re-check Windows Update after rebooting

    No special tools

    Who:
    You can perform this check in Settings after the device restarts.
    How:
    Allow any running Windows Update or application installer to finish, complete the system restart, and then open Start > Settings > Windows Update > Check for updates.
    Result that matters:
    IUpdateInstaller::Install only allows a new installation when IsBusy returns VARIANT_FALSE and no pre-installation reboot is required.
    If the queued KB downloads and installs normally after the reboot, that confirms 0x80240016 was caused by the temporary concurrency or restart lock.
    If 0x80240016 returns immediately with no visible installer running, that indicates a stuck servicing transaction or automation script calling WUA while busy.
    Evidence to keep:
    Keep a screenshot of the Windows Update page showing the post-restart installation result.

    Evidence: Microsoft Windows Update troubleshooting · IUpdateInstaller::Install method (wuapi.h) · IUpdateInstaller::get_RebootRequiredBeforeInstallation method (wuapi.h)

  3. Run the Windows Update troubleshooter to clear stuck update service states

    No special tools

    Who:
    You can run this built-in tool from Start > Settings > System > Troubleshoot > Other troubleshooters.
    How:
    Locate Windows Update in the list, select Run, and follow the on-screen prompts to completion.
    Result that matters:
    The troubleshooter checks whether the Windows Update service or a pending post-reboot operation is stuck.
    If the troubleshooter clears a stuck update state and allows the KB to install, that confirms a hung local update operation was holding the lock.
    If the troubleshooter completes without clearing the block, that points to a Group Policy or TrustedInstaller transaction issue requiring administrator review.
    Evidence to keep:
    Save a screenshot of the troubleshooter diagnostic findings.

    Evidence: Common Windows Update errors · Microsoft Windows Update troubleshooting

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x80240016
  • Windows Update 0x80240016
  • WU_E_INSTALL_NOT_ALLOWED

What it means

In the Windows Update error reference and Wuerror.h, 0x80240016 corresponds to WU_E_INSTALL_NOT_ALLOWED: the operation tried to install while another installation was in progress or the system was pending a mandatory restart. At the Windows Update Agent (WUA) API level, IUpdateInstaller::Install returns WU_E_INSTALL_NOT_ALLOWED if called while the installer is already installing or removing an update (IsBusy is not VARIANT_FALSE) or when IUpdateInstaller::get_RebootRequiredBeforeInstallation is true. Code 0x80240016 alone never indicates corrupted system files or hardware damage; it is a concurrency and reboot-lock safeguard.

Warnings and stop conditions

  • Lowsource verified

    Never force-power-off the computer while Windows is actively installing updates or displaying Update and restart; interrupting an active servicing transaction can leave components in a partially installed state.

    Evidence: Common Windows Update errors · Microsoft Windows Update troubleshooting

Symptoms and causes

Probable causes · in order

  • Another update installation or removal is currently in progressConfirmed

    Microsoft defines 0x80240016 (WU_E_INSTALL_NOT_ALLOWED) when an operation tries to install while another installation is in progress; IUpdateInstaller::Install requires IsBusy to be VARIANT_FALSE.

    Evidence: Windows Update error reference · IUpdateInstaller::Install method (wuapi.h)

  • System is pending a mandatory restart from an earlier updateConfirmed

    WU_E_INSTALL_NOT_ALLOWED is also returned when the system is pending a mandatory restart and IUpdateInstaller::get_RebootRequiredBeforeInstallation indicates a reboot is required before installing updates.

    Evidence: Windows Update error reference · IUpdateInstaller::get_RebootRequiredBeforeInstallation method (wuapi.h)

  • TrustedInstaller startup policy or post-reboot transaction still pendingPossible

    If a Group Policy sets the TrustedInstaller service startup type to Manual before a restart, pending update transactions cannot finish and block subsequent update installations.

    Evidence: Common Windows Update errors

Virtual technician

Does 0x80240016 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Sources and technical references

  1. 1

    Windows Update error reference

    Microsoft · 2026 · official_doc

Sources: Windows Update error referencereviewed 2026-10-19 · verified

Was this entry useful?