Fix STATUS_CTX_NOT_CONSOLE 0xC00A0024 on Windows

What's happening here

You're on a Remote Desktop or SSH session, and some program — often an installer, a legacy service, or a command that tries to interact with the physical screen — throws STATUS_CTX_NOT_CONSOLE (0xC00A0024). The message says it plainly: "The requested operation can be performed only on the system console."

Windows checks if your session is session 0 (the local console) versus a remote session (session 1, 2, etc.). Many old or poorly written apps assume they're running on the console and refuse to start elsewhere. It's a pain, but the fix is quick.

The fix

You have two options. Try the first one — it works 90% of the time.

Option 1: Use the console session directly

Connect to the machine's actual console session via RDP:

mstsc /admin /v:your-server-name

The /admin flag (or /console on older Windows versions) connects you to session 0, the real console. Now run your command again. It'll work because Windows thinks you're sitting at the keyboard.

Why this works: The /admin switch bypasses the session redirection that Remote Desktop normally does. You're literally on the same session as the local monitor. The app sees session ID 0 and stops complaining.

Option 2: Change the Group Policy (Windows Pro/Enterprise/Server)

If you can't use /admin — maybe you need the RDP session to stay and you want all apps to run — tweak this policy:

Press Win+R, type gpedit.msc, hit Enter.
Navigate to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections
Find "Restrict Remote Desktop Services users to a single Remote Desktop Services session". Set it to Disabled.
Also check "Limit number of connections" — set it higher than 1 if you want multiple sessions.
Run gpupdate /force in an elevated command prompt.

Now reconnect without /admin. The app might still fail — this policy doesn't directly remove the console check, but it changes how sessions are allocated. I've seen this work for some legacy apps that were hardcoded to session 0.

Option 3: Registry hack (works on all editions)

Got Windows Home? No Group Policy? Use the registry:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 0 /f

Then restart the Remote Desktop Services service (net stop TermService & net start TermService). This disables Network Level Authentication and lets you connect more directly. It's less secure, but it's a quick win for internal networks or VMs.

Why does this error happen anyway?

Windows uses a session isolation model introduced in Vista. Session 0 is reserved for system services and the local console. Remote Desktop sessions get numbered 1, 2, etc. Apps that call WTSQueryUserToken or GetConsoleWindow without checking the session ID will fail with 0xC00A0024 if the session isn't 0.

Microsoft did this for security — so malware from a remote session can't easily interact with the system console. But it breaks a ton of older software, especially installation utilities that try to draw UI on the console.

Less common variations

Sometimes the same error pops up in unexpected places:

Running schtasks with /ru SYSTEM from a remote session: The task runs as SYSTEM but still inherits the remote session. Use /it (interactive) flag to force it to session 0.
Windows 10/11 with Fast User Switching: If you switch users without logging off, the new user's session might not be the console. Trying to run certain system tools from the secondary user will trigger this error. Log off the first user completely.
Third-party remote tools (TeamViewer, AnyDesk): These don't use RDP — they run as a service in session 0 but inject into the user's session. If they try to launch a console-mode app, it can still fail. The workaround is to launch the app via psexec -i -s cmd.exe to get back to the console.

Prevention

Don't write or deploy apps that hardcode session 0 dependencies. If you're a developer, check WTSGetActiveConsoleSessionId and handle the case where the active console session might not be yours. For sysadmins, standardize your RDP connection shortcuts to include /admin when you know you'll be running system-level tools.

The simplest long-term fix: always connect with mstsc /admin for administrative work. It's one extra character, and it sidesteps this entire class of errors.