What does HRESULT 0xC0262349 (ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED) mean?

ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED

Interpret the result in its owning layer: graphics multisampling not supported

The useful interpretation of ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED (0xC0262349) starts at the vidpn boundary: the path cannot scan out the requested multisampled primary surface arrangement. In practical terms, inspect VidPN present-path multisampling mode before changing application-wide graphics settings.

Resolve before scan-out when required

Multisampling can be valid for an application render target while unsupported for the primary surface used on a specific present path. Record sample count, sample quality, source format and whether a resolve operation occurs before presentation. The focused control renders into the same multisampled resource, resolves to a single-sample surface and presents that surface. Success demonstrates a scan-out restriction rather than absence of multisample rendering support.

ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED: VidPN handles and subobjects are generation-bound. For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, A monitor hot-plug, docking action, session switch or mode commit can invalidate an otherwise well-formed cached object. For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, the built-in one-line message identifies the immediate result; diagnosis also needs the producing API, object ownership and the display generation current at the time.

Capture before recreating objects

For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, preserve the unsigned HRESULT, symbolic name, first failing API and timestamp in one record. If cleanup later fails too, keep that secondary result separately from ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.

Reproduce one variable at a time

1. Freeze the ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED generation. Record sample count, sample quality, source format, path support and resolve behavior. Before diagnosing ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED comparison. resolve into a single-sample presentation surface and compare. During the ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED. For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED boundary was crossed.
4. Repeat ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED through a lifecycle transition. For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that this result does not reuse stale handles.

The comparison with ERROR_GRAPHICS_INVALID_PIXELFORMAT is especially useful: ERROR_GRAPHICS_INVALID_PIXELFORMAT concerns the source format independent of sample count. For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Recovery contract

Perform multisampling in the render target and resolve before presentation when required. Repair of ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED is complete only when the original call succeeds or returns its documented nonfatal status and the same lifetime test remains correct after a second display transition.

• The ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED trace identifies one producing API and one current graphics object, rather than only the final UI symptom.
• The passing run changes exactly the condition described for ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED; unrelated adapter, monitor and application state remains unchanged.
• For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, debug-layer, ETW or driver diagnostics no longer report the rejected VidPN present-path multisampling mode contract during the same scenario.
• The application handles recurrence of ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED

For ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED, log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data. When the ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED path returns a count, size, status flag or replacement object, retain it even on a nonfatal result because it can direct the next call.

A production fallback for ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED should be explicit: pause rendering, re-enumerate, rebuild one cache entry, recreate a device, or decline a protected path only when this layer calls for that action. Reinstalling every display component, deleting all caches or forcing a resolution change is not an evidence-based fix for ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.

Technical references

• Microsoft: Introduction to Video Present Networks — background for the VidPN present-path multisampling mode boundary involved in ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.
• Microsoft: VidPN objects and interfaces — background for the VidPN present-path multisampling mode boundary involved in ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.
• Microsoft: Enumerating cofunctional VidPN modes — background for the VidPN present-path multisampling mode boundary involved in ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.
• Microsoft: Determining VidPN support — background for the VidPN present-path multisampling mode boundary involved in ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED.

Looking for a different code? Search another status or error code.