I first noticed this issue on 2026-01-07, Wednesday.
My original LinkedIn post, alerting Microsoft to the issue:
https://www.linkedin.com/posts/activity-7414853161020055552-HGbj
Note:
- Expected:
- Version: 5.138
- Filename: Windows-KB890830-x64-V5.138.exe
- Actual:
- Version: 5.137 (?)
- Filename: Windows-KB890830-x64-V5.137.exe.exe
I reported this to Microsoft on or about 2026-01-16, Friday.
Today (2026-01-28, Wednesday) - the problem still had not been corrected.
So, I escalated (yet again)
https://www.microsoft.com/en-us/download/details.aspx?id=9905
This is complete asshatery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2026-01-28 13:30 Wedneday UPDATE:
As of approximately 13:30 (Central Time)
After I escalated (yet again) - it has now been resolved.
[Thank You to Jason Geffner (Principal Security Engineer, Senior Director, Microsoft) for his assistance in getting this communicated to the proper team]
Folks who may have assisted?
Simon Christiansen, Principal Software Development Engineer, Defender for Endpoint at Microsoft


