| Previous | Next |
| STATUS_VID_PARTITION_NAME_NOT_FOUND | STATUS_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT |
STATUS_VID_MESSAGE_QUEUE_ALREADY_EXISTS
Duplicate VID message queue name
STATUS_VID_MESSAGE_QUEUE_ALREADY_EXISTS is a queue namespace collision. It is more specific than a generic object-name collision because the failing object is the communication queue used by the host virtualization infrastructure.
This usually means the caller retried queue creation without fully closing the previous queue, or two components derived the same internal queue name for different purposes.
A VID message queue with the requested host-side name already exists, so queue creation encountered a namespace collision. Determine whether the previous queue is still legitimately owned or was left behind by a partial startup; the queue name and creator sequence are more useful than guest network traces.
What to inspect
- Identify the queue owner and whether the previous handle is still open.
- Check for retry loops after partial device, memory, or notification setup failures.
- Compare queue names across cloned/imported VM configurations if the issue follows migration or restore.
References
- Microsoft TLFS: inter-partition communication
- Microsoft TLFS: HV_MESSAGE
- Microsoft: Hyper-V architecture
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.