How to Fix Computer Backups That Keep Failing
Published 2026-10-16 · Marion Remote Fix
Your computer backup keeps failing. You set it up expecting automatic protection for your files, but instead you get error messages, incomplete backups, or the backup stops partway through. Backup failures are dangerous because most people only discover the problem when they actually need to restore files — and by then it is too late. The causes range from simple disk space issues to corrupted backup databases, permission errors, and drive hardware problems. Identifying why the backup fails and fixing it now means your files are actually protected when something goes wrong.
Check the error message
The error message from your backup tool tells you where to start:
- Not enough space: The backup destination (external drive, network location, or cloud storage) is full. This is the most common backup failure. The backup needs enough free space to store the new backup data plus working space for temporary files during the backup process
- The drive is not available or cannot be found: The backup destination is disconnected, turned off, or the network path has changed. External USB drives must be connected during the scheduled backup time. Network drives must be accessible from the computer
- Access denied or permission error: The backup software does not have permission to read the source files or write to the destination. This happens after Windows updates change security policies, when backing up files owned by other user accounts, or when network share permissions have changed
- The backup is corrupted: Previous backup data on the destination drive is damaged, and the backup software cannot append to or verify the existing backup chain. This requires clearing the old backup and starting fresh
- VSS (Volume Shadow Copy Service) error: Windows backup tools use VSS to create point-in-time snapshots of files that are in use. If the VSS service fails, the backup cannot capture open files and reports an error. VSS failures are common and have multiple possible causes
Fix Windows File History
File History is the built-in backup feature in Windows 10 and 11 that continuously backs up files in your user folders:
- File History says the drive is full: Open Settings, System, Storage, and check the free space on your backup drive. File History keeps older versions of files indefinitely by default, filling the drive over time. Go to Settings, Update and Security (or System), Backup, More Options, and under Keep My Backups, change from Forever to a shorter retention period — 3 months or 6 months. Then scroll down and click Clean Up Versions to remove old backups and free space
- File History stopped working: Turn File History off and back on. Open Settings, Update and Security, Backup. Toggle off Back Up Using File History, wait a few seconds, then toggle it back on and select your backup drive. This resets the connection to the backup drive
- File History shows errors in Event Viewer: Open Event Viewer, Applications and Services Logs, Microsoft, Windows, FileHistory-Engine. Look for error events that describe the specific failure. Common issues include the backup drive being formatted as FAT32 (File History requires NTFS), corrupted configuration files, or files that are locked by other programs
- Reset File History: If File History is consistently failing, delete its configuration and start over. Navigate to the File History folder on your backup drive (typically labeled FileHistory in the root of the drive), delete or rename the Configuration folder, then set up File History again from Settings. This loses the backup history but creates a clean starting point
Fix Windows Backup (Windows 7 style)
The legacy Windows Backup and Restore tool (available in Control Panel on Windows 10 and 11) creates system images and file backups:
- Backup fails with VSS errors: Open Services (press Windows+R, type services.msc). Find Volume Shadow Copy, right-click, and select Restart. Also restart the Microsoft Software Shadow Copy Provider service. If these services are set to Disabled, change them to Manual or Automatic
- Backup fails on specific files: Large files, files with very long paths (over 260 characters), encrypted files, or files in use by other programs can cause backup failures. Check the backup log for the specific files causing errors. Move or rename files with excessively long paths. Close programs that lock files during the backup window
- System image backup fails: System image backups require contiguous free space on the destination drive. If the drive is fragmented or nearly full, the system image cannot be written. Use a freshly formatted external drive for system images. The drive must be NTFS formatted and have enough space for the entire system partition
Fix VSS (Volume Shadow Copy Service)
VSS errors affect all Windows backup tools and many third-party backup programs:
- Restart VSS services: Open Command Prompt as administrator. Run the following commands one at a time: net stop vss then net start vss. Also restart related services: net stop swprv then net start swprv
- Re-register VSS components: If restarting the services does not help, re-register the VSS DLL files. Open Command Prompt as administrator and run: cd /d %windir%\system32 followed by net stop vss then regsvr32 ole32.dll then regsvr32 vss_ps.dll then vssvc /register then net start vss
- Check disk space for shadow copies: VSS needs free space on the source drive (the drive being backed up, usually C:) to create shadow copies. If the C: drive is nearly full (less than 10 percent free space), VSS cannot create snapshots. Free up space on the system drive
- Third-party VSS conflicts: Some antivirus software, database applications, and virtual machine software install their own VSS writers that conflict with Windows backup. Open Command Prompt as administrator and run vssadmin list writers. Look for writers with a state of Failed or Not Responding. If a third-party writer is failing, updating or reinstalling that software usually fixes its VSS writer
Network backup failures
- Credentials changed: If you back up to a network share (NAS device, another computer, or server), the backup fails when the network share password changes. Re-enter the credentials in your backup software. For Windows Backup, remove the network location and re-add it with the current credentials
- Network interruptions: Backup to a network location fails if the connection drops during the transfer. This is common on Wi-Fi connections. For large backups, use a wired Ethernet connection to the network. If the backup software supports it, enable resume on failure so the backup picks up where it left off rather than starting over
- SMB version mismatch: Older NAS devices use SMB version 1, which is disabled by default in Windows 10 and 11 for security reasons. If your backup to a NAS fails with a connection error, check whether the NAS supports SMB 2 or 3. If not, you can enable SMB 1 in Windows Features (Control Panel, Programs, Turn Windows Features On or Off), but upgrading the NAS firmware or replacing an old NAS is the better long-term solution
Cloud backup failures
- Storage quota reached: Cloud backup services like OneDrive, Google Drive, or Backblaze have storage limits. When the quota is reached, new backups fail. Check your cloud storage usage and either free up space by deleting old files or upgrade your storage plan
- Large files or file types blocked: Some cloud services have maximum file size limits or block certain file types. OneDrive has a 250GB per-file limit. Check your cloud service documentation for restrictions that might affect your backup
- Upload bandwidth: If your internet upload speed is slow, large backups may time out before completing. Schedule backups for overnight when bandwidth demand is lowest. Some backup software lets you throttle the upload speed to prevent the backup from saturating your connection during work hours
Verify your backups actually work
- A backup that completes without errors is not necessarily a good backup. Periodically test your backups by restoring a few files to a temporary location and verifying they open correctly. Backup corruption can go undetected for months if you never test restores
- For system image backups, verify the image by mounting it or booting from recovery media and checking that the restore option sees your backup. An untested system image that turns out to be corrupted when you need it is worse than no backup because you thought you were protected when you were not
Backup troubleshooting in Marion
If your computer backups keep failing and you cannot identify the cause, Marion Remote Fix can remotely diagnose the backup errors, fix VSS issues, resolve permission problems, verify your backup is working correctly, and set up a reliable backup strategy so your files stay protected.