| Previous | Next |
| VDS_E_PARTITION_NON_DATA | VDS_E_VOLUME_SYNCHRONIZING |
VDS_E_CRITICAL_PLEX
A mirrored VDS volume contains multiple plexes, but a system or boot role can be associated with the plex currently used for startup. This HRESULT protects that active critical plex from operations such as removal or topology changes that would invalidate the running machine's boot path. It is a role restriction, not a statement that the plex is unhealthy.
Why this state matters
Enumerate all plexes and their properties, then identify which one is the current boot or system plex before choosing a repair or break operation. A healthy alternate plex may still lack a usable boot environment. Do not select a different plex by disk number alone; correlate volume topology with boot configuration and, for recovery planning, verify that the alternate disk has a documented boot path.
Diagnostic focus
- Enumerate plex GUIDs, types, sizes, health, and transition state.
- Identify the active system and boot roles independently of mirror health.
- Confirm that any intended alternate plex has a prepared and tested boot environment.
- Do not force-remove the critical plex as a shortcut around a topology precondition.
Technical references
MS-VDS error codes · VDS Volume Object · VDS_VOLUME_PLEX_PROP · IVdsVolume · Set up dynamic boot partition mirroring on GPT disks
Looking for a different code? Search another status or error code.