What does HRESULT 0x087A0005 (DXGI_STATUS_NO_DESKTOP_ACCESS) mean?

DXGI_STATUS_NO_DESKTOP_ACCESS

Locate the failing graphics boundary: status no desktop access

Windows reports DXGI_STATUS_NO_DESKTOP_ACCESS (0x087A0005) at the dxgi status checkpoint. Here, the present occurred while the process could not display on the active desktop, such as during a secure-desktop transition. That narrows the first investigation to interactive desktop ownership instead of the entire GPU stack.

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

A controlled comparison

1. Freeze the DXGI_STATUS_NO_DESKTOP_ACCESS generation. Record session ID, desktop name, lock or Ctrl+Alt+Delete transition, HWND validity and Present timestamps. Before diagnosing DXGI_STATUS_NO_DESKTOP_ACCESS, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow DXGI_STATUS_NO_DESKTOP_ACCESS comparison. present before, during and after a controlled desktop switch without recreating unrelated resources. During the DXGI_STATUS_NO_DESKTOP_ACCESS comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after DXGI_STATUS_NO_DESKTOP_ACCESS. For DXGI_STATUS_NO_DESKTOP_ACCESS, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_STATUS_NO_DESKTOP_ACCESS boundary was crossed.
4. Repeat DXGI_STATUS_NO_DESKTOP_ACCESS through a lifecycle transition. For DXGI_STATUS_NO_DESKTOP_ACCESS, 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_SESSION_DISCONNECTED is especially useful: DXGI_ERROR_SESSION_DISCONNECTED indicates a disconnected session rather than a temporary different desktop. For DXGI_STATUS_NO_DESKTOP_ACCESS, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Correction and proof

Suspend visible rendering across desktop transitions and revalidate the window and swap chain when the interactive desktop returns. Repair of DXGI_STATUS_NO_DESKTOP_ACCESS 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_DESKTOP_ACCESS 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_DESKTOP_ACCESS; unrelated adapter, monitor and application state remains unchanged.
• For DXGI_STATUS_NO_DESKTOP_ACCESS, debug-layer, ETW or driver diagnostics no longer report the rejected interactive desktop ownership contract during the same scenario.
• The application handles recurrence of DXGI_STATUS_NO_DESKTOP_ACCESS without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for DXGI_STATUS_NO_DESKTOP_ACCESS

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

Technical references

• Microsoft: DXGI status codes — background for the interactive desktop ownership boundary involved in DXGI_STATUS_NO_DESKTOP_ACCESS.
• Microsoft: DXGI overview and presentation — background for the interactive desktop ownership boundary involved in DXGI_STATUS_NO_DESKTOP_ACCESS.
• Microsoft: DXGI_PRESENT flags — background for the interactive desktop ownership boundary involved in DXGI_STATUS_NO_DESKTOP_ACCESS.
• Microsoft: DXGI best practices — background for the interactive desktop ownership boundary involved in DXGI_STATUS_NO_DESKTOP_ACCESS.

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