What does HRESULT 0x88980800 (DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED) mean?

DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED

What Windows rejected: window already composed

The useful interpretation of DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED (0x88980800) starts at the dcomp boundary: the application attempted to create a second composition target for a window already associated with one. In practical terms, inspect DirectComposition target ownership for an HWND before changing application-wide graphics settings.

This result: DirectComposition batches changes until Commit, while surface drawing has its own BeginDraw/EndDraw lifetime. Treat those two transactions separately in traces and cleanup. 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

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 this result.

Separate state from capability

1. Freeze the result generation. Record HWND, process and thread IDs, existing IDCompositionTarget lifetime, topmost flag and target creation stack. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow this result comparison. create one target successfully and issue a second CreateTargetForHwnd for the same window. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after it. for it, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the boundary was crossed.
4. Repeat it through a lifecycle transition. for it, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that it does not reuse stale handles.

The comparison with DCOMPOSITION_ERROR_ACCESS_DENIED is especially useful: DCOMPOSITION_ERROR_ACCESS_DENIED is returned when the window belongs to another process. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Keep one target owner per window and release or reuse it during visual-tree replacement. Repair of it 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 result 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 it; unrelated adapter, monitor and application state remains unchanged.
• debug-layer, ETW or driver diagnostics no longer report the rejected DirectComposition target ownership for an HWND contract during the same scenario.
• The application handles recurrence of it without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes

Log BeginDraw/EndDraw or target-creation sequence, Commit result, HWND ownership and CheckDeviceState output. When the 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 it 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 it.

Technical references

• Microsoft: DirectComposition error codes — background for the DirectComposition target ownership for an HWND boundary involved in it.
• Microsoft: DirectComposition reference
• Microsoft: IDCompositionDevice::Commit
• Microsoft: IDCompositionDevice::CheckDeviceState

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