| Previous | Next |
| STATUS_VSM_DMA_PROTECTION_NOT_IN_USE | STATUS_VOLSNAP_ACTIVATION_TIMEOUT |
STATUS_VOLSNAP_BOOTFILE_NOT_VALID
Persistent snapshot support failed at the bootfile requirement
STATUS_VOLSNAP_BOOTFILE_NOT_VALID belongs to persistent snapshot infrastructure. VSS defines persistent shadow-copy attributes and persistent contexts whose snapshots can survive requester release and, when marked persistent, remain part of the shadow-copy set across reboot-oriented lifecycle handling.
This status should not be reduced to “the source volume is low on free space” or “a VSS writer timed out.” The NTSTATUS specifically identifies the bootfile as too small for persistent snapshots. Microsoft’s public VSS documentation describes persistence semantics, but it does not provide a universal public size formula that applications should hard-code for this VolSnap bootfile requirement.
Preserve VolSnap and System event data and identify which persistent snapshot operation was being activated or created. Do not invent a registry tweak or resize value from the NTSTATUS name alone. Use platform-supported storage and VSS diagnostics to determine why the persistent-snapshot support files cannot satisfy the current configuration.
What to inspect
- The snapshot context and whether the shadow-copy set requests persistence.
- VolSnap and System events around boot or persistent snapshot activation.
- Recent changes to the system volume, boot storage, snapshot configuration, or persistent shadow-copy inventory.
References
- Microsoft: Shadow Copy Context Configurations
- Microsoft: VSS_VOLUME_SNAPSHOT_ATTRIBUTES
- Microsoft: VSS_SNAPSHOT_CONTEXT
- Microsoft: Volume Shadow Copy Service
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.