How to fix 0x80240020 (no logged-on interactive user) in Windows Update
This means an update tried to run when no one was signed in, so it could not finish. It also shows up when the update components are corrupt. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~7 min Updated Jun 2026 88% found this helpful
Error message
0x80240020 WU_E_NO_INTERACTIVE_USER. The operation did not complete because there is no logged-on interactive user.
Summary
0x80240020 (WU_E_NO_INTERACTIVE_USER) means an update needed someone to be signed in interactively and there was no logged-on user, so it could not complete. This is common with a deferred or scheduled feature upgrade that tried to run in the background, where the install wants an interactive session to proceed. The same code also appears when the Windows Update components are corrupt. The fix is to sign in and run the update yourself from Settings, run the troubleshooter, make sure the update services are running, reset the components and clear the SoftwareDistribution cache, and for a stuck feature upgrade set the AllowOSUpgrade registry value so it can proceed. Running the update interactively is usually all it takes.
What this error means
Some update operations, especially a feature upgrade, expect an interactive user session to complete, because they may need to show prompts or run user-context steps. When the update is triggered with no one signed in, for example on a schedule, it stops and reports that there is no interactive user.
The straightforward fix is to give it what it wants: sign in and run the update manually so there is an interactive session. When the error persists with a user signed in, the cause shifts to corrupt update components, which the standard reset clears.
Common causes
The update ran with no interactive user signed in.
A scheduled or deferred feature upgrade ran in the background.
The Windows Update components are corrupt.
The Windows Update or BITS service is stopped.
The SoftwareDistribution cache is corrupt.
An antivirus interfered with the update session.
The OSUpgrade allow flag is not set for a feature upgrade.
Expert insight
“The wording sounds alarming but it is usually benign, a scheduled update fired when nobody was signed in, and that particular step wanted a user present. So the first thing I do is sign in and just run Check for updates by hand, which gives it the interactive session it was missing, and it sails through. If it still complains with someone clearly signed in, then it is the components, and the standard cache reset sorts it.”
0x80240020 usually just means an update fired with nobody signed in, so signing in and running it manually clears it most of the time. If it persists with a user clearly signed in, treat it as corrupt update components and do the standard SoftwareDistribution reset. For a stuck feature upgrade, the AllowOSUpgrade flag lets it proceed.
Frequently asked questions
What does error 0x80240020 mean?
WU_E_NO_INTERACTIVE_USER means an update needed a signed-in interactive user and there was none, so it could not complete. It is common with background or deferred feature upgrades.
How do I fix it?
Sign in and run the update manually from Settings, Windows Update, Check for updates. That gives the update the interactive session it was missing, which clears most cases.
It still fails with me signed in
Then the cause is corrupt update components. Reset them by renaming SoftwareDistribution and catroot2 with the services stopped, then restart the services and retry.
What is AllowOSUpgrade for?
It is a registry flag that lets a feature upgrade proceed. Set the AllowOSUpgrade DWORD to 1 under the WindowsUpdate\OSUpgrade key when a feature upgrade is stuck with this error.
Can I install the update manually?
Yes. Note the failing KB number, download it from the Microsoft Update Catalog, and install it yourself to bypass the background trigger.
Is this a serious error?
Usually not. It often just means a scheduled update ran with nobody signed in. Running the update interactively resolves it without any deeper repair.
Still not working?
If the update keeps failing even when run manually, reset the update components in full and then install the specific KB from the Microsoft Update Catalog. If a feature upgrade is the one failing, the Windows Installation Assistant runs it interactively and avoids the background trigger. You can also submit your error to us for a tailored fix.
