Local Security Authority Protection

The OP and many others, including me, started getting this problem after the January updates, so the problem was already there before this February update. In fact, I have not received that update yet. The last update I have for KB5007651 was received in August (Update for Windows Security platform - KB5007651 (Version 1.0.2207.20002)).

@Davyday,

I never got January 2023 updates for the security. Last kb5007651 I got 1.0.2207.20002 back in Sept 2022, it was working fine with 22H2 Builds 22621, but unfortunately, they sent it out also on 21H2 builds 22000.xxxx and that created a mess with those Builds and had to be removed.

Now this 1.0.2302.21002 was received on Feb 23, 2023, and it created the problems with LSA with current public Build 22H2 22621.1265.

Luckily, I found a way to fix the problem as I described in the other thread. You may check that out or stick with the bug, it is your choice. 🤷‍♂️

Could you remind me where that tread is?

Kenneth

I have already applied the fix on two devices. My point is that I don't think the cause has been correctly identified. In fact, the Surface device I am using now is new last month. It came with 22H1 and was immediately updated to 22H2. It has never had an update for KB5007651. But it had the same problem.

I have already applied the fix on two devices. My point is that I don't think the cause has been correctly identified. In fact, the Surface device I am using now is new last month. It came with 22H1 and was immediately updated to 22H2. It has never had an update for KB5007651. But it had the same problem.

Surface devices are a different game. 🤣🤣 Probably already had kb5007651 updates already installed when it came new. 😎

I use x64 machines.

I had plenty of different issues with kb5007651 starting August 2022.

I had to remove those updates to get rid of the problems, then MS pulled back those updates.

This 2302 is the 1st one that I got on build 22621.1265 after Sep 2022, and it came down only on one machine even if I have 3 more at the same Build level.

I wish I knew what criteria MS is using to decide which machines get those kb5007651 updates.

Anyway, the problem for me started right after that 2302 update was applied and that is the way I fixed the problem.

If you find a better way let me know. 😎

The same Update came down 2 days before on Dev Build 25300, but on Dev Build it did not cause these issues because the LSA was already turned on a few Dev Builds earlier.

We'll see what happens when I get the same 1.0.2302.21002 update on the other machines, if they cause the same problems, I'll file more FBH reports. 😎

The Windows Security guys at MS are not much help and they seem to ignore the problem reports of the last several months. 🤐🤐🤷‍♂️

I still have one machine at 22H1 Build 22000.1574 and already had received 4 kb5007651 that were already causing a bunch of different problems. the 2109 was the only one good for 22H1 the other ones were for 22H2 and should not be even there, because they are not compatible with 22H1. 🤣🤣

Already here "App & browser control" is completely missing from the security dashboard. 🤐🤷‍♂️

Could you remind me where that tread is?

Kenneth

The link was on a post in previous page. Here it is again.

Build 22621.1265 Received Security update KB5007651 1.0.2302.21002 - Microsoft Community