| 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 boundary first
When it is returned, Windows Animation is a stateful COM subsystem. During a this result investigation, animation variables, transitions and storyboards are created under a manager, scheduled against a monotonic animation time, updated before drawing, and eventually sealed or released. A visible glitch can therefore be downstream of a lifecycle, ownership, timeline, callback, or numeric contract failure.
During a this result investigation, 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.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Keep neighboring conditions separate
When it is returned, 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 for this HRESULT
| Capture | Diagnostic value |
|---|---|
| Window handle and generation for it. | This places the failure on the lifecycle or transaction timeline and helps test the Windows Animation Manager boundary. |
| Close/destroy message timeline for it. | This separates caller input from environment and service state and helps test the Windows Animation Manager boundary. |
| Queued animation callbacks for it. | This provides a stable comparison across retries or another machine and helps test the Windows Animation Manager boundary. |
| Target object release order for it. | This identifies the exact object or resource generation involved and helps test the Windows Animation Manager boundary. |
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: for it, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for it, 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: for it, 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: for it, keep the original this result sample available for the final regression test.
Definition of done
Closure for it 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.
- Microsoft: Windows Animation error codes
- Microsoft: Windows Animation overview
- Microsoft: Schedule a storyboard
- Microsoft: IUIAnimationManager interface
Looking for a different code? Search another status or error code.