KB5015818: Release Preview Update for Windows 11 v 22H2 Build 22621.232

@JohnathanAchuff,

This security bug was already reported on Build 22621.105.

The problem is caused by a leftover folder from when a new Windows Security platform was installed. No idea why MS did not clean that out.

Check your update history to see if you got this KB5007651.

It will be in the list with the defender definition updates.

Check if you have this folder 1.0.2109.27002-0 in SecurityHealth. If it is there you can delete it with all its contents and the problem will be fixed.

C:\Windows\System32\SecurityHealth\1.0.2109.27002-0

Note that it requires system authorization to delete.

You can use command prompt from recovery mode.

I used the command rmdir <path> /s to delete the folder and all its contents.

rmdir | Microsoft Docs

Also, you probably miss App & browser control, the 2 problems occur together when that folder is present.

I had the same issue on 3 different boxes which had previously received the same Windows Security platform KB5007651.

Deleting that folder fixed the bug on all 3 machines.

The machines that did not have the problem showed

C:\Windows\System32\SecurityHealth\

empty with nothing in it.

This is the folder causing the problems:

I ended up backing up my files and doing a clean install of Windows 11. From there, I was able to run windows update and am on Beta build 22622.290 with Windows Feature Experience Pack 1000.22632.1000.0.

I thought being on this release would have the new File Explorer with tabs, but I do not see them.

I am on Windows 11 Pro,

Try installing the update in safe mode?

Well you see...

Where else would I find Core Isolation? I looked it up in the search, clicked on it and nothing.

Go to Settings. then Privacy and Security, then Windows Security, then Device Security. The top choice on this window is Core Isolation.

Click on the small blue print underneath, "Core isolation details." It will bring you to a screen with Memory Integrity, and one of those slide switches.

Turn Memory Integrity on. (Otherwise known as virtualization based security.)

FYI, first time I did that, it said I needed a newer Realtek audio driver. Got that updated driver from my OEM's support site, installed it, and then no problem turning on memory integrity.

(I could be wrong about this, but initially, you did not need to switch one Memory Integrity to run Windows 11. I seem to recall a note that in one of the Windows 11 Updates, it became mandatory. Although for me, I had already switched it on in Windows 10, just to be sure it worked, when seeing if my PC met all the security requirements.)