Microsoft fixes Windows 11 crashes by patching memory leak

Not shocking.

Good news, folks, as Microsoft has just released a fix for a memory leak issue that was caused during a recent update. This feels like a nigh-on weekly bit of news from us at the moment, but don’t blame us; blame Microsoft for continuing to release updates that do more harm than good so regularly. This time around, the new fix is because of a memory leak caused in the March patches.

Crashing and stuttering issues cropped up in the last couple of weeks due to this month’s patch run, and it’s because of a memory leak that Microsoft has now admitted was the issue. The KB5037422 (OS Build 20348.2342) Out-of-band patch reads, “This update addresses a known issue that affects the Local Security Authority Subsystem Service (LSASS). It might leak memory on domain controllers (DCs). This issue occurs after you install KB5035857 (March 12, 2024). The leak occurs when on-premises and cloud-based Active Directory DCs process Kerberos authentication requests.”

That leak was causing memory issues, and because of that, you get random restarts, Windows insults your children (that’s a joke), and you crash a lot. It’s a whole thing, and we’re obviously happy that a fix has now been introduced because crashes are frustrating, but we can’t be the only ones who feel as though these issues just sort of shouldn’t be happening at this point.

A lot of people will have just uninstalled the patch that was causing the issue, but plenty of PC users aren’t that tech-savvy, and they shouldn’t really have to be. The whole point of all these updates should be to fix things that aren’t working and update security measures to keep them ahead of all of the potential threats. When these fixes need further fixes, they sort or remove people from the pool of people who aren’t comfortable uninstalling updates.

You might be reading that and thinking, “Well, then those people shouldn’t have computers,” and to that, we say, shhhh, stop that. Using a computer is second nature to a lot of us because we grew up with them, but basically anyone older than, let’s use an arbitrary stopping point of 45, didn’t grow up with IT as a class in school. It’s completely unfair for them to have to suffer through these little hiccups once a month because Microsoft can’t seem to handle its own updates. Basically, we’re really hoping that we don’t have to keep reporting these issues, because they simply shouldn’t exist.