| Previous | Next |
| ERROR_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT | ERROR_GRAPHICS_NO_PREFERRED_MODE |
ERROR_GRAPHICS_MODE_NOT_PINNED
VidPN source or target has no pinned mode
ERROR_GRAPHICS_MODE_NOT_PINNED is HRESULT 2499335 (0x00262307) from winerror.h. The documented description is “No mode is pinned on the specified VidPN source/target.” In the Windows display topology or Desktop Window Manager operation, the value reports a nonfailure state that must not be collapsed into plain S_OK.
A cleared severity bit does not make the return equivalent to ordinary completion; the postcondition remains specific.
What must be true before accepting it
Verify that the API permits an unpinned mode at this phase and the caller does not dereference a nonexistent pinned mode. Without the boundary check, the HRESULT can hide stale output, pending ownership, or omitted work.
Where the status is encountered
- VidPN mode-set, topology, and path negotiation; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
- Display miniport and graphics-kernel dataset enumeration;
- DWM composition and GDI redirection-surface handling;
Correct handling and recovery
Enumerate the mode set or establish a valid pinned mode before operations that require one. Preserve the source, target, and topology generation.
A new attempt following this result should be triggered by a meaningful transition, not merely by elapsed time.
Practical scenario
A display miniport query runs before topology commitment and finds no pinned source mode. It waits for mode selection instead of reading null mode data.
Difference from nearby results
NO_PREFERRED_MODE means modes exist without preference; MODE_NOT_PINNED means no current pinned choice exists.
References
Looking for a different code? Search another status or error code.