A computer-crashing bug found in Windows!
The Local Security Authority Subsystem Service (Lsass) Memory Leak error, introduced in Windows through March updates, is causing serious problems and crashes on domain control devices. According to Microsoft, this bug affects Windows Server versions 2012 R2, 2016, 2019, and 2022.
Windows update causes domain control devices to crash due to Memory Leak error
The KB5035855 and KB5035857 Windows Server security updates, released on March 12, created a Memory Leak in Lsass. This leak led to memory overload on affected servers, causing system crashes and unexpected restarts.
Administrators on Microsoft Windows forums report continuously increasing Lsass memory usage in most DCs, eventually leading to system crashes. Memory usage slowly rises due to the Memory Leak error.
Will the new Windows 11 update put an end to bugs?
In smaller environments, this situation can be noticed with detailed monitoring. However, in larger settings, hourly memory usage increases more rapidly. More complaints about this Windows issue can be found on platforms like Reddit.
Microsoft made a statement about this Memory Leak, which it mentioned is associated with the processing of Kerberos authentication requests. The company stated that this error could crash Lsass and lead to unexpected restarts of domain control devices.
Microsoft has identified the source of the problem and announced it will release a solution in the “coming days.” Until this issue is resolved, uninstalling the faulty update can provide a temporary fix.
For instance, it’s possible to run the command wusa /uninstall /kb:5035857 in a command prompt with admin rights. Alternatively, administrators can regularly restart their servers to prevent unexpected crashes until Microsoft resolves the Windows issue.
This error could cause significant disruptions in corporate Windows Server environments and underscores the need for Microsoft to be more cautious with such updates. What are your thoughts on the Memory Leak? Feel free to share your opinions in the comments section below.
Your comment has been submitted,
it will be published after approval.