Patch Tuesday Broke Half My Domain: The KB5124008 Secure-Channel Fiasco

I keep waiting for the day a routine Patch Tuesday update does more damage than the vulnerability it's actually fixing, and this September cycle came uncomfortably close. Microsoft's KB5124008, the security update that pushes Windows 11 25H2 to build 26200.9445, has started silently breaking domain trust relationships on enterprise fleets. Install it, reboot, and suddenly the machine can no longer prove itself to Active Directory. Users get the classic "your password is wrong" error even when it isn't, domain logons fail, and admins stare at ERROR_NO_TRUST_LSA_SECRET trying to work out what a Tuesday patch did to their secure channel. Microsoft has confirmed it's aware and investigating, which is as far as you get before you start pulling the update and rejoining PCs to the domain by hand.

The interesting bit isn't that a patch broke something — patches do that, it's in the job description. It's where it broke. The failures trace back to stricter Netlogon secure-channel negotiation settings that KB5124008 turns on, and they line up specifically with Windows Server 2019 domain controllers and certain Windows Server 2022 configurations that don't support the new negotiation level the updated client is now asking for. Reports point at the Windows Machine Identity Isolation feature, especially in audit or enforcement mode, as the tripwire. In other words, this is the old, boring infrastructure doing exactly what it's designed to do: a modern client and an older domain controller negotiate, disagree, and the secure channel drops. The machine account credentials no longer match what AD expects, and the trust relationship quietly rots. It's the kind of thing that surfaces in a Reddit thread and a Microsoft Q&A post long before it lands in a support article, because the symptom — "why is my password wrong?" — looks like a user error until it isn't.

Source article image
Source image 1

What I actually find telling is how the workaround went. Remove KB5124008, rejoin the affected machine to the domain, logon comes back. Reinstall the update, the break returns. That clean round-trip is basically a confession that the patch is the culprit, and it's the sort of confirmation you only get when a fleet of sysadmins independently reproduce the same failure and start comparing notes. The follow-up fix that was supposed to patch over it — KB5129195 — appears to have stumbled too, leaving operators with the same stop-the-deployment, wait-for-the-real-fix posture you get whenever a security feature has quietly outgrown the directory you pointed it at. The takeaway for anyone running a traditional AD environment is a familiar one that keeps getting more expensive: the more modern your endpoint gets, the more it can trip over the domain controllers it depends on, and the blast radius of a single update scales with how old your DCs are. So I'm left with the questi

Source article image
Source image 2
on that matters to anyone who's been burned by this before: if you're still on Windows Server 2019 or early 2022 DCs, do you gate the client side of the fleet on the domain controller's version, or do you just accept that every major client update is now a controlled burn and test it like one?

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more