Skip to main content
AdminSignal
Windows Update / WUfBdecimal -2145124320

Fix Intune Error 0x80240020: The update needed an interactive user session to finish, and nobody was signed in (WU_E_NO_INTERACTIVE_USER).

Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.

WindowsUpdate.log

Folder: C:\Windows\Logs\WindowsUpdate\

Also check: UpdatesDeployment.log (ConfigMgr) · WUAHandler.log (ConfigMgr)

Root causes

  • The update requires user interaction and the install ran when no one was signed in, such as on a kiosk or a device at the sign-in screen.
  • The process calling the Windows Update Agent runs in a secondary logon (RunAs) context that cannot show the interactive prompt.
  • A deployment ran during Autopilot ESP or first sign-in before a user session existed.

Step-by-step remediation

  1. Merge the Windows Update traces into a readable file with Get-WindowsUpdateLog (it writes WindowsUpdate.log to the desktop), then search it for the error code.
  2. Sign in to the device and let the installation start, then allow the restart.
  3. For shared or kiosk devices, set active hours and restart deadlines so installs complete without needing someone signed in.
  4. If a script or tool starts the install, run it as SYSTEM or in the user session, not through RunAs.
  5. Retry the update and confirm the log no longer reports WU_E_NO_INTERACTIVE_USER.

Keep patching failures out of the queue

Repeat update and client failures are cheaper to prevent than to chase. Compare the options that take app packaging and upkeep off your task list, from Enterprise App Management to PSADT.

Compare Win32 packaging tools

Related Error Codes in This Category

Other Windows Update / WUfB errors with their own runbooks.

Search all 21 error codes