| Previous | Next |
| UI_E_VALUE_NOT_DETERMINED | UI_E_BOOLEAN_EXPECTED |
UI_E_INVALID_OUTPUT
Within Windows Animation Manager, UI_E_INVALID_OUTPUT reports that a callback reported output that violated its interface contract. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Mechanism behind the code
During a this result investigation, Windows Animation is a stateful COM subsystem. 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.
Custom interpolation or priority callbacks participate in animation decisions through out parameters., S_OK is not enough when the returned values are invalid, nonfinite, outside the documented domain, or inconsistent with the accompanying result.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
High-value telemetry
| Capture | Diagnostic value |
|---|---|
| Callback IID and method for this HRESULT. | This provides a stable comparison across retries or another machine and helps test the Windows Animation Manager boundary. |
| All output parameters before return for this HRESULT. | This identifies the exact object or resource generation involved and helps test the Windows Animation Manager boundary. |
| Input values and animation time for this HRESULT. | This places the failure on the lifecycle or transaction timeline and helps test the Windows Animation Manager boundary. |
| Finite/range validation result for this HRESULT. | This separates caller input from environment and service state and helps test the Windows Animation Manager boundary. |
Decision table
- Fresh storyboard or animation object: for this HRESULT, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for this HRESULT, 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 this HRESULT, retain callback iid and method and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: initialize every out parameter on all branches. Hold constant: for this HRESULT, keep the original failing sample available for the final regression test.
Safe reduction procedure
When it is returned, use a disposable control object, repository copy, file, or device association where the subsystem permits it.
- First: Initialize every out parameter on all branches.
- Next: Reject NaN, infinity, and domain violations before returning.
- Then: Test cancellation and failure branches separately.
- Finally: Use a minimal callback with constant valid output as a control.
Do not erase the distinction
During an investigation, UI_E_BOOLEAN_EXPECTED is specifically an invalid success HRESULT used as a Boolean; INVALID_OUTPUT concerns returned data.
Do not clamp silently unless the callback contract explicitly allows clamping.
Successful outcome
Verify it with the original scenario, one boundary case, and one deliberate failure; success means the callback passes explicit output validation for boundary, cancellation, and ordinary inputs.
Technical references
The references below define the API family or storage/protocol behavior used to interpret it.
- 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.