VSS error 0x8004231f means Windows could not create a volume snapshot, usually because the Volume Shadow Copy service is stopped, the target drive lacks space, or the file system is unsupported. The fix is to restart the VSS services, check the event log for the exact failing component, and ensure the volume is NTFS with at least 1 GB free. Below is a full breakdown of what causes this error and how to resolve it.
What Is VSS and Why Does It Fail?
Volume Shadow Copy Service (VSS) is a Windows framework that coordinates snapshot creation for backups, System Restore, and tools like Windows Backup or third-party software. When an application requests a snapshot, VSS asks all registered writers (like SQL Server or Exchange) to freeze their data, then the storage provider creates the shadow copy. Error 0x8004231f is the generic VSS_E_VOLUME_NOT_SUPPORTED code, meaning the volume does not meet the requirements for snapshotting.
The most common trigger is a non-NTFS file system (FAT32, exFAT, ReFS) or a drive that is not a basic disk. However, the error can also appear when the VSS service is disabled, the system drive is full, or a third-party antivirus locks the volume. In practice, the error message rarely tells you which condition failed, so you must check the Windows Event Log for the underlying cause.
Step-by-Step Fix for Error 0x8004231f
- Restart VSS-related services. Open Command Prompt as Administrator and run:
net stop vss && net stop swprv && net start swprv && net start vss. This resets the Volume Shadow Copy service and the Microsoft Software Shadow Copy Provider. - Check the file system. Open
cmdand runfsutil fsinfo volumeinfo C:(replace C: with the affected drive). Look for “NTFS” in the output. If it says FAT32 or exFAT, you must convert the drive to NTFS (backup data first) or use a different backup target. - Verify free space. VSS needs at least 1 GB free on the system drive and on the target volume. For large databases, you may need several GB. Right-click the drive in File Explorer and check properties.
- Check the Event Log. Press Win+R, type
eventvwr.msc, go to Windows Logs > Application, and look for events with source “VSS” or “VolSnap” around the time of the error. The details often say the exact reason, such as “insufficient storage” or “a writer has timed out.” - Run a disk check. In an elevated Command Prompt, run
chkdsk /f /r C:(replace C:). This fixes file system errors that can block snapshot creation. - Disable third-party antivirus temporarily. Some security software locks volume handles. Pause protection and retry the backup. If it works, add an exception for the backup process.
Common Causes and How to Identify Them
- Non-NTFS volumes: VSS only supports NTFS (and ReFS in some cases). If you try to snapshot a USB drive formatted as exFAT, you get 0x8004231f.
- System drive full: VSS uses the system drive for the shadow copy storage area. If it has less than 1 GB free, the snapshot fails.
- VSS writers are stuck: Applications like SQL Server or Exchange can hang during the freeze phase. Check the Event Log for VSS writer errors (e.g., “writer timeout”).
- Shadow storage limits: If you have a small shadow storage quota set, older snapshots may be deleted, but new ones can still fail if the storage is full.
- Disk is a dynamic disk: VSS generally works on basic disks. Dynamic disks can cause issues, especially with third-party backup tools.
How to Fix VSS Writer Errors
If the Event Log mentions a specific writer (like “Exchange Writer” or “SQL Server Writer”), the problem is that the application is not responding to VSS requests. First, restart the application service. For example, for SQL Server, restart the SQL Server service in Services.msc. If that fails, run vssadmin list writers in an elevated command prompt to see the state of each writer. A writer with “Failed” or “Unknown” state needs attention. You can often fix it by restarting the service that hosts the writer, or by reinstalling the application’s VSS writer component (for example, by running the application’s repair installation).
When to Use a Third-Party Backup Tool
If you consistently get 0x8004231f even after trying the steps above, consider using a backup tool that does not rely on VSS. Some tools use a different snapshot method (like a block-level copy while the system is offline) or they can run in a pre-OS environment. However, for most users, the built-in Windows Backup (which uses VSS) can be fixed by ensuring the system drive has enough free space and that the target drive is NTFS. If you are backing up a server with a large database, you may need to increase the shadow storage size using vssadmin add shadowstorage /for=C: /on=C: /maxsize=10GB.
Preventing Future Snapshot Failures
- Keep at least 10% of the system drive free, or a minimum of 5 GB for typical desktops.
- Regularly run
chkdskto avoid file system corruption. - Set a reasonable shadow storage limit (e.g., 5-10 GB) so VSS does not run out of space.
- Update your backup software and ensure it is compatible with your Windows version.
- If you use a NAS, make sure it supports SMB 3.0 and that the network is stable.
Frequently Asked Questions
Does this error mean my hard drive is failing?
Not necessarily. The error is about the snapshot process, not physical disk health. However, if you also see disk errors in the Event Log, run a SMART check (e.g., with wmic diskdrive get status) to verify the drive is healthy.
Can I fix this without restarting my computer?
Yes, the service restart and most of the steps above do not require a reboot. Only the chkdsk /f may require a restart to schedule the check on the system drive.
Why does this happen on a USB drive?
USB drives are often formatted as exFAT or FAT32, which VSS does not support. Also, some USB drives are not “fixed” disks but “removable” disks, which VSS cannot snapshot. Reformat the drive to NTFS and set its policy to “Better performance” in Device Manager to make it a fixed disk.
Is there a way to create a snapshot without VSS?
Yes, some tools use a different mechanism, such as a hardware snapshot from a RAID controller, or a file-level backup that does not require a volume snapshot. However, for system state backups, VSS is the standard method on Windows.
Will this error affect my system restore points?
Yes, System Restore uses VSS. If you get this error, new restore points may not be created. Fixing the underlying issue (usually free space or file system) will restore normal operation.