Fix File History Error 80070005: We Can't Copy Files to Your Drive

File History in Windows 10 Not Working!

When File History Windows 10 is not working, it means your automatic backups have ground to a halt, leaving your data vulnerable. But don't worry. You will learn why you get the error message “We can’t copy files to your File History drive. Failed to initiate user data backup (error 80070005)” while using File History to take a backup. This guide will walk you through it, step by step, from simple fixes to more advanced solutions.

Why Does File History Show Error 80070005?

At its core, the file history error 80070005 is an access denied error. This isn't usually a hardware failure; it's a permissions and credentials snafu. The service responsible for the backup doesn't have the proper rights to write to the destination folder, leading to that frustrating "failed to initiate user data backup error80070005" message.

• A common trigger is simply disconnecting and reconnecting your backup drive.
• Sometimes, Windows gets confused, and the permission structure doesn't re-establish correctly.
• Other times, it can be a corrupted user profile, where the specific identity the File History service uses gets mangled.
• Group Policy settings in a workplace environment can also be the invisible hand, restricting access in a way that breaks the backup.
• Even a Windows update, designed to improve things, can occasionally reset service permissions, leaving File History out in the cold.

How to Fix File History Error 80070005?

Way 1. Verify Drive Connectivity and Permissions

First things first, is the drive even there? Physically check the cable connections for your external drive. Try a different USB port, preferably one directly on your computer, not a hub.

If it's a network drive, can you still browse to it in File Explorer?

Once connectivity is confirmed, let's talk permissions.

1. Right-click on the backup destination folder (usually on your external drive), select 'Properties', and navigate to the 'Security' tab.

2. Check that the 'SYSTEM' account and your user account have 'Full Control'. If not, that's your problem.

This is the most common reason for the "failed to initiate user data backup error 80070005".

Way 2. Ensure Sufficient Storage Space

You'd be surprised how often a full drive is the culprit.

Open File Explorer, check your backup drive, and ensure it has ample free space—at least 10-15% more than the amount of data you're trying to back up.

File History requires space to create new versions of your files. A drive bursting at the seams can absolutely cause File History to throw its hands up and stop working, mimicking the symptoms of a permissions error.

Way 3. Configure File History Service Settings

The backbone of the entire operation is the "File History Service" itself. If this service is running with incorrect permissions, nothing will work.

1. To check this, press Win + R, type services.msc, and press Enter.

2. Scroll down to find "File History Service".

3. Right-click it, select 'Properties', and go to the 'Log On' tab.

4. This is critical. It should be set to "Local System account", and the checkbox for "Allow service to interact with desktop" should be selected.

5. If it's not, change it, click 'Apply', and then restart the service from the 'General' tab.

Way 4. Reconfigure Your Backup Target

One of the most effective nuclear options is to reconfigure your backup target completely.

1. In File History settings, turn File History off for the current drive.

2. Then, using File Explorer, you can either rename or delete the existing "FileHistory" folder on your backup drive. This forces Windows to view it as a brand-new destination.

3. Then, go back into settings, turn File History back on, and select the drive again.

4. Windows will set up a fresh new folder with clean permissions.

This often clears the "Failed to initiate user data backup error 80070005" by starting the relationship from scratch.

Way 5. Runa System File Check

A final, broader diagnostic step is to check for overall system file corruption. The file history error 80070005 can sometimes be a symptom of a wider system malaise. To do this:

1. Right-click the Start button, select "Command Prompt (Admin)" or "Terminal (Admin)".

2. Type the command sfc /scannow.

This will scan all protected system files and replace corrupted versions with a cached copy. It’s a long shot for this specific error, but it’s a good health check for your OS and can prevent other mysterious issues from popping up down the line.

Way 6. Fix a Corrupted File History Configuration

If the problem persists deeper within Windows, you may need to clear the local configuration cache.

This involves stopping the File History Service, then navigating to C:\Users\[YourUsername]\AppData\Local\Microsoft\Windows\FileHistory\Configuration and temporarily moving the config files there to a different folder.

When you restart the service and File History, it will rebuild these files from scratch.

It’s a more technical step, but for a stubborn case where "File History in Windows 10 is not working" is your constant reality, it can be the magic bullet.

Way 7. Edit Group Policy and Registry Permissions

For users on professional versions of Windows, Group Policy might be the lock on the door.

1. Press Win + R, type gpedit.msc, and navigate to Computer Configuration > Administrative Templates > Windows Components > File History.

2. Ensure that "Turn off File History" is set to "Not Configured" or "Disabled".

For all users, or if Group Policy isn't available, the Registry Editor is the next stop.

A key permission fix involves granting the "SYSTEM" account full control over the File History configuration database. This is an advanced step, so it's wise to back up your registry first. Navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fhsvc and ensuring the "SYSTEM" account has full control can often unstick the most stubborn file history error 80070005.

FAQs About File History Error 80070005

Q: What does the File History error 80070005 actually mean?

A: It's an "Access Denied" error. The File History service doesn't have permission to write to your backup drive.

Q: I've checked permissions, and they seem correct. What's a hidden cause for this error?

A: Check the "File History Service" itself. It must run as the "Local System Account".Antivirus software can also block it during a scan.

Q: Can a Windows update cause the "failed to initiate user data backup error 80070005"?

A: Yes. Updates can reset service permissions. If backups break after an update, it's a prime suspect.

Q: Is it safe to edit the registry to fix this File History error?

A: It's risky. Always back up the registry first. Try service configuration and Group Policy fixes before editing the registry.

Q: Why does File History keep failing even after I fix error 80070005?

A: The cause may have changed. Check for constantly locked files (like an Outlook PST file) or network timeouts. View the Event Viewer logs for the latest specific error.

Q: Should I just switch to a different backup tool?

A: If you've tried everything and it still fails, switching is a pragmatic choice. Your data's safety is the goal. Consider the "Backup and Restore (Windows 7)" tool or a third-party application.

Recover Lost Files with MyRecover

If File History is still not working, you can try a professional data recovery software like MyRecover to help you out of the trouble. MyRecover is designed to recover files from any complex situation and ensure your data security.

With MyRecover, enjoy the following strengths:

Recovery Without a Backup. File History requires a pre-existing backup. MyRecover scans your drive directly to find and restore lost files, even if you never set up a backup solution.

Deep, Advanced Scanning. It doesn't just look at recent files. MyRecover uses advanced algorithms to deeply scan your storage device, recovering data from formatted, corrupted, or inaccessible partitions where File History has no reach.

Cost-Effective Solution. Investing in a new backup drive and spending hours reconfiguring File History has a cost. MyRecover provides a one-time solution to get your critical files back immediately, saving you time and money.

User-Friendly & Safe. MyRecover offers a simple, guided interface. It's a read-only tool, meaning it won't write to or further damage the drive you are recovering from.

Preview Before Recovery. Before you restore anything, you can preview found files (like photos, documents, and videos) to ensure they are the correct, uncorrupted versions you need.

So, how to recover deleted files on your Windows computer with MyRecover? Check the simple guide:

1. Please download and install MyRecover on your computer (not on the drive you’re trying to recover files from).

2. Launch MyRecover, choose Deleted Files Recovery, choose the drive where your deleted files are located, and hit Scan.

3. Wait for the scan to complete and hit OK.

4. Preview and select the files you need, and hit Recover. Then choose a safe location to save.

5. Check the recovered files on your destination.

Notes:✎...

By default, MyRecover lists files by file type, so you can find your missing files quickly. Besides, you can use file name, file path, and file size to filter them.

You can recover unlimited files at once instead of recovering them one by one.

For administrators, you can recover files from unlimited computers within a company after upgrading to MyRecover Technician.

 

Write in the End

If you encounter the File History error 80070005, you can try the above solutions to fix it. Besides, MyRecover is another option for you to recover files quickly once File History is not working after trying all the above solutions.

Please ensure you have backed up important files first, then you can recover them quickly if something bad happens to your files. Or you have to recover files with MyRecover. Moreover, you can recover files from a crashed computer, recover files from a corrupted SD Card, etc.