This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 89%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECJ%3C/text%3E%3C/svg%3E)
"Your files will be temporarily copied to your hard drive until you reconnect your File History drive and run a backup."
I have tried everything I can think of and that ChatGPT has suggested.
I have formatted the entire drive, which has worked before when this has happened.
I have deleted the File History catalogue structure on C:\ as well with no success.
I have tried restarting it in services and restructuring the index as well.
I've tried another harddrive for the backup.
I've also tried inactivating it and activating it again.
It is locked in showing this error 100%.
Any suggestions?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 45%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED2%3C/text%3E%3C/svg%3E)
There is no problem with your PC or the drive, the File History problem you are experiencing is caused by a bug introduced in the September udpate, this is widely reported and Microsoft have indicated they are aware of the problem and they will provide a patch to fix the problem as soon as possible.
That sounds great. Do you have a link or something to their response? I have yet to find anything.
I’ve had this issue before, if I accidentally hit backup without my external drive being on. A deletion and new backup would solve that. But never has it been like this.
Check the 'Known Issues' section on this link Microsoft provides about the KB5124008
Thanks man, I appreciate it. Then it’s nothing to do than to backup manually until it’s fixed. I hope they do, soon. This really sucks. It should have been addressed already one thinks,..
