Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
The Windows 11 LSA bug was fixed with kernel-mode hardware stack protection
Another issue you ca scratch off the list
2 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
Microsoft is always releasing little updates to deal with certain flaws or problems it previously overlooked, so nothing new there.
By the way, theApril Patch Tuesdayupdates have rolled out, so you might want to check that out as well.
Now, the tech giant may have quietly fixed a widespread issue that was affecting Windows Defender recently.
Here’s how Microsoft tackled this annoying bug
After a surge in user reports and complaints, the company confirmed that a recent Defender update, led to an error that caused the Windows Security app to wrongly display Local Security Authority (or LSA) protection as disabled.
KB5007651 (version 1.0.2302.21002), released via theMarch Patch Tuesday, left users worried as the message would suggest that their devices could be vulnerable.
As a result, users were failing to toggle LSA protection to on as a device restart, which was prompted by this change.
Know that it would do nothing and revert the change automatically. Basically, LSA protection would remain disabled even after the PC was restarted as instructed by the Defender app.
The Redmond-based tech giant had provided a workaround for the issue, and it basically involved dismissing such warnings.
That being said, the company have since fixed the problem with a more recent Defender update (KB5007651).
With a new update and as noted fromWindows release health‘s page, Windows Security Service version 1.0.2303.27001 has supposedly fixed the issue, so you don’t have to worry about it anymore.
Experts suggest the issue was resolved by an update to Kernel-mode Hardware-enforced Stack Protection security feature present under Core Isolation (VBS).
This feature was introduced withWindows 11 22H2. However, KB5007651 was released nearly two weeks ago and Microsoft’s known issues dashboard still lists thebug as open.
Others are alsonoticingthat the setting may be disabled by default, or it could be a bug. In order to use the Kernel-mode Hardware-enforced Stack Protection feature, Intel’s Control-flow Enforcement Technology (CET) or AMD Shadow Stack technology is required.
Supported chips include Intel 11th Gen Tiger Lake or newer parts, or AMD Zen 3 and newer, so please keep that in mind.
We will constantly monitor the situation and report anything new. Share your thoughts and ideas with us in the comments section below.
More about the topics:Windows 11 Software & Apps
Alexandru Poloboc
Tech Journalist
With an overpowering desire to always get to the bottom of things and uncover the truth, Alex spent most of his time working as a news reporter, anchor, as well as TV and radio entertainment show host.
A certified gadget freak, he always feels the need to surround himself with next-generation electronics.
When he is not working, he splits his free time between making music, gaming, playing football, basketball and taking his dogs on adventures.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Alexandru Poloboc
Tech Journalist
With a desire to always get to the bottom of things and uncover the truth, Alex spent most of his time working as a news reporter.
