This guide walks you through fixing the Windows 11 system image backup error 0x80780038, which typically appears when you try to create a system image using the Backup and Restore (Windows 7) tool. The error often points to a problem with the destination drive, system files, or the backup service. Below are clear, step-by-step fixes that address the most common causes, from simple restarts to deeper system checks.
What You’ll Need
- Administrator account access
- An external drive or network location with enough free space (at least the size of your system drive)
- Optional: a USB recovery drive or Windows installation media
Step-by-Step
- Restart your PC and try again. Sometimes the error is temporary. Restart Windows normally, then attempt the system image backup again. If it succeeds, no further steps are needed.
- Check the destination drive. Ensure the drive you’re backing up to is connected, has enough free space, and is formatted as NTFS (FAT32 won’t work for system images). If using a network location, confirm the path is correct and you have write permissions.
- Run the System File Checker (SFC) and DISM. Corrupted system files can trigger this error. Open Command Prompt as administrator, then run these commands one by one, pressing Enter after each:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Wait for each to finish (this can take 15-30 minutes). Restart and try the backup again. - Disable and re-enable the Volume Shadow Copy service. The backup relies on this service. Press Win + R, type
services.msc, and press Enter. Scroll to Volume Shadow Copy, right-click it, and select Restart. Also check that Windows Backup service is set to Manual and is running. - Free up space on the system drive. The system image needs temporary space on your C: drive. Use Disk Cleanup to remove temporary files, or move large files to another drive. Ensure you have at least 10-15% free space on C:.
- Run Check Disk on the source and destination drives. Open Command Prompt as administrator and run
chkdsk C: /f /r(for your system drive). You may need to restart to let it run. Do the same for the destination drive (e.g.,chkdsk D: /f). This repairs file system errors that can block backup. - Use a different backup method. If the error persists, try using File History or the older “Backup and Restore (Windows 7)” with a different destination drive. Alternatively, use third-party imaging software that doesn’t rely on VSS.
Common Mistakes
- Ignoring drive health. A failing drive can cause this error. Check the SMART status of both source and destination drives using tools like CrystalDiskInfo (free) or the built-in
wmic diskdrive get statuscommand. - Using a drive formatted as exFAT or FAT32. System images require NTFS. Reformat the destination drive (this erases data, so back up first).
- Skipping the DISM step. SFC alone often doesn’t fix underlying Windows image corruption. Always run DISM after SFC.
- Not enough free space on C: drive. Even if the destination has space, Windows needs temporary space on the system drive. Clear junk files before retrying.
- Running the backup while other heavy tasks are active. Close unnecessary programs, especially those that write to disk, to avoid conflicts with the backup process.
Tips
- Create a system repair disc or USB. This gives you a recovery option if the backup fails and your system becomes unbootable.
- Schedule backups during idle time. Use Task Scheduler to run the backup when you’re not using the PC, reducing the chance of interference.
- Keep your Windows updated. Some backup errors are fixed in cumulative updates. Check Settings > Windows Update and install all pending updates.
- Use a dedicated backup drive. Avoid backing up to the same drive that contains your system files (like a second partition on C:).
- Verify the backup after completion. In Backup and Restore, click “Restore personal files” to test that the image is readable.
Troubleshooting
If the error persists after all steps, try these advanced fixes:
- Reset the Windows Backup components. Open Command Prompt as administrator and run these commands in order:
net stop wbengine,net start wbengine. This restarts the backup engine. - Check Event Viewer for more details. Press Win + X and select Event Viewer. Go to Windows Logs > Application and look for errors with source “Backup” or “VSS” around the time of the failure. The details may point to a specific VSS writer that’s failing.
- Run a VSS diagnostic. Use the command
vssadmin list writersin Command Prompt (admin). Look for any writer with “Failed” or “Stable” status. If one shows “Failed”, note its name and search for a fix or disable that specific service (if safe). - Boot into Safe Mode and try the backup. Safe Mode loads minimal drivers, which can isolate third-party software conflicts. Restart your PC, hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart, and press 4 or F4 for Safe Mode.
- Use a Windows installation media to run Startup Repair. If you suspect system file corruption that SFC can’t fix, boot from a USB/DVD with Windows 11 setup, choose “Repair your computer”, then Troubleshoot > Advanced options > Startup Repair.
- Last resort: reset Windows. If nothing works, you can reset Windows 11 (Settings > System > Recovery > Reset PC) while keeping your files. This reinstalls Windows and often resolves persistent backup errors, but ensure you have other backups of important data.
Frequently Asked Questions
Why does error 0x80780038 occur?
It usually means Windows cannot create the system image due to a problem with the Volume Shadow Copy service, corrupted system files, or an issue with the destination drive (like insufficient space or wrong format).
Can I back up to an external USB drive?
Yes, but it must be formatted as NTFS and have enough free space. Also, make sure it’s connected directly to a USB port (not a hub) and is recognized by Windows before starting the backup.
How long does a system image backup take?
It depends on the size of your system drive and the speed of the destination drive. A typical 200 GB system drive can take 30 minutes to 2 hours. Don’t interrupt it.
Will this error damage my files?
No, the error only prevents the backup from being created. Your existing files are not affected. However, you should still fix the issue to ensure you have a backup for disaster recovery.
Can I use a network drive for the system image?
Yes, Windows supports backing up to a network location. Ensure the shared folder is accessible, you have write permissions, and the network connection is stable. Wired connections are more reliable.
Is there a way to bypass this error?
No safe bypass exists. Trying to force the backup by disabling services can lead to an incomplete or corrupt image. Follow the steps above to fix the root cause instead.
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
- Fix Slow Internet Lag on Samsung Galaxy Note
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step