sodcalculator

10 Tech How-To

Windows 10 System Image Backup Error 0x807800a1 0x800423f3

Guide 10-48402 · Updated · Step by step

Windows 10 system image backup error 0x807800a1 0x800423f3 occurs when the Volume Shadow Copy (VSS) service fails to create a snapshot, often due to insufficient disk space, incompatible storage drivers, or a corrupted VSS state. The fix typically involves freeing up space on the destination drive, checking the shadow copy storage, and running the VSS troubleshooting commands below.

What These Error Codes Mean

Both codes point to a VSS failure during the backup process. 0x807800a1 is a generic VSS error, while 0x800423f3 specifically means the shadow copy could not be created because the volume is not in a valid state. In practice, this usually translates to:

  • The destination drive (where the backup is saved) is formatted as FAT32 or exFAT, which does not support shadow copies.
  • The destination drive is full or has a file size limit (FAT32 caps files at 4 GB).
  • The system drive has System Protection disabled, so no snapshot can be taken.
  • Third-party backup software or disk utilities are interfering with VSS.
  • The VSS service or its dependencies are stopped or corrupted.

Prerequisites for a Successful System Image

Before running the backup, confirm these conditions:

  • The destination drive must be NTFS. If it is FAT32, convert it or use a different drive.
  • The destination drive must have at least as much free space as the used space on your system drive (plus a little extra). For example, if Windows uses 200 GB, you need about 220 GB free.
  • System Protection must be enabled on the drive you are backing up. Go to Control Panel > System > System Protection, select the drive, and click Configure.
  • You need administrator privileges.

Step-by-Step Fix

  1. Free up space on the destination drive. Delete unnecessary files or use a larger external drive. Remember that the backup is a full image of your system drive, not just your user files.
  2. Check the file system. Right-click the destination drive in File Explorer, select Properties, and verify it says NTFS. If it is FAT32, you can convert it without losing data using the command prompt: convert X: /fs:ntfs (replace X with the drive letter).
  3. Restart the VSS services. Open Command Prompt as administrator and run:
    net stop vss
    net stop swprv
    net start swprv
    net start vss
  4. Run the System File Checker and DISM. In the same Command Prompt, run:
    sfc /scannow

    Then:

    DISM /Online /Cleanup-Image /RestoreHealth

    Restart your PC after both complete.

  5. Increase the shadow copy storage space. In Command Prompt (admin), type:
    vssadmin list shadowstorage

    If the “Used” value is close to the “Allocated” value, delete old shadow copies with:

    vssadmin delete shadows /for=C: /oldest

    Then set a larger storage limit (e.g., 10 GB):

    vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB
  6. Disable third-party backup tools. Temporarily uninstall or disable any antivirus with backup features, or tools like Acronis, Macrium, or even OneDrive’s backup. They may hold VSS locks.
  7. Try a different destination. Some USB drives or network locations have issues with VSS. Use an internal secondary drive or a different USB port.

Why the Error Happens on External Drives

External drives are the most common cause. Many are pre-formatted as exFAT for compatibility with Macs and game consoles. Windows system image backup requires NTFS because VSS snapshots are stored as hidden files that FAT/exFAT cannot handle. Additionally, if the external drive is connected via USB 2.0, the backup may time out, causing the VSS to fail. Use USB 3.0 or eSATA if possible.

Alternative: Use the Windows 7 Backup Tool

Windows 10 still includes the legacy “Backup and Restore (Windows 7)” tool, which is more reliable for system images than the newer “File History” or “Backup” settings. To access it, go to Control Panel > Backup and Restore (Windows 7) and click Create a system image. This tool uses the same VSS engine, but it often handles errors more gracefully and gives clearer messages. If the error persists, you can also try using wbadmin start backup from an elevated Command Prompt, which gives more detailed logs.

Frequently Asked Questions

Will this error damage my existing backups?

No. The error only prevents a new backup from being created. Your existing system image files remain intact. You can still restore from them if needed.

Can I use a network drive for the system image?

Yes, but the network share must be NTFS and you must have write permissions. Also, the backup may fail if the network connection is unstable. It is safer to use a locally attached drive.

Why does the backup stop at 99% and then fail?

This is typical of VSS timeouts. The backup is about to finalize the image, but the snapshot expires. Increasing the shadow storage size and disabling any power-saving settings on the USB ports can help.

Do I need to reinstall Windows to fix this?

No. This is a software-level issue. The steps above resolve the vast majority of cases. Reinstalling Windows would be a last resort and would likely not help if the root cause is a faulty driver or external drive.

Is there a way to check the VSS event log for more details?

Yes. Open Event Viewer, go to Windows Logs > System, and filter by source “VolSnap” or “VSS”. Look for events with ID 13, 14, or 8229. These will tell you which volume failed and why.

Can I create a system image without VSS?

No. Windows built-in backup relies entirely on VSS. If you cannot fix VSS, you can use third-party imaging tools like Macrium Reflect Free or Clonezilla, which do not use VSS and often work even when Windows backup fails.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →