error 0x80070002 in file history when selecting a new device

Hi alocksley

Thank you for your reply.

Regarding your question, on the screenshot you have provided, there is "Replace all child object permissions entries with inheritable permission entries from this object" on the bottom part of that.

Have you tried the Repair in-place upgrade?

Create a new user profile.

if this still does not work, it is best to reach out to our Microsoft Support.

If you prefer to contact our phone or chat teams, you can do so by following the link below:

 https://support.microsoft.com/home/contact?ContactUsExperienceEntryPointAssetId=S.HP.outlook

Once you've opened the link, do the following:

(1) Provide a brief description of your problem and click Get Help;

(2) click Contact Supportat the bottom of the****results that appear;

(3) click Confirm after making sure which product you have a problem with**;** and

(4) Finally, you will have the option of contacting an Office chat representative or receiving a call from an Office telephone representative.

Best regards

Lonex P.

Microsoft Moderator

You stated: "You can try to check the box beside the "Replace all child object permissions entries with inheritable permission entries from this object" then Apply > OK."

Where do I do this?

> Check SMB Settings on the Router

On windows, as previously mentioned, SMB 1.0/CIFS connections is checked but only client. Are you suggesting this needs to be checked on the router? There is no SMB 2 or 3 on Windows 10.

> Manually Map the Network Drive Again

This has been done numerous times

> Check File History Permissions

Besides the fact that file history was already working to an existing drive, all permissions have been already granted

>Try a Different USB Port on the Router

Only one port.

Did you see my response to your previous suggestions? Much of this has already been covered.

Hi alocksley

Thank you for trying the steps above.

You can try to check the box beside the "Replace all child object permissions entries with inheritable permission entries from this object" then Apply > OK.

> Check SMB Settings on the Router

Since you're using an Arris Surfboard Router, check if the USB storage settings allow SMB 1.0/CIFS connections.

Some routers automatically disable older SMB versions for security reasons. If possible, try enabling SMB 2.0 or 3.0 instead.

> Manually Map the Network Drive Again

Open File Explorer → Right-click This PC → Map Network Drive.

Assign a drive letter and enter the full network path (\RouterIP\USBDrive).

Try accessing the drive manually before setting it in File History.

> Check File History Permissions

Open File Explorer → Navigate to C:\Users\lahnk\AppData\Local\Microsoft\Windows\FileHistory\Configuration.

Right-click the folder → Properties → Security → Ensure your user account has Full Control.

> Try a Different USB Port on the Router

Some routers have multiple USB ports with different power or compatibility settings.

If available, test the drive on another port.

Perform Repair in-place upgrade: This will reinstall your Operating System and will keep your files and apps. This will take some time depending on the computer performance and internet speed. You can follow the steps from this link: How to do a Windows 10 Repair Upgrade - Microsoft Community

Please let me know if this helps.

Best Regards,

Lonex P.

Microsoft Moderator

Hi alocksley

Thank you for posting in Microsoft Community.

I understand the issue you are facing with error 0x80070002 in File History when trying to change the destination drive. Based on the information provided, it seems like there might be a corruption in the File History configuration. Here are some steps you can try to resolve this issue:

> Reset the File History Configuration

Sometimes issues stem from a corrupted or misconfigured File History database. Even though you’ve already removed some files from C:\Users\*****\AppData\Local\Microsoft\Windows\FileHistory\Configuration, try these additional steps:

Stop File History: Use the Control Panel’s File History manager to stop the backup service.

Backup and Remove Configuration:

Rename (or move) the entire FileHistory configuration folder (both “Configuration” and “Data”) to a safe location. This forces Windows to reinitialize a clean configuration on the next start.

Restart your computer so that any locked handles are released.

Restart File History: Go back to the File History manager, choose “Select drive,” choose your network drive, and allow it to recreate the configuration files.

These steps can clear out any residual corruption that might be causing the error .

> Check Network Drive Access and Permissions

Even though you have confirmed that individual files can be copied manually to your network drive, File History can be more finicky with network locations. Consider these points:

Mapping and Consistency:

Ensure that you consistently map the network drive using a fixed drive letter and that it remains connected at login.

Instead of relying solely on the mapped drive letter, try using the UNC path (e.g., \server\share) when setting up File History.

Permissions:

Double-check that your user account has full control (read/write/modify) on the network share.

Verify that the share and NTFS permission settings do not conflict.

These adjustments ensure that File History isn’t tripped up by permission issues or network path inconsistencies .

> Check Windows Services and System File Health

Misbehaving system services or corrupted system files might also contribute to this error:

Confirm File History Service:

Open Services (Win+R, type services.msc).

Ensure the “File History Service” is set to Automatic and is currently running. Restart the service to see if that helps clear temporary glitches.

Run System File Checker and DISM:

Open Command Prompt as an Administrator.

Run the following command to verify integrity of Windows system files:

sfc /scannow

If SFC finds issues that it cannot resolve, subsequently run:

DISM /Online /Cleanup-Image /RestoreHealth

Performing these checks addresses any underlying system file problems that could interfere with File History’s operation .

> Additional Considerations

Antivirus/Firewall Interference: Sometimes, security software might block File History’s access to the network drive. Temporarily disable your antivirus or firewall (if you have full control and understand the risks) and then try the backup again.

Remove “Move Existing Files” Option: If File History is stumbling over a migration step, try setting up a fresh backup without choosing the “move existing files” option. You might replicate your previous backups later if needed.

SMB Protocol and Network Configuration: Ensure that your network drive is sharing via an SMB version that Windows 10 supports. Occasionally, conflicts occur if the share’s configuration differs from what File History expects.

Perform Repair in-place upgrade: This will reinstall your Operating System and will keep your files and apps. This will take some time depending on the computer performance and internet speed. You can follow the steps from this link: How to do a Windows 10 Repair Upgrade - Microsoft Community

Please let me know if this helps.

Best Regards,

Lonex P.

Microsoft Moderator

Results:

> Reset the File History Configuration

A little worse. Got a message "The system cannot find the file specified" without an error code.

The log message was "Unable to start a backup cycle for configuration C:\Users\lahnk\AppData\Local\

Microsoft\Windows\FileHistory\Configuration\Config"

> Check Network Drive Access and Permissions

Here's a shot of the permissions from the properties of the drive.

> Check Windows Services and System File Health

"Windows Resource Protection did not find any integrity violations."

Didn't get far enough to "remove “Move Existing Files" this time.

Finally, SMB 1.0/CIFS File Sharing Support > SMB 1.0/CIFS Client is checked. Not "Automatic Removal" or "Server". SMB Direct is also checked.

If it's any help, I'm trying to connect to a drive in the USB port of my Arris Surfboard Router. Again, this has worked in the past (I'm moving to a bigger USB drive), although it has quietly quit working along the way.

Hi alocksley

Thank you for posting in Microsoft Community.

I understand the issue you are facing with error 0x80070002 in File History when trying to change the destination drive. Based on the information provided, it seems like there might be a corruption in the File History configuration. Here are some steps you can try to resolve this issue:

> Reset the File History Configuration

Sometimes issues stem from a corrupted or misconfigured File History database. Even though you’ve already removed some files from C:\Users\*****\AppData\Local\Microsoft\Windows\FileHistory\Configuration, try these additional steps:

Stop File History: Use the Control Panel’s File History manager to stop the backup service.

Backup and Remove Configuration:

Rename (or move) the entire FileHistory configuration folder (both “Configuration” and “Data”) to a safe location. This forces Windows to reinitialize a clean configuration on the next start.

Restart your computer so that any locked handles are released.

Restart File History: Go back to the File History manager, choose “Select drive,” choose your network drive, and allow it to recreate the configuration files.

These steps can clear out any residual corruption that might be causing the error .

> Check Network Drive Access and Permissions

Even though you have confirmed that individual files can be copied manually to your network drive, File History can be more finicky with network locations. Consider these points:

Mapping and Consistency:

Ensure that you consistently map the network drive using a fixed drive letter and that it remains connected at login.

Instead of relying solely on the mapped drive letter, try using the UNC path (e.g., \server\share) when setting up File History.

Permissions:

Double-check that your user account has full control (read/write/modify) on the network share.

Verify that the share and NTFS permission settings do not conflict.

These adjustments ensure that File History isn’t tripped up by permission issues or network path inconsistencies .

> Check Windows Services and System File Health

Misbehaving system services or corrupted system files might also contribute to this error:

Confirm File History Service:

Open Services (Win+R, type services.msc).

Ensure the “File History Service” is set to Automatic and is currently running. Restart the service to see if that helps clear temporary glitches.

Run System File Checker and DISM:

Open Command Prompt as an Administrator.

Run the following command to verify integrity of Windows system files:

sfc /scannow

If SFC finds issues that it cannot resolve, subsequently run:

DISM /Online /Cleanup-Image /RestoreHealth

Performing these checks addresses any underlying system file problems that could interfere with File History’s operation .

> Additional Considerations

Antivirus/Firewall Interference: Sometimes, security software might block File History’s access to the network drive. Temporarily disable your antivirus or firewall (if you have full control and understand the risks) and then try the backup again.

Remove “Move Existing Files” Option: If File History is stumbling over a migration step, try setting up a fresh backup without choosing the “move existing files” option. You might replicate your previous backups later if needed.

SMB Protocol and Network Configuration: Ensure that your network drive is sharing via an SMB version that Windows 10 supports. Occasionally, conflicts occur if the share’s configuration differs from what File History expects.

Perform Repair in-place upgrade: This will reinstall your Operating System and will keep your files and apps. This will take some time depending on the computer performance and internet speed. You can follow the steps from this link: How to do a Windows 10 Repair Upgrade - Microsoft Community

Please let me know if this helps.

Best Regards,

Lonex P.

Microsoft Moderator