Windows Update error 0x80242016, explained and fixed

0x80242016 means WU_E_UH_POSTREBOOTUNEXPECTEDSTATE: after the restart, the update handler found the update in a state it did not expect, so it reported the operation as failed. It appears after the reboot phase of an update, most often feature updates and larger cumulative updates, and it has a quirk: the update frequently installed successfully anyway.

The fix, in order

  1. Check whether the update actually installed. Settings → Windows Update → Update history: if the update shows as successfully installed, and Settings → System → About shows the expected build, the error was bookkeeping noise from the restart. Clear it by checking for updates once more and move on.
  2. Run the Windows Update troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It catches stopped services, cache problems, and registration faults automatically.
  3. Restart once more and re-check for updates. The unexpected-state flag often clears when the handler reconciles its records on a clean cycle.
  4. Reset the Windows Update components. In an admin Command Prompt, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old, then restart the four services with net start. This rebuilds the download cache and the update database from scratch.
  5. Repair the component store and system files. From an admin Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Restart afterwards; a repaired store often lets the same update sail through on the next attempt.

If it still happens

If the update truly did not install and the code repeats, install it manually from the Microsoft Update Catalog. For feature updates stuck in this loop, the Installation Assistant or an in-place upgrade via installation media sidesteps the state machine entirely.

Common questions

The update shows both ‘failed 0x80242016’ and ‘successfully installed.’ Which is true? The installed entry. This code fires when the post-reboot check finds the state already advanced past where it expected, typically because the update completed and a later process moved things along. If the build number and history agree it installed, trust them.

Why does the state end up ‘unexpected’? Commonly because another update or a servicing operation ran across the same reboot, or the pending state was committed by a different path than the handler anticipated. It is a coordination hiccup in the update bookkeeping rather than damage to the system.

Related errors

Windows Update error 0x80004005 · Windows Update error 0x800f0988 · Windows Update error 0x80070002