| Previous | Next |
| STATUS_GRAPHICS_INVALID_COPYPROTECTION_TYPE | STATUS_GRAPHICS_INVALID_SCANLINE_ORDERING |
STATUS_GRAPHICS_UNASSIGNED_MODESET_ALREADY_EXISTS
Only one unassigned mode set may exist for the same object
During mode enumeration and recommendation, WDDM interfaces can create mode sets that are not yet assigned to a specific source or target state. This status means code attempted to create another unassigned mode set where one already exists.
The problem is usually cleanup or ownership. A previous enumeration pass created an unassigned mode set and did not release, assign, or discard it before retrying. In recovery paths, the second attempt then fails even though the underlying modes are valid.
What to check
- Track ownership of unassigned mode-set handles across enumeration, pruning, and failure exits.
- Release or assign the existing unassigned set before creating another.
- Check retry loops that restart recommendation without cleaning objects from the first attempt.
References
- Microsoft: VidPN objects and interfaces
- Microsoft: Enumerating cofunctional VidPN source and target modes
Looking for a different code? Search another status or error code.