Forum Discussion
File History has stopped functioning
My file history program has stopped functioning. I tried searching the internet for some of these error messages and I have not found anything that has a solution that works. I tried deleting the backup on my backup drive, and also deleting the file history data/configuration folders so it would "start fresh" and I still keep getting errors.
Here are some of the errors:
Also have gotten a bunch of different errors for "reparse points". This is one example. I tried to exclude some of these folders from the backup but it didn't seem to help. But how do I find and eliminate a "reparse point" so it doesn't cause the file history to fail? And why doesn't file history just ignore those folders and go on and back up everything else?
60 Replies
- AguyCopper Contributor
i be able to fix it but new problem keep showing up
first- i found out the File History stop updating the file's newer version, latest backup in File History is around 1-2 months ago
- I go to delete File History's files to set it up anew > but File History not accepting my drive > i find solution in the internet of deleting File History's cache, fixed > but File history now won't run, clicking "turn on" does nothing, seem to run but then stop, won't turning on > find solution in this site by putting code in CMD as administrator, fixed
BUT NOW, it duplicates files even if the file changes nothing, and as because it keep duplicating, the File Restore menu of File History won't show anything; it keeps saying that "File History is running for the first time..." > i continues to try, but I'm stuck here, files keep duplicating in File History's folders and won't allow me to open its menu to restore file, also there is no version of the file that is already has its backup in File History's folders
So yeah 😅 darkness on all sides, it working but can't use it to restore anything now, even if it keep duplicating the file, so i guess i can only manually pick the file's backup now - sheratonIron Contributor
What angered me the most was that when I asked customer service for the process record of our encountered files, they actually told me to reinstall the system. I was furious; their attitude was very passive.
- shift7solutionsCopper Contributor
My last Successful FileHistory backup was 20July. This was the same time as KB101650 installed.
There are no files written to external drive.```
Get-HotFix -Id KB5101650,KB5121003 -ErrorAction SilentlyContinue | Format-Table HotFixID,InstalledOn,DescriptionHotFixID InstalledOn Description
-------- ----------- -----------
KB5101650 20/07/2026 12:00:00 AM Security Update
fhmanagew.exe -backupnow does nothing.
I have reviewed all configurations. There is nothing remarkable in the eventlogs.
- PhilsFileHistoryBrass Contributor
Ya, when I un-installed KB101650 a few weeks ago, FileHistory worked for a short time until I installed some Windows Updates later. I'm done trying to get it to work.
- sheratonIron Contributor
My situation is slightly different from yours. My last backup was on July 28th, and the problem arose after I updated KB5101684:
- Files can still be backed up to the D: drive normally.
- The Last Backup time in the File History is not updating correctly.
- Newly created or saved Word documents, images, videos, etc., still show No previous version available in Content → Previous Versions.
- PhilsFileHistoryBrass Contributor
Welcome to the club! You are now a member of an elite Windows group.
btw, Thanks for your post.
- sheratonIron Contributor
Even after updating KB5121003, the archive history wasn't fixed. Has Microsoft taken this issue seriously?
- TakketBrass Contributor
So, I was never able to fix this. But I did exclude two folders in which error messages were always occurring. And it ran once I excluded the folders.
BUT.... I tried it today, and now there is a completely different problem. it is not launching the backup. When I plug it in the PC recognizes that drive is plugged in, and the "run now" link appears, but clicking on it does nothing......
- sheratonIron Contributor
Based on your description in the image above, my problem is different from yours. The error occurred on June 1, 2026, at which point the archive history could be accessed.
The anomaly only appeared after KB5101684 was updated on July 29th.
- sheratonIron Contributor
Mine is showing the same symptoms. The last file date I see on the external drive in the archive history is July 28, 2026, and KB5101684 was updated on July 29, so it's clearly related to KB5101684. It's still staging files on the C drive, and I've wasted too much time trying to fix this. I hope the next cumulative update will fix it; it's excessive that Microsoft refuses to admit its mistakes.
- SeniorMoment77Tin Contributor
File History has recently stopped working for me. I have tried numerous fixes, including those mentioned by several of the other contributors. Nothing worked. This is very frustrating.
- PhilsFileHistoryBrass Contributor
Try this Senior:
https://techcommunity.microsoft.com/discussions/windows11/file-history-has-stopped-functioning/4510472/replies/4543231
- cheshirecatnycTin Contributor
Same symptoms. The last files I see on my external drive under File History are from 7/14/26, so it's pretty obvious that it's related to KB5101650 or KB5100998. It is still staging files on C:, and I've wasted enough time trying to fix this. I'm hoping the next cumulative addresses it.
- sheratonIron Contributor
The issue remains unresolved even after the 8.28 update. It's unclear what Microsoft is doing.
- sheratonIron Contributor
My situation is slightly different from yours; the anomaly only appeared after I updated KB5101684.
- MikeAnnandaleTin Contributor
Same problem - my last update was 7/29/2026. Drive is readable by file explorer so it doesn't appear to be a connection problem
- LarryM11Tin Contributor
I tried stopping file history service, deleting existing config, re-assigning drive, restarting service... this fixed the problem on my Win 11 home machine, but the same problem (coincidentally starting on 7/28/26) persists on my Win 11 pro machine. What the hey?