What does HRESULT 0xC0370005 (ERROR_VID_INVALID_OBJECT_NAME) mean?

 
Could be also:
ConstantTypeOS
STATUS_VID_INVALID_OBJECT_NAMENTSTATUSWindows
Previous Next
ERROR_VID_HANDLER_NOT_PRESENT ERROR_VID_PARTITION_NAME_TOO_LONG

ERROR_VID_INVALID_OBJECT_NAME

ERROR_VID_INVALID_OBJECT_NAME is HRESULT 0xC0370005 in the VID object naming area of the Windows virtualization stack. It applies to syntax or semantics of a partition or message-queue name passed to VID.

Where the result originates

The name fails the internal object-naming contract before normal lookup or creation. Preserve exact characters, length, encoding, terminator handling, and whether the value was generated from an external VM name.

Neighboring result: NAME_TOO_LONG identifies length specifically; NAME_NOT_FOUND concerns lookup of a syntactically valid name. INVALID_OBJECT_NAME is the broader validation failure.

Build an incident record

EvidenceWhy it changes the diagnosis
Raw nameRecord escaped UTF-16 code units, length excluding and including terminator, and source field.
Object typeIdentify partition versus message queue and the operation using the name.
Normalization pathKeep trimming, case conversion, GUID formatting, and prefix construction steps.
Control nameUse a minimal known-good generated name through the same wrapper.

Run narrow checks

  1. Reject embedded NULs and invalid serialization before the VID call.
  2. Keep display names separate from internal stable identifiers.
  3. Test boundary lengths and non-ASCII input without lossy conversion.
  4. Do not sanitize by silently changing identity; log the mapping explicitly.

Interpret three controls

ControlInterpretationHold constant
Fresh owned objectA clean lifecycle changing this result implicates duplicate initialization, leaked ownership, stale lookup, or incomplete rollback.Preserve request flags and topology while changing only object instance.
Same request on a compatible hostIf it follows one host, compare resource limits, topology, build, and inventory before altering VM data.Use the same request and leave virtual disks unchanged in the result comparison.
One operation parameterChange one count, name, identity, or state transition. If it moves, the selected condition is causal rather than the VM as a whole.Keep host build, VM ID, and returning operation fixed.

Keep neighboring states separate

Prove the correction

A valid fix accepts documented names, rejects malformed input deterministically, and preserves stable object identity across restart.

Technical references


Looking for a different code? Search another status or error code.