New
#11
I can live without clean up not sure if file restore words not need to try.
They need bring back Ballmer, these Millennials fools are destroying Windows but hey they gave us 1000's of emoji's.
I can live without clean up not sure if file restore words not need to try.
They need bring back Ballmer, these Millennials fools are destroying Windows but hey they gave us 1000's of emoji's.
Having this exact issue on 21H1 build number 19043.1052
An In-place upgrade didn't fix the issue, nor did the File History reset .bat, so it might be caused by the folder on the backup drive. It might also be related to the fact that Windows has been reset multiple times since I've been using my backup folder.
For me the best solution is to make a new backup folder and rename the existing folder to .old and delete the old backups once a month or so has past to make sure I no longer need them.
I have over six months of backed up files in my current file history and planned on purging old data before moving to a new drive to make the move faster but I guess that's not an option due to Microsoft's bugs.
Also this isn't the first time I've had issues with File History:
File History new setup doesn't work
With the upcoming release of Windows 11 I'm concerned critical issues like this might not be fixed once development resources are moved away from Win 10.
Yeah even after a new install and/or repairing it I still get this error now. Sad to see MSFT degrade in such a manner. They've literally given up.
Haha doh... well, at least we know we're not alone with our grief.Please do continue to see if you can find a way to work around this. Currently, I have to re-configure/re-apply File History from scratch every time it reaches capacity, which is not a pleasant experience, to say the least.