| Previous | Next |
| VDS_E_DELETE_WITH_BOOTBACKING | FSRM_E_NOT_FOUND |
VDS_E_FORMAT_WITH_BOOTBACKING
Formatting is destructive to the file-system layer even when the underlying volume object remains. VDS therefore rejects format when the selected volume supplies backing storage for the Windows boot volume. This is distinct from the general FormatEx2 rule that denies formatting the boot or system volume itself: a backing relationship can make another storage object critical to the boot path.
Why this state matters
Resolve the dependency before investigating file-system parameters such as NTFS versus ReFS or allocation-unit size. Enumerate the boot volume topology and map it to plexes and extents. If the target contributes to that chain, formatting it would invalidate the boot volume regardless of the chosen format options. Migrate the boot dependency first and confirm the resulting boot path before returning to the format operation.
Diagnostic focus
- Confirm the exact VDS volume object passed to the format method.
- Map the Windows boot volume to all plexes and underlying disk extents.
- Separate a boot-backing restriction from file-system format capability errors.
- After migration, verify bootability before formatting former backing storage.
Technical references
MS-VDS error codes · IVdsVolumeMF3::FormatEx2 · VDS Volume Object · VDS_VOLUME_PLEX_PROP · BCDBoot command-line options
Looking for a different code? Search another status or error code.