| Previous | Next |
| ERROR_HV_INVALID_ALIGNMENT | ERROR_HV_ACCESS_DENIED |
ERROR_HV_INVALID_PARAMETER
The call frame was accepted, but its requested operation was not
ERROR_HV_INVALID_PARAMETER is intentionally broader than an invalid hypercall control value. The exact rule comes from the individual hypercall. For inter-partition delivery, for example, HvCallPostMessage rejects a zero message type, a message type with its high bit set, or a payload larger than 240 bytes. HvCallSignalEvent rejects a flag number outside the destination port's declared flag range.
Therefore the symbolic status alone is not enough to identify the bad field. The hypercall code and the complete serialized input must be kept together in diagnostics.
How to diagnose it
- Identify the actual hypercall and validate its documented ranges, reserved fields and object-type requirements.
- For message delivery, log message type and payload size; for event delivery, log the requested relative flag number and port configuration.
- Do not reinterpret this as
ERROR_HV_INVALID_HYPERCALL_INPUT: the control word may be valid while an API-level value is not. - Preserve the raw input before rebuilding it, because a wrapper can otherwise hide a truncated or incorrectly packed field.
Microsoft TLFS: HvCallPostMessage · Microsoft TLFS: HvCallSignalEvent
Looking for a different code? Search another status or error code.