| Previous | Next |
| ERROR_VID_MBPS_ARE_LOCKED | ERROR_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED |
ERROR_VID_MESSAGE_QUEUE_CLOSED
ERROR_VID_MESSAGE_QUEUE_CLOSED is HRESULT 0xC037001A in the VID queue closure state area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a known VID message queue that has entered its closed lifecycle state. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The queue identity is recognized, but enqueue, receive, or notification work arrived after closure began. Determine whether shutdown ordering is correct or a producer/consumer outlived the channel.
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: INVALID_MESSAGE_QUEUE_HANDLE means the token itself is not valid; QUEUE_FULL means the live queue lacks capacity. CLOSED is a lifecycle result.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Close initiator | Record thread, reason, and timestamp that closed the queue. |
| Late operation | Capture enqueue/dequeue/association request and its owner. |
| Drain state | Keep remaining depth, outstanding acknowledgements, and final consumer result. |
| Generation handoff | Record replacement queue creation and publication order. |
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
- Stop producers before closing and drain or cancel according to message semantics.
- Publish a replacement only after its consumer is ready.
- Make close idempotent but reject new work immediately.
- Test worker crash, VM stop, and migration handoff.
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 a known VID message queue that has entered its closed lifecycle state as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Single producer and consumer — this result | 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. |
| Controlled stall or burst — it | 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. |
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
Shutdown has a documented final-message boundary, no producer writes after close, and restart routes work only to the new queue. 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.