Windows Backup Error 0x8078012d: Fixes That Work

Windows backup error 0x8078012d stops the built-in Backup and Restore tool from completing a backup, usually because the destination drive is full, formatted incorrectly, or has a corrupted shadow copy. The fix is to free up space, reformat the target drive to NTFS, or delete problematic restore points, then retry the backup. Below are the specific causes and step-by-step solutions that resolve this error on current Windows versions.

What This Error Means

Error 0x8078012d appears during a Windows Backup (the legacy Backup and Restore tool in Windows 7/8/10) or File History setup. The code itself translates to “The backup destination is not available or does not have enough space.” Windows reports it when it cannot write the initial backup image or a subsequent incremental backup to the selected external drive, network share, or second internal disk.

Unlike some Windows errors that point to a single driver or service, this one is almost always tied to the destination volume’s state. The most common triggers are:

The destination drive is formatted as FAT32 or exFAT, which Windows Backup does not support for system images.
The drive is full, or the free space is less than the size of the data being backed up.
Previous backup files or shadow copies are corrupted, blocking new writes.
The drive has a read-only attribute or is connected via a USB hub that disconnects intermittently.
Antivirus software is locking the backup files mid-process.

Quick Fixes to Try First

Before reformatting anything, try these low-risk steps. They resolve a large percentage of 0x8078012d cases without losing existing data.

Restart the computer and reconnect the external drive. Use a direct USB port on the motherboard (not a front-panel hub) and a known-good cable.
Run Windows Backup again. Sometimes the error is a one-time glitch from a suspended sleep cycle.
Check the drive’s free space. Right-click the drive in File Explorer → Properties. You need at least as much free space as the total size of the files you are backing up, plus 10% overhead for the shadow copy system.
Disable third-party antivirus temporarily. Real-time scanners can lock the .vhd files Windows Backup creates. Re-enable it immediately after the backup finishes.
Run the backup again after disabling “Fast Startup.” Go to Control Panel → Power Options → Choose what the power buttons do, then uncheck Turn on fast startup. A stale hibernation file can confuse the backup engine.

Reformat the Destination Drive to NTFS

Windows Backup requires the destination to be NTFS. If your drive is FAT32 (common on older USB sticks) or exFAT (common on drives formatted for Mac or game consoles), the backup will fail with 0x8078012d. Reformatting erases everything on the drive, so first move any files you want to keep to another location.

Open File Explorer, right-click the destination drive, and select Format.
In the File system drop-down, choose NTFS.
Set Allocation unit size to Default and check Quick Format.
Click Start and wait for it to finish.
Reopen Windows Backup and choose this drive as the destination.

If the drive already shows NTFS, skip this step and move to the next section.

Delete Corrupted Backup Files and Shadow Copies

When a previous backup attempt was interrupted (power loss, cable pull, or forced shutdown), the partially written files can block new backups. Windows stores system image backups in a hidden folder called WindowsImageBackup at the root of the destination drive. Deleting this folder removes the old backup entirely.

Open File Explorer and go to the destination drive.
If you see a folder named WindowsImageBackup, right-click it and delete it. This removes all prior system images.
If you only need to clear shadow copies (not the whole backup), open Command Prompt as Administrator and type: vssadmin delete shadows /for=C: /all (replace C: with the drive letter of the source disk). This clears all restore points on that volume.
Restart the computer and start a fresh backup.

Be aware that deleting the WindowsImageBackup folder also deletes all previous system images, so you lose the ability to restore to an older point. If you have a second drive with a valid backup, keep it connected until the new one completes.

Check Disk Errors and File System Corruption

A failing or corrupted destination drive will produce 0x8078012d even when space and format are fine. Run a disk check on the destination drive to find and repair bad sectors or file system errors.

Open File Explorer, right-click the destination drive, and select Properties.
Go to the Tools tab and click Check under Error checking.
Choose Scan and repair drive. Windows will tell you if it found errors.
For a deeper check, open Command Prompt as Administrator and run: chkdsk X: /f /r (replace X: with the drive letter). This may take hours on large drives.

If chkdsk reports bad sectors that cannot be repaired, the drive is physically failing. Replace it before attempting another backup. Do not ignore this step – backing up to a dying drive gives you a false sense of security.

Use a Different Backup Method

If the error persists after all the above, the legacy Backup and Restore tool may be beyond repair (it is deprecated in Windows 10 and removed in Windows 11). Instead, use File History or the newer “Backup and Restore (Windows 7)” alternative, or simply copy your important files manually.

File History – Works for personal files in Libraries, Desktop, Contacts, and Favorites. It does not create a system image, but it is more reliable and runs continuously.
System Image via “Backup and Restore (Windows 7)” – Still available in Windows 10 and 11 under Control Panel → Backup and Restore (Windows 7). It uses the same engine, so if 0x8078012d persists, it will likely fail too.
Third-party imaging tools – Many free and paid tools create full disk images without the shadow copy restrictions. They also handle FAT32 destinations by splitting the image into files.

If you only need to protect documents and photos, File History is the most straightforward replacement. For a full system image, a third-party tool is often more forgiving about destination drive quirks.

Preventing This Error in the Future

Once you’ve resolved 0x8078012d, take these steps to avoid a repeat:

Use a dedicated external drive at least 1.5 times the size of your source data.
Keep the drive formatted as NTFS and never use it for other purposes that might change its format.
Eject the drive safely before disconnecting it, and never disconnect during a backup.
Run chkdsk on the destination drive every few months.
Keep at least 20% free space on the destination drive at all times.

Frequently Asked Questions

Can I ignore this error and keep using my computer? Yes, but you are not protected. The error means your backup is incomplete, so a system crash or drive failure could result in permanent data loss. Fix it before you need to restore.

Does this error mean my hard drive is dying? Not necessarily. It more often indicates a formatting or space issue. However, if chkdsk finds bad sectors, the drive is failing and should be replaced.

Will reformatting the destination drive delete my existing backup? Yes. Reformatting erases everything on that drive, including any prior backups. Move those files elsewhere if you need them.

Can I back up to a network drive with this error? Yes, but the network share must be NTFS and have enough free space. Also, the share must be accessible without a password prompt during the backup. Map the drive and test writing a file to it first.

Is there a way to fix this without losing my old backups? Often yes. Try deleting only the shadow copies (vssadmin command) or freeing up space. If that fails, you may need to delete the WindowsImageBackup folder, which removes all old backups.

Why does Windows Backup need NTFS when my external drive is exFAT? Windows Backup creates large system image files that require NTFS’s support for files larger than 4GB and its shadow copy integration. exFAT cannot handle these properly, so Windows refuses to use it.

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 →