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

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. ...

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.

Yes, that was one heck of a valuable contribution on your part, fg2001. And it only begs the question, why does Microsoft think it is acceptable for them, to cause widespread frustration among the users, for such inexcusably long periods of time? You even did the work for them, free of charge! How hard can it be to get that fix distributed along with the frequent Defender updates?

Make sure that core isolation is tuned on in Windows Security and try again.

That doesn't seem to make any difference, I updated 2 different machines one with core isolation on and one off, they both worked fine for me.

The 0x800f0911 0x80070002 errors are caused by something else.

Other users on this thread have worked around the problem doing the update using an ISO file instead of W.U.

Perhaps that is the solution while waiting for a fix from MS. 😉

Even this device below, which does not meet the Windows 11 Requirements updated to 22621.232 without problems. 🤣😂

Unrelated to this topic but I had this issue on another computer and this tip helped fix it. Thanks @fg2001

I was just answering the previous post on page 4 from JohnathanAchuff which is reporting the Security bug on this thread for this build. 😎

Unrelated to this topic but I had this issue on another computer and this tip helped fix it. Thanks @fg2001

I confirm this works and that is the correct fix for the Device Security issue.

Just to come back to the initial topic: I fixed the issue updating using an ISO including the KB created using https://uupdump.net/. Worked like a charm.