| 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. It applies to the generated name of a host-side VID message queue.
Why this result 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.
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. |
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.
Reproduce this condition 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
| Control | Interpretation | Hold constant |
|---|---|---|
| Fresh channel generation | 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 test. |
| Controlled stall or burst | 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 | If it disappears with serialized ownership, the queue, handler, acknowledgement, or delivery race is implicated. | Preserve message type, partition, target VP, and queue capacity. |
Misleading shortcuts
Verification after repair
The same configuration creates all required queues across restart and migration without truncation collisions.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft TLFS: inter-partition communication — used to interpret this result.
- Microsoft TLFS: HV_MESSAGE — used to interpret this result.
- Microsoft: Hyper-V architecture — used to interpret this result.
Looking for a different code? Search another status or error code.