HRESULT 0x887A0032 (DXGI_ERROR_NON_COMPOSITED

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The operation failed because the compositor is not in control of the output.

Previous	Next
DXGI_ERROR_DYNAMIC_CODE_POLICY_VIOLATION	DXGI_ERROR_CACHE_CORRUPT

DXGI_ERROR_NON_COMPOSITED_UI

What Windows rejected: non composited ui

Windows reports DXGI_ERROR_NON_COMPOSITED_UI (0x887A0032) at the dxgi error checkpoint. Here, the requested operation depends on composited UI while the compositor is not controlling that output. That narrows the first investigation to Desktop Window Manager ownership of the output instead of the entire GPU stack.

DXGI_ERROR_NON_COMPOSITED_UI: Do not erase all shader caches or recreate every graphics object before preserving the first failing call. For DXGI_ERROR_NON_COMPOSITED_UI, Cache, policy, remote-session and device-lifetime failures have different recovery rules. For DXGI_ERROR_NON_COMPOSITED_UI, 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.

Build a useful diagnostic record

Capture item	Why it matters for `DXGI_ERROR_NON_COMPOSITED_UI`
Current graph state	DXGI factory, adapter, device, resource or cache session
Supporting trace	DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters
Object identity	Desktop Window Manager ownership of the output
Rejected boundary	the requested operation depends on composited UI while the compositor is not controlling that output
Decisive capture	DWM composition state, session type, full-screen exclusivity, output ownership, swap-chain model and window hierarchy

For DXGI_ERROR_NON_COMPOSITED_UI, 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_ERROR_NON_COMPOSITED_UI.

Separate state from capability

Freeze the DXGI_ERROR_NON_COMPOSITED_UI generation. Record DWM composition state, session type, full-screen exclusivity, output ownership, swap-chain model and window hierarchy. Before diagnosing DXGI_ERROR_NON_COMPOSITED_UI, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow DXGI_ERROR_NON_COMPOSITED_UI comparison. leave exclusive or noncomposited mode and repeat the same operation after DWM controls the target. During the DXGI_ERROR_NON_COMPOSITED_UI comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after DXGI_ERROR_NON_COMPOSITED_UI. For DXGI_ERROR_NON_COMPOSITED_UI, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_ERROR_NON_COMPOSITED_UI boundary was crossed.
Repeat DXGI_ERROR_NON_COMPOSITED_UI through a lifecycle transition. For DXGI_ERROR_NON_COMPOSITED_UI, 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_STATUS_NO_REDIRECTION is especially useful: DXGI_STATUS_NO_REDIRECTION is a successful alternate presentation path rather than a compositor-required failure. For DXGI_ERROR_NON_COMPOSITED_UI, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Perform the UI operation only on a composited target or use an API path documented for exclusive presentation. Repair of DXGI_ERROR_NON_COMPOSITED_UI 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_ERROR_NON_COMPOSITED_UI 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_ERROR_NON_COMPOSITED_UI; unrelated adapter, monitor and application state remains unchanged.
For DXGI_ERROR_NON_COMPOSITED_UI, debug-layer, ETW or driver diagnostics no longer report the rejected Desktop Window Manager ownership of the output contract during the same scenario.
The application handles recurrence of DXGI_ERROR_NON_COMPOSITED_UI without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `DXGI_ERROR_NON_COMPOSITED_UI`

For DXGI_ERROR_NON_COMPOSITED_UI, log DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters. When the DXGI_ERROR_NON_COMPOSITED_UI 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_ERROR_NON_COMPOSITED_UI 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_ERROR_NON_COMPOSITED_UI.

Technical references

Microsoft: DXGI error codes — background for the Desktop Window Manager ownership of the output boundary involved in DXGI_ERROR_NON_COMPOSITED_UI.
Microsoft: DXGI overview — background for the Desktop Window Manager ownership of the output boundary involved in DXGI_ERROR_NON_COMPOSITED_UI.
Microsoft: Direct3D 12 shader cache StoreValue — background for the Desktop Window Manager ownership of the output boundary involved in DXGI_ERROR_NON_COMPOSITED_UI.
Microsoft: Handle device-removed scenarios — background for the Desktop Window Manager ownership of the output boundary involved in DXGI_ERROR_NON_COMPOSITED_UI.

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