Forum Discussion
Microsoft support KB5124010, KB5124008: Known issues in this update, Highlights: semantic ambiguity
Hello, I have a question regarding Microsoft is announcement.
Hi everyone,I was reviewing the Microsoft support pages for the September 2026 Windows updates and got quite confused by the wording regarding the File History bug fix. Furthermore, my actual experience after updating doesn't seem to align with the official description. I'd like to hear your thoughts on this.
Question 1: Does the word after in KB5124008 imply a phased/partial fix?
In the Known issues section of KB5124008, Microsoft lists a few specific symptoms:
Incorrectly displaying a Reconnect your drive message.
The Last Backup timestamp might not update, and previously backed-up files might show No previous version available.
Application crash events referencing FileHistory.exe.
However, in the Resolution section, Microsoft states: This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010.
What exactly does after mean in this context? Does it imply that KB5124010 did not completely fix all symptoms, and the remaining issues (like the timestamp bug) will not be fully resolved until the October 13th Patch Tuesday?
Question 2: Why did the KB5124010 release notes omit the timestamp issue?
I then checked the Highlights section for KB5124010, which states:
File History Fixed: This update addresses an issue where File History might fail to back up or restore files... Affected devices might incorrectly display a Reconnect your drive message...
Noticeably, it completely omits any mention of fixing the Last Backup timestamp might not update symptom. Does this omission mean that this specific part of the bug has not been fixed yet?
My Actual Experience:
My suspicions seem to be confirmed in my actual usage. After installing the latest KB5124010 update, my File History can now successfully find the backup drive, run properly, and back up new files (Symptom 1 is resolved). However, the Last Backup date/timestamp still has not changed at all (Symptom 2 remains).
To summarize my questions:
Based on Microsoft is wording, is KB5124010 only a partial fix?
For the lingering issues regarding the timestamp not updating and no previous version available, do I just have to wait for the October update? Has anyone else experienced this exact situation?
3 Replies
Hi sheraton , I read "on and after September 22" as meaning every cumulative update released from that date onward includes the fix, not that it's a phased or partial fix. Since Windows updates are cumulative, KB5124010 and later ones (including October Patch Tuesday) should contain it. That's my interpretation of the wording, though, not something the page spells out.
On the Highlights section, it's a short summary, so it usually names the headline symptom ("Reconnect your drive") and not every detail. The missing timestamp mention doesn't prove that part is unfixed. It may be a side effect of the same fault.
Some things to try for the timestamp:
- Click "Run now" in File History to force a backup cycle, then check "Last Backup".
- Check Event Viewer > Applications and Services Logs > Microsoft > Windows > FileHistory-Engine for errors.
- Restart the File History Service (fhsvc) in services.msc, or reboot.
- If it still doesn't update, turn File History off and on again (your existing backups stay on the drive).
If none of that works, send feedback through the Feedback Hub with your build number so Microsoft can check whether it's a leftover bug.
Hello, on September 23rd, I communicated online with the Microsoft support team and informed them of my issue, which others had also encountered (a small error appeared in the file history log after updating KB5124010). Just today, the Microsoft support team emailed me to inform me that they are aware of the issue and are currently investigating.
Hi, the methods you suggested haven't worked for me. I've already asked a question on Feedback Hub.
