Fix Windows 10 Backup Internal Error: 8 Steps

The “Backup application could not start due to an internal error” message in Windows 10 usually appears when the backup service is not running, the backup catalog is corrupted, or a system file is damaged. The most reliable fix is to restart the Windows Backup service, then run the System File Checker (SFC) and DISM tools to repair system files, and finally delete the corrupted backup catalog if the error persists. Below is a step-by-step guide covering these and other proven methods.

What Causes the Backup Internal Error in Windows 10

Windows 10’s built-in backup tool (formerly “File History” and also used by “Backup and Restore (Windows 7)”) depends on several background services and a stored catalog of backup files. The error typically appears for one of three reasons:

• Stopped or disabled services: The “Windows Backup” service (wbengine) or the “Volume Shadow Copy” service (VSS) may be stopped, disabled, or set to manual when they need to be running.
• Corrupted backup catalog: Windows keeps a database of your backup files. If this catalog is damaged (often after a crash or interrupted backup), the app cannot start.
• Damaged system files: Corrupted Windows system files, often from a recent update or disk error, can prevent the backup application from launching.

Less commonly, the error is caused by a conflict with third-party backup software, a full system drive, or a failing hard disk. The fixes below address the most frequent causes first.

Fix 1: Restart the Windows Backup Services

The quickest fix is to ensure the required services are running. Press Win + R, type services.msc, and press Enter. In the list, find these three services:

• Windows Backup (or “Block Level Backup Engine Service”)
• Volume Shadow Copy
• Microsoft Software Shadow Copy Provider

For each one, right-click and select Restart (if running) or Start (if stopped). Then double-click each service, set the Startup type to Automatic (for Windows Backup and Volume Shadow Copy) and click OK. After restarting all three, try opening the backup app again.

Fix 2: Run SFC and DISM to Repair System Files

If services are fine, corrupt system files are the next likely culprit. Open Command Prompt as administrator (search “cmd”, right-click, select “Run as administrator”). Run these commands in order:

1. Type sfc /scannow and press Enter. This scans and repairs protected system files. It can take 10-15 minutes.
2. After it finishes, run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the Windows image that SFC relies on. It may take longer.
3. Restart your computer and try the backup app again.

If SFC reports that it found corrupted files but could not fix them, running DISM first and then repeating SFC usually resolves it.

Fix 3: Delete the Corrupted Backup Catalog

If the error persists, the backup catalog itself may be damaged. The catalog is stored in a hidden folder. You will need to show hidden files first: in File Explorer, go to the View tab and check Hidden items. Then navigate to:

C:\ProgramData\Microsoft\Windows\Backup

Inside this folder, look for a subfolder named Catalog. Rename it to Catalog_old (do not delete it yet). Then try starting the backup app. Windows will create a new catalog. If the app works, you can delete the old folder after confirming your backups are intact. Note that this may remove your ability to restore from older backups, so only do this if you have a current backup elsewhere or accept the risk.

Fix 4: Check for Conflicting Third-Party Software

Some third-party backup tools (like Acronis, Macrium, or older versions of Norton) install their own volume shadow copy drivers that conflict with Windows’ built-in backup. If you have such software installed, temporarily uninstall it or disable its backup service, then try the Windows backup app. If the error disappears, you have found the conflict. You can then either keep the third-party software and use it instead of Windows backup, or reinstall it after updating to the latest version.

Fix 5: Ensure the Backup Drive Has Enough Space

A full destination drive can cause the backup app to fail with a generic internal error. Check the drive you are backing up to (external drive or network location). Windows needs at least 10-15% free space on the destination to create the catalog and temporary files. Also check your main system drive (C:) — if it is nearly full, the backup service may not be able to write temporary files. Delete unnecessary files or move them elsewhere, then retry.

Fix 6: Use the Windows Backup Troubleshooter

Windows 10 includes a built-in troubleshooter for backup. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters. Scroll down and select Backup and Restore (or “Windows Backup”), then click Run the troubleshooter. This tool automatically checks for common issues with backup services, permissions, and disk settings, and applies fixes where possible. It is worth trying before more drastic measures.

Fix 7: Create a New Backup Job or Use File History

If none of the above works, the existing backup configuration may be beyond repair. You can create a fresh backup job:

1. Open Control Panel > Backup and Restore (Windows 7).
2. Click Turn off backup (if one exists), then click Set up backup again.
3. Choose a destination and follow the prompts.

Alternatively, switch to File History (Settings > Update & Security > Backup). File History is a separate feature that backs up files in your Libraries, Desktop, and Contacts folders. It uses different underlying mechanisms and often works when the older backup tool fails. If File History also fails with the same error, the problem is more likely system-wide, and you should consider the final fix below.

Fix 8: Perform a Repair Upgrade or Reset

If every fix fails, the Windows installation itself may have deeper corruption. A repair upgrade (also called an in-place upgrade) reinstalls Windows while keeping your files, settings, and installed apps. To do this, download the Windows 10 Media Creation Tool from Microsoft’s official website, run it, and choose Upgrade this PC now. This takes about an hour and is less drastic than a full reset. After the upgrade, check if the backup app works. If it still fails, a full reset (Settings > Update & Security > Recovery > Reset this PC) is the last resort, but back up your important files manually to an external drive first.

Frequently Asked Questions

Will deleting the backup catalog erase my backups?
No. The catalog is just an index of your backups. Deleting it (or renaming it) does not delete the actual backup files. However, Windows may not be able to restore from older backups until it rebuilds the catalog, which it does automatically when you start a new backup. It is safest to rename the folder rather than delete it.

Why does the error appear only after a Windows update?
Windows updates can change service startup types, reset permissions, or introduce incompatible drivers. The Volume Shadow Copy service is particularly sensitive to updates. Re-running the service restart steps (Fix 1) and the SFC/DISM commands (Fix 2) usually resolves update-related corruption.

Can I use a third-party backup tool instead?
Yes. If the built-in backup app continues to fail, many reliable third-party tools are available. They do not rely on the Windows Backup service and often have their own drivers. Just ensure you uninstall or disable the built-in backup’s scheduled tasks to avoid conflicts. Always choose a reputable tool and test a restore before relying on it.

Does this error affect File History as well?
Sometimes, but not always. File History uses a different service (File History Service) and a different file format. If the error appears in both, the cause is likely system file corruption or a full disk. If only the “Backup and Restore” app fails, the issue is specific to that service or catalog.

Is it safe to set the Volume Shadow Copy service to Automatic?
Yes. Microsoft sets it to Manual by default, but it starts on demand. Setting it to Automatic ensures it is always ready and can prevent this error. It does consume a small amount of memory, but the benefit outweighs the cost for most users. If you never use System Restore or backup, you can leave it on Manual, but then you must start it manually when the error occurs.

What if the error says “insufficient storage” instead?
That is a different message, but it often appears alongside this one. It means the destination drive is out of space. Free up space on the backup drive, or choose a larger destination. The backup app needs room for both the data and the catalog, which can be several gigabytes.

Related

• How to Turn an Android Phone Into a Wi-Fi Extender
• Apple Watch Not Getting Notifications? Fix It
• Router Basics: How It Moves Data Between Networks