Build 22621.1265 Received Security update KB5007651 1.0.2302.21002 which caused a problem with current public windows Build 22H2.

Question

This update was received on 2/23/2023 and caused several warnings that seem to be caused by incompatibility with current public Windows Build 22621.1265.

There was absolutely no problem before receiving this update, which seems to be for Dev Build 25305 and not for current public Build 22H2.

https://aka.ms/AAjsnwo

Answer 1

On another machine with the same Build 22621.1265 that did not receive that Security update KB5007651 1.0.2302.21002 the security dashboard looks fine without any yellow warnings, and the Windows\Systeme32\SecurityHealth folder is empty.

Answer 2

Hi fg,

Yep, confirmed. this is from my laptop. My desktop also switched off Memory integrity. I turned them back on and restarted on my desktop. The laptop and desktop are on current release.

Wonder what's up with all the screwups on Release lately. Simply unbelievable.

Regards,

Answer 3

Hi fg,

Yep, confirmed. this is from my laptop. My desktop also switched off Memory integrity. I turned them back on and restarted on my desktop. The laptop and desktop are on current release.

Wonder what's up with all the screwups on Release lately. Simply unbelievable.

Regards,

Hi Johnny,

I got this update only on one Desktop. What is the way around this? I have LSA on with DEV build 25300 and it looks fine.

But on the same machine I'm dual booting current public build and it shows the warning after this security update was installed.

I can dismiss and disable LSA and just leave core Isolation that is already on.

I'm not sure how to deal with it.

If I remove the security update it works as before without LSA, but W.U. reinstalls it as soon as I connect to the internet. 😵‍💫

We went through a similar fiasco back in Sept 2022, then they pulled the KB5007651 updates 2208, 2209 and later, but now we are back to the same situation. 🤐🤷‍♂️

Answer 4

I have only one device running public Win 11 and I don't have that issue. This is lates I have on that device:

Answer 5

Hi Johnny,

I think I found a fix for my problem with security, it is listed in a tutorial in the link below.

Enable or Disable Local Security Authority (LSA) Protection in Windows 11 Tutorial | Windows 11 Forum (elevenforum.com)

I just checked this registry and modified the 2 DWORDs as showing below.

The 1st dword was already there but had a value of 0, the second one I had to add because it was not there.

Seems to work fine now. 😉

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"RunAsPPL"=dword:00000002
"RunAsPPLBoot"=dword:00000002

Edition Windows 11 Pro

Version 22H2

Installed on ‎9/‎21/‎2022

OS build 22621.1265

Experience Windows Feature Experience Pack 1000.22638.1000.0