| Previous | Next |
| DXGI_STATUS_CLIPPED | DXGI_STATUS_NO_DESKTOP_ACCESS |
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.
A DXGI status can describe a successful or temporarily invisible presentation. Converting every non-S_OK value into device recreation destroys useful state and can create a full-screen transition loop.
Evidence that makes the result actionable
| Capture item | Why it matters |
|---|---|
| What to capture | driver model, swap effect, composition state, output ownership, session type and the exact call returning the status |
| Current graph state | swap chain, target window, output and Present call |
| Supporting trace | Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity |
| Object identity | DXGI-to-DWM transport choice |
| Rejected condition | the display driver requested a path that does not use the normal shared-resource redirection channel to Desktop Window Manager |
A controlled comparison
- Capture the failing state. Record driver model, swap effect, composition state, output ownership, session type and the exact call returning the status.
- Repeat the same swap-chain operation with ordinary windowed composition and with the driver-specific path that triggers no redirection.
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.
Correction and proof
Preserve the driver-selected path and avoid assuming that every successful presentation is redirected through a shared surface.
- debug-layer, ETW or driver diagnostics no longer report the rejected DXGI-to-DWM transport choice contract during the same scenario.
Implementation notes
A production fallback 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 this condition.
Technical references
- Microsoft: DXGI status codes — background for the DXGI-to-DWM transport choice.
- Microsoft: DXGI overview and presentation
- Microsoft: DXGI_PRESENT flags
- Microsoft: DXGI best practices
Looking for a different code? Search another status or error code.