| Previous | Next |
| ERROR_VID_PARTITION_NAME_TOO_LONG | ERROR_VID_PARTITION_ALREADY_EXISTS |
ERROR_VID_MESSAGE_QUEUE_NAME_TOO_LONG
ERROR_VID_MESSAGE_QUEUE_NAME_TOO_LONG is HRESULT 0xC0370007 in the VID message queue naming limit area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the generated name of a host-side VID message queue. Record the first returning operation and host-side event before a management layer retries or translates it.
Why this HRESULT is specific
The queue name exceeds the accepted limit, often after partition identity, channel role, and instance suffixes are combined. Diagnose the final generated value rather than the user-facing VM name.
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: PARTITION_NAME_TOO_LONG applies to partition identity. Queue names can fail independently because channel or device suffixes expand the string.
Records worth collecting
| Evidence | Why it changes the diagnosis |
|---|---|
| Generated queue name | Record complete escaped value and UTF-16 length. |
| Component lengths | Keep partition token, channel/device role, direction, and instance suffix. |
| Collision strategy | Record whether shortening uses a stable hash and preserves uniqueness. |
| Lifecycle path | Note whether create, restore, migration, or device hot-add generated the name. |
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.
A reproducible test plan
- Bound each human-readable component and reserve space for generated suffixes.
- Use stable compact IDs for queue identity.
- Test maximum-length VM and device names together.
- Verify shortening cannot map two live queues to the same name.
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.
Comparison matrix
Across these controls for it, preserve the generated name of a host-side VID message queue as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Fresh channel generation — this result | 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. |
| 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. |
Misleading shortcuts
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.
Verification after repair
The same configuration creates all required queues across restart and migration without truncation collisions. 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.