| Previous | Next |
| UI_E_DIFFERENT_OWNER | UI_E_FP_OVERFLOW |
UI_E_AMBIGUOUS_MATCH
UI_E_AMBIGUOUS_MATCH belongs to Windows Animation Manager. It marks a lookup criterion matched more than one animation object. The useful starting point is the exact API, object and state transition that returned 0x802A000A, because a shell or application message can hide that boundary.
Where this result is raised
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. During a this result investigation, a visible glitch can therefore be downstream of a lifecycle, ownership, timeline, callback, or numeric contract failure.
When it is returned, name, tag, or property-based lookup must identify a single target when the API expects uniqueness. During a this result investigation, duplicate application tags or insufficient constraints can make a valid object collection impossible to resolve deterministically.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Evidence worth collecting
- Lookup criteria and namespace. for this HRESULT, this pins the event to an object or resource generation within the Windows Animation Manager boundary.
- All matching object identities. for this HRESULT, this places the event on the lifecycle or transaction timeline within the Windows Animation Manager boundary.
- Tag or name assignment history. for this HRESULT, this separates caller input from environment and service state within the Windows Animation Manager boundary.
- Scope in which uniqueness is required. for this HRESULT, this creates a stable comparison across retries or another machine within the Windows Animation Manager boundary.
A controlled diagnostic sequence
During a this result investigation, reduce the case while preserving the condition described by the HRESULT.
- First: Enumerate and log every match.
- Next: Strengthen the criterion with owner or object identity.
- Then: Assign stable unique tags when objects are created.
- Finally: Test duplicate registration as a negative case.
How to interpret comparison tests
| Control | Interpretation | Hold constant |
|---|---|---|
| Same input, fresh object or connection | If the result disappears, retained lifecycle or ownership state is implicated. | While diagnosing this result, keep the original data, account, device, or timeline parameters unchanged. |
| Same object, reduced operation | If the result follows one specific transition, statement, file, or ceremony step, the failure is localized. | While diagnosing it, remove only unrelated work and keep the first failing boundary visible. |
| Same operation, controlled environment | If the result follows one machine, account, volume, network, or device, environment matters. | While diagnosing it, keep versions and identity explicit rather than comparing only the final message. |
What this code does not justify
UI_E_VALUE_NOT_SET indicates absence; AMBIGUOUS_MATCH indicates more than one candidate.
Do not pick the first enumeration result because ordering may be incidental.
Verification after correction
Treat it as corrected only when the lookup returns exactly one intended object and the duplicate test is rejected explicitly; retain the original negative case so fallback cannot be mistaken for repair.
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.