What does HRESULT 0x087A0004 (DXGI_STATUS_NO_REDIRECTION) mean?

DXGI_STATUS_NO_REDIRECTION

Locate the failing graphics boundary: status no redirection

DXGI_STATUS_NO_REDIRECTION, value 0x087A0004, is produced by dxgi status when the display driver requested a path that does not use the normal shared-resource redirection channel to Desktop Window Manager. The investigation should stay attached to DXGI-to-DWM transport choice and to the exact generation in which it was obtained.

DXGI_STATUS_NO_REDIRECTION: A DXGI status can describe a successful or temporarily invisible presentation. For DXGI_STATUS_NO_REDIRECTION, Converting every non-S_OK value into device recreation destroys useful state and can create a full-screen transition loop. For DXGI_STATUS_NO_REDIRECTION, 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.

Evidence that makes this result actionable

For DXGI_STATUS_NO_REDIRECTION, 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 DXGI_STATUS_NO_REDIRECTION.

A controlled comparison

1. Freeze the DXGI_STATUS_NO_REDIRECTION generation. Record driver model, swap effect, composition state, output ownership, session type and the exact call returning the status. Before diagnosing DXGI_STATUS_NO_REDIRECTION, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow DXGI_STATUS_NO_REDIRECTION comparison. repeat the same swap-chain operation with ordinary windowed composition and with the driver-specific path that triggers no redirection. During the DXGI_STATUS_NO_REDIRECTION comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after DXGI_STATUS_NO_REDIRECTION. For DXGI_STATUS_NO_REDIRECTION, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_STATUS_NO_REDIRECTION boundary was crossed.
4. Repeat DXGI_STATUS_NO_REDIRECTION through a lifecycle transition. For DXGI_STATUS_NO_REDIRECTION, 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 DXGI_ERROR_NON_COMPOSITED_UI is especially useful: DXGI_ERROR_NON_COMPOSITED_UI is a failure caused by compositor ownership, not a successful transport status. For DXGI_STATUS_NO_REDIRECTION, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Correction and proof

Preserve the driver-selected path and avoid assuming that every successful presentation is redirected through a shared surface. Repair of DXGI_STATUS_NO_REDIRECTION 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 DXGI_STATUS_NO_REDIRECTION 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 DXGI_STATUS_NO_REDIRECTION; unrelated adapter, monitor and application state remains unchanged.
• For DXGI_STATUS_NO_REDIRECTION, debug-layer, ETW or driver diagnostics no longer report the rejected DXGI-to-DWM transport choice contract during the same scenario.
• The application handles recurrence of DXGI_STATUS_NO_REDIRECTION without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for DXGI_STATUS_NO_REDIRECTION

For DXGI_STATUS_NO_REDIRECTION, log Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity. When the DXGI_STATUS_NO_REDIRECTION 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 DXGI_STATUS_NO_REDIRECTION 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 DXGI_STATUS_NO_REDIRECTION.

Technical references

• Microsoft: DXGI status codes — background for the DXGI-to-DWM transport choice boundary involved in DXGI_STATUS_NO_REDIRECTION.
• Microsoft: DXGI overview and presentation — background for the DXGI-to-DWM transport choice boundary involved in DXGI_STATUS_NO_REDIRECTION.
• Microsoft: DXGI_PRESENT flags — background for the DXGI-to-DWM transport choice boundary involved in DXGI_STATUS_NO_REDIRECTION.
• Microsoft: DXGI best practices — background for the DXGI-to-DWM transport choice boundary involved in DXGI_STATUS_NO_REDIRECTION.

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