| Previous | Next |
| ERROR_FILE_INVALID | ERROR_NO_TOKEN |
ERROR_FULLSCREEN_MODE
the requested operation cannot be performed in full-screen mode.
ERROR_FULLSCREEN_MODE means that a display or console operation is incompatible with the current full-screen presentation mode. In this case, the decisive context is legacy console full-screen modes, together with session type, console host, display mode, and whether the app is local or remote.
Where the result appears
- legacy console full-screen modes.
- display-mode transitions and older graphics compatibility paths.
- window-management operations that require a desktop windowed state.
- remote-session or virtualization environments emulating legacy full-screen behavior.
Typical causes
- the operation is defined only for windowed mode.
- the display/console subsystem is in the middle of a mode transition.
- the current session or graphics stack does not support the requested legacy feature.
- an application assumes historical full-screen behavior no longer provided.
Evidence to collect
- session type, console host, display mode, and whether the app is local or remote.
- the exact UI/display API and requested operation.
- OS version, compatibility settings, graphics driver, and virtualization layer.
- events around switching into or out of full-screen mode.
For this condition, begin the investigation with session type, console host, display mode, and whether the app is local or remote. Correlate it with the exact UI/display API and requested operation and check whether the operation is defined only for windowed mode. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
Handling and recovery
Return to a supported windowed state before retrying, or replace the legacy operation with a modern window or presentation API. Applications should treat full-screen as presentation state, not as permission to use obsolete display mechanisms.
Any retry policy for it should be tied to evidence that the display/console subsystem is in the middle of a mode transition has changed. Before another attempt, verify OS version, compatibility settings, graphics driver, and virtualization layer. If an application assumes historical full-screen behavior no longer provided still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
This is not a generic “window is maximized” error. It normally concerns a subsystem-specific full-screen mode with restrictions beyond ordinary maximization.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by display-mode transitions and older graphics compatibility paths. A useful telemetry record also includes events around switching into or out of full-screen mode. For a-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which the current session or graphics stack does not support the requested legacy feature, assert this result, and confirm that the program releases resources associated with window-management operations that require a desktop windowed state. The recovery test should also verify that session type, console host, display mode, and whether the app is local or remote is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.