| Previous | Next |
| ERROR_VID_PARTITION_NAME_NOT_FOUND | ERROR_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT |
ERROR_VID_MESSAGE_QUEUE_ALREADY_EXISTS
ERROR_VID_MESSAGE_QUEUE_ALREADY_EXISTS is HRESULT 0xC037000B in the VID queue creation identity area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: creation of a VID message queue whose name or identity is already registered. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The queue already exists in the current partition/worker generation. Determine whether the caller should attach to that queue, whether initialization ran twice, or whether teardown left an orphan.
Hyper-V architecture documentation identifies VID as the component that provides partition, virtual-processor, and memory-management services., many ERROR_VID_* values describe internal host objects rather than a public API that administrators should call directly. Accordingly, diagnose this result through the named object/state, the VMMS or Worker event chain, and the operation that produced it; do not invent a user-mode VID call from the constant name.
Neighboring result: QUEUE_FULL concerns capacity of an existing queue; ALREADY_EXISTS concerns duplicate creation before normal message flow.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Queue identity | Record name, handle if available, partition, direction, and message role. |
| Existing owner | Capture consumer thread/module and creation correlation ID. |
| Duplicate path | Keep second create stack and initialization phase. |
| Cleanup record | Compare queue create/close/delete counts across failures. |
Preserve identifiers and counts without dumping guest secrets or unrelated memory. Useful this result timestamps include the last successful operation, first failure, any automatic retry, and the object-generation change that followed.
Reduce the case safely
- Make queue creation single-owner and publish the handle only after success.
- Use generation-scoped names for replacement workers.
- Inject failures after creation to prove rollback removes the queue.
- Do not attach to an existing queue until message format and owner are verified.
Exercise this result with bounded producers and a fully instrumented consumer. Preserve message ordering, queue generation, handler ownership, target VP, and acknowledgement timestamps while changing only one concurrency condition.
What comparison can tell you
Across these controls for it, preserve creation of a VID message queue whose name or identity is already registered as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Controlled stall or burst — this result | Deliberately slow the consumer or bound the producer rate. The threshold at which it appears identifies backpressure versus lifecycle failure. | Record queue depth, oldest-item age, and acknowledgement timing. |
| Single producer and consumer — it | If it disappears with serialized ownership, the queue, handler, acknowledgement, or delivery race is implicated. | Preserve message type, partition, target VP, and queue capacity for it. |
| Fresh channel generation — it | A new queue or handler generation changing it points to stale registration, backlog, or incomplete teardown. | Keep payload, producer order, and host build unchanged in the result test. |
Do not erase the evidence
A VM or service restart can empty queues and replace handler generations, temporarily hiding it. Before clearing the result channel, capture depth, oldest item, owner, delivery sequence, and acknowledgement state.
Closure criteria
Only one queue is created for each intended channel, and lifecycle stress leaves no queue from an earlier generation. Repeat the original operation under the original supported conditions and retain one deliberate negative control. A management command succeeding on a different object is not sufficient to close this incident.
Technical references
These sources define it and the public Hyper-V architecture surrounding the internal state. They do not create a public user-mode VID API for the named object.
- Microsoft Open Specifications: HRESULT values — used to interpret the boundary.
- Microsoft TLFS: inter-partition communication — used to interpret the boundary.
- Microsoft TLFS: HV_MESSAGE — used to interpret the boundary.
- Microsoft: Hyper-V architecture — used to interpret the boundary.
Looking for a different code? Search another status or error code.