| 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
Name, tag, or property-based lookup must identify a single target when the API expects uniqueness. Duplicate application tags or insufficient constraints can make a valid object collection impossible to resolve deterministically.
Evidence worth collecting
- Lookup criteria and namespace.
- All matching object identities.
- Tag or name assignment history.
- Scope in which uniqueness is required.
A controlled diagnostic sequence
- 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 operation, controlled environment | If the result follows one machine, account, volume, network, or device, environment matters. | 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
Looking for a different code? Search another status or error code.