Fix VSS Snapshot Failure 0x80042308 on a Volume With BitLocker Suspended

When you attempt to create a Volume Shadow Copy Service snapshot on a Windows 11 volume that has BitLocker Drive Encryption suspended, you may receive error 0x80042308. This error indicates that the VSS writer failed during the snapshot creation process. The root cause is a conflict between the BitLocker suspension state and the VSS writer’s requirement for a consistent volume state. This article explains why the error occurs, provides step-by-step fixes to resolve it, and covers related failure patterns you may encounter.

Why BitLocker Suspension Causes VSS Snapshot Error 0x80042308

The Volume Shadow Copy Service relies on consistent point-in-time snapshots of a volume. When BitLocker is suspended, the volume is still encrypted, but the encryption key is exposed or held in an unprotected state. VSS writers, especially the BitLocker writer, detect this inconsistent security state and fail the snapshot operation. The error 0x80042308 translates to VSS_E_WRITERERROR_RETRYABLE, meaning the writer encountered a transient problem that may be resolved by retrying after the underlying issue is fixed.

BitLocker suspension is commonly used during firmware updates or system maintenance. After the maintenance completes, BitLocker should be resumed. If you forget to resume protection, any backup or system restore point creation that uses VSS will fail with this error. The fix is straightforward: resume BitLocker protection or fully decrypt the volume if suspension was temporary.

Steps to Fix VSS Snapshot Failure 0x80042308 by Resuming BitLocker

The primary solution is to resume BitLocker protection on the affected volume. Follow these steps in an elevated Command Prompt or PowerShell session.

1. Open Command Prompt as administrator
   Press the Windows key, type cmd, right-click Command Prompt in the results, and select Run as administrator. Click Yes in the User Account Control prompt.
2. Check BitLocker status on all volumes
   Type the following command and press Enter: manage-bde -status. Look for the volume that shows Protection Status: Suspended. Note the drive letter, for example C:.
3. Resume BitLocker protection
   Type the following command, replacing C: with the actual drive letter: manage-bde -protectors -enable C:. Press Enter. You should see a message that protection was enabled successfully.
4. Verify protection is active
   Run manage-bde -status again. Confirm that the volume now shows Protection Status: On.
5. Attempt the VSS snapshot again
   Open your backup software or use vssadmin create shadow /for=C: in an elevated prompt to test. The error 0x80042308 should no longer appear.

If Resuming BitLocker Fails

In some cases, the manage-bde -protectors -enable command may fail with a different error. This can happen if the protectors are missing or corrupted. To fix this, you can temporarily disable BitLocker entirely, then re-enable it.

1. Disable BitLocker on the volume
   Run: manage-bde -off C:. This starts decryption. Wait for it to complete by checking manage-bde -status until Conversion Status: Fully Decrypted appears.
2. Re-enable BitLocker
   Run: manage-bde -on C:. This starts encryption. After encryption completes, the VSS snapshot should work.

Other Causes and Fixes for VSS Snapshot Error 0x80042308

If resuming BitLocker does not resolve the issue, other factors may be at play. The following subsections cover additional causes and their specific fixes.

VSS Writer Is in a Failed State

A VSS writer may be stuck in a failed or inconsistent state unrelated to BitLocker. To check, run vssadmin list writers in an elevated prompt. Look for any writer with a State: Failed entry. Note the writer name and ID.

To reset a failed writer, restart the service it depends on. For example, if the System Writer is failing, restart the Volume Shadow Copy service and the Cryptographic Services:

1. Open Services
   Press Win + R, type services.msc, and press Enter.
2. Restart Volume Shadow Copy
   Find the service named Volume Shadow Copy. Right-click it and select Restart.
3. Restart Cryptographic Services
   Find the service named Cryptographic Services. Right-click it and select Restart.
4. Test the snapshot
   Run vssadmin create shadow /for=C: again. If the writer state changes to Stable, the issue is resolved.

Disk Space Is Low on the Volume

VSS requires a minimum of 300 MB of free space on the volume for the shadow copy storage area. If space is insufficient, the snapshot fails with error 0x80042308. Check free space in File Explorer. If it is below 1 GB, free up space by deleting temporary files or moving data to another drive.

Third-Party Backup Software Conflict

Some third-party backup tools install their own VSS requestors or writers that can conflict with the system. Temporarily uninstall the backup software, reboot, and test the snapshot again. If the error disappears, reinstall the software and check for updates from the vendor.

BitLocker Suspended vs VSS Snapshot: Key Behaviors

Item	BitLocker Suspended	BitLocker Active
Protection Status	Protection is temporarily paused	Full encryption with key protectors in use
VSS Writer Behavior	BitLocker writer fails snapshot due to inconsistent state	BitLocker writer supports snapshot creation
Error Code	0x80042308 (VSS_E_WRITERERROR_RETRYABLE)	No VSS error from BitLocker writer
Fix	Resume BitLocker with manage-bde -protectors -enable	No fix needed

This table shows that the suspended state is the primary trigger for the error. Once protection is resumed, the VSS writer operates normally.

After resuming BitLocker protection, you can create VSS snapshots without error 0x80042308. If you perform maintenance that requires suspending BitLocker again, remember to resume it immediately after the task completes. For persistent VSS writer failures, use the vssadmin list writers command to pinpoint the problematic writer and restart its associated services. As an advanced tip, you can automate BitLocker resumption after a reboot using a scheduled task that runs manage-bde -protectors -enable C: at system startup.