File History problems after installing KB5124008, KB5126052, andKB890830

Question

File History problems after installing KB5124008, KB5126052, andKB890830

BobHayes-3027 15

Ran Windows Update on two sepearate Windows 11 computers that were all up to date as of Saturday morning - broke File History

Today I ran File History on 2 computers - both ran correctly. Then ran Windows Update and File History on both are now broken. File History panel pops up but will not run - says to connect a drive. (drive was connected and verified that I could read and write to it)

Reached out to support who logged on to one of the computers, but troubleshooting did not provide an answer. Later I connected a drive and configured File History on a 3rd computer - it was working. Then I ran Windows Update and it broke it.

Updated the case number and was told now by two seperate techs that it seems to be an issue with one of the updates and was passing it on to level 2 with the detailed testing notes I provided.

The three updates that were installed were

2026-09 Security Update (KB5124008) (26200.9445)

2026-09 .NET Framework Security Update (KB5126052)

Windows Malicious Software Removal Tool x64 - v5.145 (KB890830)

Working before the update - not working after the update

just letting others know in case they are running into the same issue.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Alan B 0 Reputation points

2026-09-09T08:30:26.7133333+00:00

I'm having the same issues trying to run my back up to file history on my external drive- failed, same error messages as you. Had to do a manual save to the drive. CHATGPT says likely that what you have highlighted is the problem and microsoft will pick up and solve soon.
La Ma 0 Reputation points

2026-09-10T03:41:21.8066667+00:00

I have just now encountered this same problem. I will try uninstalling the Security Update.

Answer recommended by moderator

BobHayes-3027 15

Resolved the issue for now by uninstalling
2026-09 Security Update (KB5124008) (26200.9445)

Did this all three computers that had the issue and it resolved the issue on all three.

La Ma 0 Reputation points

2026-09-10T11:03:37.36+00:00

For me also, uninstalling that Security Update resolved the issue. But of course, I also had to pause updates until the end of the month. I don't want Windows Update to re-install it!
BobHayes-3027 15 Reputation points

2026-09-10T11:23:35.6933333+00:00

You can hide the update from being installed so you can still get other updates. Best method I found was using commands in the admin terminal )PowerShell).

Only caveat is that if Windows Update has already downloaded it, you need to install it, uninstall it, then run the commands to block it. Search "Block the Installation of Certain Windows Updates Using PowerShell" on the Internet.
Carl-L 21,320 Reputation points Microsoft External Staff Moderator

2026-09-10T13:44:21.6933333+00:00

Hello BobHayes-3027,

It's good to hear if you have found a way to resolve this.

If you have any other questions. Feel free to ask.
Derek S 0 Reputation points

2026-09-10T16:44:35.2+00:00
What concerns me about the "uninstall the update" answer is that it doesn't tell us whether Microsoft has:

acknowledged the bug,

logged it,

reproduced it,

or fixed it.

It merely demonstrates a correlation:

"I removed the update and File History worked again."

That's useful information, but it's not the same as a long-term solution.

4 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Alan B 0 Reputation points

2026-09-09T08:30:26.7133333+00:00

I'm having the same issues trying to run my back up to file history on my external drive- failed, same error messages as you. Had to do a manual save to the drive. CHATGPT says likely that what you have highlighted is the problem and microsoft will pick up and solve soon.
La Ma 0 Reputation points

2026-09-10T03:41:21.8066667+00:00

I have just now encountered this same problem. I will try uninstalling the Security Update.
La Ma 0 Reputation points

2026-09-10T11:03:37.36+00:00

For me also, uninstalling that Security Update resolved the issue. But of course, I also had to pause updates until the end of the month. I don't want Windows Update to re-install it!
BobHayes-3027 15 Reputation points

2026-09-10T11:23:35.6933333+00:00

You can hide the update from being installed so you can still get other updates. Best method I found was using commands in the admin terminal )PowerShell).

Only caveat is that if Windows Update has already downloaded it, you need to install it, uninstall it, then run the commands to block it. Search "Block the Installation of Certain Windows Updates Using PowerShell" on the Internet.
Carl-L 21,320 Reputation points Microsoft External Staff Moderator

2026-09-10T13:44:21.6933333+00:00

Hello BobHayes-3027,

It's good to hear if you have found a way to resolve this.

If you have any other questions. Feel free to ask.
Derek S 0 Reputation points

2026-09-10T16:44:35.2+00:00

What concerns me about the "uninstall the update" answer is that it doesn't tell us whether Microsoft has:

acknowledged the bug,

logged it,

reproduced it,

or fixed it.

It merely demonstrates a correlation:

"I removed the update and File History worked again."

That's useful information, but it's not the same as a long-term solution.

Answer 1

Sure - here you go - tried it with two external USB drives and one internal drive, all which I have verified can be read and written to. Microsoft Tech support connected to computer and also verified drive was able to be written too as well as doing SFC and DISM commands. Then finally agreed that since File History was working be the updates (manually run prior to installing the updates) and is now not working after the updates on all three computers it is an issue with one or more of the three updates that were installed.

While that error message was being displayed I manually copied a file over to the backup drive and could also read it.

Rather than trying to blindly uninstall all three updates - what order would you suggest I try to uninstall them in? 2026-09-09_9-32-54

a2026-09-09_9-42-36

Answer 2

Fred Acosta 0

Thank you BobHayes for posting this. I had the same exact issue and removing KB5124008 resolved it.

Much appreciated.

-Fred A.

0 comments

Answer 3

Ezio De Pazzi 126

exactly what you are expericing.

0 comments

Answer 4

Carl-L 21,320 Microsoft External Staff Moderator

Hello Bob H,

Welcome to Microsoft Q&A forum.

Before we proceed, may I have a photo of the situation to check for you? Please remember to remove all personal information before posting.

Additionally, may I know if you can rollback the updates?

I'm waiting for your reply.

Derek S 0 Reputation points

2026-09-10T08:34:38.77+00:00

Greetings all,
If I may just add a little more info from my perspective. I am unable to turn File History off! If I click 'Turn off' it still shows that 'File History is on", as in the photo supplied by BobHayes-3027. If I click 'Run now', that's when the message to "Reconnect your drive" appears. I am able to Stop the File History service by running services.msc, but when it is running again, nothing changes from my description above. While trying this last night, it did create the following folder structure on the backup drive: D:\File History<user_name><System_name> which contained two more sub -folders: 'Configuration' and 'Data'. In 'Configuration, there were two files: Config1.xml and Config2.xml but nothing in data. Again, it says it is turned on but if I click Run now, I get the 'reconnect drive' message.
In addition, Copilot is recommending NOT to uninstall KB5124008, with this being an important Security update, so I am reluctant to try that. Also, there is no option to stop using the currently selected drive or the option to select another drive.
Hopefully some of what I've said here may be of use in helping to diagnose this issue. I'm feeling vulnerable now with out File History running.