| Previous | Next |
| STATUS_STORAGE_LOST_DATA_PERSISTENCE | STATUS_PARTITION_TERMINATING |
STATUS_VRF_CFG_ENABLED
The rejected operation is a volatile Driver Verifier reconfiguration
STATUS_VRF_CFG_ENABLED is narrowly about Driver Verifier volatile settings when CFG is enabled. Volatile Verifier settings are runtime changes intended for debugging; Microsoft documents that some verifier options can be activated or changed without rebooting, but not every configuration is valid in every protection state.
Control Flow Guard (CFG) is a platform security mitigation that restricts indirect call targets. The status should therefore not be treated as a generic Driver Verifier failure or as evidence that the target driver failed verification. It says the requested volatile-setting operation is incompatible with the current CFG-enabled context.
What to record
- The exact
verifiercommand, flags and target drivers used for the volatile change. - The Verifier settings active before the request and whether the change was attempted at runtime.
- CFG state and the Windows build on the test machine.
- Whether the same verification goal can be configured persistently for the next boot instead of through volatile settings.
Do not disable CFG as a routine workaround on a production system. Driver Verifier is a testing tool and can deliberately stress drivers; reproduce the intended verifier configuration in a controlled test environment and choose a supported configuration path.
References
- Microsoft: Using Driver Verifier volatile settings
- Microsoft: Driver Verifier command line
- Microsoft: Control Flow Guard
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.