| Previous | Next |
| DWM_E_COMPOSITIONDISABLED | DWM_E_NO_REDIRECTION_SURFACE_AVAILABLE |
DWM_E_REMOTING_NOT_SUPPORTED
DWM operation is not supported while remoting
DWM_E_REMOTING_NOT_SUPPORTED is HRESULT 0x80263002 (signed decimal -2144980990, unsigned decimal 2149986306). AllStat's winerror.h text says that some desktop-composition APIs are not supported while remoting and that the requested operation is unsupported in a remote session.
This result is a capability decision for the active presentation path. It does not mean that Remote Desktop as a whole has failed, and it does not imply that every DWM API is forbidden remotely. The caller must identify the exact operation and the session technology—full Remote Desktop, RemoteApp, virtual desktop infrastructure, console shadowing, or another remoting stack—before selecting a fallback.
Typical contract boundary
- An application asks for a local-compositor artifact, shared surface, timing behavior, thumbnail behavior, or presentation feature that the remote path does not expose.
- The target window may reside in a different session from the caller, or the caller may have cached assumptions from a prior console session before reconnection.
- A legacy graphics integration may rely on mirror-driver or local redirection behavior that changed when DWM became always enabled and remoting architecture evolved.
Diagnostic sequence
- Record the failing DWM function, target window, caller and owner session IDs, Windows build, remoting product, and whether the app runs as a full desktop or RemoteApp.
- Compare the same operation at the physical console. A console success and remote failure supports a capability distinction; it does not by itself identify network quality or server load as the cause.
- Verify that the application detects session changes instead of caching a “local” result at process startup. Re-evaluate capabilities after disconnect, reconnect, lock, unlock, and display-topology change.
- Check whether the requested visual result can be produced through an application-owned bitmap, ordinary window paint, supported capture API, or remote-compatible presentation path.
Difference from nearby DWM failures
DWM_E_COMPOSITIONDISABLED says the operation lacks a composition prerequisite. DWM_E_NO_REDIRECTION_SURFACE_AVAILABLE says a particular redirection surface could not be supplied. DWM_E_REMOTING_NOT_SUPPORTED is narrower: the current remote-session path does not implement the requested DWM operation. Switching adapters or shrinking a texture is not a justified response unless separate evidence identifies those conditions.
Retry and user experience
Retry is useful only after a capability-changing event, such as moving the operation to the console session, reconnecting under a supported session mode, recreating the window in the correct session, or selecting a documented remote-compatible API. A timer that repeats the same call while the session remains remote will normally repeat the same deterministic result. The application should disable only the unavailable visual feature, preserve its core function where possible, and explain that the limitation belongs to the remote presentation environment rather than reporting a generic network error.
Developer telemetry
- Raw HRESULT, exact API, feature being requested, and fallback selected.
- Caller and target process/session IDs, remote-session detection result, window station and desktop.
- RemoteApp versus full desktop, client and host Windows builds, graphics-remoting policy, and GPU acceleration configuration when relevant.
- Whether the same operation succeeds at the console and whether the failure began after reconnect or session migration.
Practical scenario
A media application enables a legacy queued-presentation feature on a local console, then the session is reconnected through Remote Desktop. The next DWM call returns DWM_E_REMOTING_NOT_SUPPORTED. The correct response is to tear down that presentation mode and use the application's ordinary remote-compatible rendering path. Repeatedly reconnecting the same DWM feature, reinstalling the display driver, or blaming media decoding would not address the documented capability boundary.
References
- Microsoft: DWM and graphics error codes
- Microsoft: DWM behavior and remoting changes
- Microsoft: queued present model deprecation
- Microsoft: Desktop Window Manager overview
Looking for a different code? Search another status or error code.