| Previous | Next |
| UI_E_PRIMITIVE_OUT_OF_BOUNDS | PLA_E_DCS_NOT_FOUND |
UI_E_WINDOW_CLOSED
The scope of UI_E_WINDOW_CLOSED is Windows Animation Manager: animation work reached a window whose close lifecycle is already in progress. Preserve 0x802A0201 beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the condition first
Window teardown can race queued animation updates, completion handlers, and composition work. The animation objects may still be referenced while their visual target and message-loop ownership are ending.
Keep neighboring conditions separate
UI_E_SHUTDOWN_CALLED is manager shutdown; WINDOW_CLOSED is the visual host lifecycle.
Do not retain an HWND value and assume it still names the same live target.
Incident record
- Window handle and generation.
- Close/destroy message timeline.
- Queued animation callbacks.
- Target object release order.
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: Cancel or detach animations when close begins.
- Next: Tag posted work with the window generation.
- Then: Drain or reject late callbacks.
- Finally: Release visual targets before the manager thread exits.
Three useful controls
- Fresh storyboard or animation object: a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: keep the timeline, transitions, and manager version fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: retain window handle and generation and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: cancel or detach animations when close begins. Hold constant: keep the original failing sample available for the final regression test.
Definition of done
Closure requires closing the window produces no late animation calls, while a new window generation animates normally; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
Looking for a different code? Search another status or error code.