'Standard hardware security not supported', till now the error is not fixed in Version 10.0.22621.674 also.

Anonymous
2022-10-14T15:30:26+00:00

Is Microsoft aware of this issue and working on it?

* Moved from Virus & Malware

Windows for home | Windows 11 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-11-13T12:25:26+00:00

Yesterday, I contacted the Microsoft Windows Support Team. They informed me that this issue has been identified and, to resolve it, an update will be released soon (probably by the end of this month).

I reverted back to Windows 10 four days ago. Today I got a notification for the Windows 11 22H2 update. Please inform me when they release the fix so that I can proceed with the Windows 11 update.

Thank you.

Was this answer helpful?

50+ people found this answer helpful.
0 comments

189 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Enric Cortés 39,445 Reputation points Volunteer Moderator
    2022-11-10T10:43:28+00:00

    Hello, ThumperNut

    "...for all those geniuses who have downloaded unofficial "fixes" from Box, Dropbox, and other Internet sources other than directly from Microsoft..."

    Indeed, you are absolutely right in what you say. But in my specific case, I will tell you 4 important points of my intervention here in this thread:

    1. Before making the settings I discussed, my first recommendation was to create a restore point as a security measure (page 6).
    2. I said: "The ideal solution has to be implemented by Microsoft through a new update for the Windows Security Platform for Windows 11 22H2."
    3. I also warned: "make these settings at your own risk".
    4. And the most important. The Box download file is mine, uploaded by me to my Box account. To try to solve this problem I did a lot of tests on my computers. In one of them I saw that I had this problem and looking for a solution it occurred to me to reinstall the "Windows Security Platform Update" application. It did indeed work.

    That is, before committing to "unofficial fixes", I try to reproduce the problem and look for possible solutions on my test machines. And when I have a "solution" I expose it here and in my Spanish community, with the obligatory security and responsibility notices. I've been at this for many years, and I know what I'm doing.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-11-30T17:02:04+00:00

    I did the same and downloaded the file from Enrics post (page 9 of this thread) I had to change ownership of the folder.

    Download from this link the folder that contains the application:

    https://app.box.com/s/8br9g6arlce8pgxx5hmh6t1jcv4zj2s0

    Now follow these steps:

    1. Create a restore point first
    2. Unzip the downloaded ZIP file on the Desktop
    3. Navigate to the location C:\Windows\System32\SecurityHealth to take ownership of that folder:

    Properties > Security > Advanced Options > Change > Administrators

    Check the "Replace owner on subcontainers and objects" box and click Apply.

    In the "SecurityHealth Permissions" window select Administrators > Full Control. Apply.

    1. Copy the "1.0.2207.20002-0" folder on the Desktop to the SecurityHealth folder
    2. Open the folder and run the application "Microsoft.SecHealthUI_8wekyb3d8bbwe.appx" as administrator to update.
    3. Restart the computer.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-11-10T03:42:03+00:00

    Still now, it's not fixed in 22621.819 build too. Is Microsoft aware of these kinds of issues. It's a request to Windows Security Team to release a fix soon.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-10-26T05:39:53+00:00

    Thanks for following up, but I don't see any point in reinstalling over the top when this has just been a fresh 22H2 install from an ISO - this is just a waste of time trying to fix something that shouldn't be broken. The point of providing this information was so that the PG can fix the problem so that multiple people don't have to try apply workarounds to get the product working. Thanks

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments