| Previous | Next |
| ERROR_HV_INVALID_PARTITION_STATE | ERROR_HV_UNKNOWN_PROPERTY |
ERROR_HV_OPERATION_DENIED
A valid hypercall can still violate a state-dependent rule
ERROR_HV_OPERATION_DENIED differs from an unknown hypercall or malformed input: the operation is recognized, but the current configuration makes it illegal. Examples include modifying a write-once security setting, changing an early partition property after initialization, or acting on an object that has begun finalization.
Use the specific hypercall documentation to identify its preconditions and one-way transitions. Record the current partition, VP, VTL, and device state together with all relevant flags. Repeating the call without changing state cannot succeed, and forcing a generic VM restart may hide the ordering defect instead of proving which prerequisite was violated.
How to distinguish denial from bad input
- Confirm that the call code and parameter encoding are supported.
- Identify properties that are early-only, write-once, or valid only while stopped.
- Check whether finalization, VTL enablement, or device detach has already begun.
- Compare the current state with the documented preconditions for that hypercall.
References
- Microsoft TLFS: supported hypercalls
- Microsoft TLFS: early partition-property boundary
- Microsoft TLFS: write-once and ordered VTL configuration
Looking for a different code? Search another status or error code.