File History Stopped Working...

I had problems with win backup and had to put the old drive, disable backup on it, and restart with the new one don't know if this is your problem just an idea.

jamis said:

I've tried several things, but nothing seems to work. I'm very ignorant on permissions, but puzzled that this worked fine until I changed drives, but I've obviously missed a step somewhere.

Yes, it is a permissions issue, error 80070005 means 'access denied'.

Check the permissions on your file history folder. At a minimum, Authenticated Users should have the permissions as shown in the first screenshot for Option One in this tutorial.

Change Permissions of Objects for Users and Groups in Windows 10

jamis said:

The recycle bin on this drive keeps coming up as being corrupted. I don't know what that means, but I'm going to full format the drive again, check permissions, and then try to set up the file history backup options again.

The recycle bin is probably a permissions issue too. The reformat sounds a good idea. But before you do, you could try copying the History folder from it, then putting it back on the newly formatted drive. When setting up File History again you can point it to the existing folder and it should be able to use your previous history too.

jamis said:

"We cannot copy your files to this location"

Apparently this is a badly-worded warning that actually means it's still trying to use File History on your old drive. Seems you need to turn off File History completely before you can start it again on a new drive. This has been a problem since Win8, apparently...

...I read that as meaning "we can't copy files to this location [because there's something wrong with the drive you're pointing to]" when actually it was saying it can't find your old drive and you asked us to get files from it.

https://answers.microsoft.com/en-us/...d6a82d1?page=1

I turned off file history, deleted the folders it had created, full formatted the drive again, and uninstalled the drive. I rebooted the system and renamed the drive as I had named it the same as the old file history drive thinking it would make things simpler. I went through the settings to start file history again and verified that the drive, folders, and files all had all of the access settings for all of the users on the system. Still get 80070005 error. File history set up creates the requisite folders on the drive when the setup process is done. I checked filehistory.exe and wbengine.exe for permissions. Both have read/execute and read only for all users, and both are owned by trusted installer which has full control permission. I manually ran filehistory.exe as administrator and it is displaying a message panel that it is saving copies of the files for the first time. I recall that the first time I ran file history, it took several hours to complete, so I will let it run overnight to see what happens. Beginning to suspect there is a registry entry that is missing, or hosed, from the drive swap, but have no idea at this point what it could be.

Update: After 10 hours, nothing has been written to the backup disk, filehistory.exe is still running, but using no CPU cycles. Going to let it run until tonight.

Update2: After 14 hours, the filehistory backup log is empty. The filehistory core log shows multiple informational events (every time I started file history, no matter how) with event code of 100. The log states "File History operational state has changed" and the stateid code varies from 0 to 255. This event code references excessive length path names on internet postings, but I don't know which yet and again, this all worked prior to the hard drive swap. I know there is some sort of work around for excessive path length names, but haven't had time to look into it yet.