'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
    2023-01-03T20:26:06+00:00

    Remember what I said on page 6 to fix this issue temporarily, but it's really up to Microsoft to fix it with an update for Windows 11:

    .........................................

    you can try reinstalling Windows Security Platform with the new update. 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.

    Tell us if it worked

    Note: make these settings at your own risk.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-11-06T07:18:22+00:00

    Computers with nothing in the C:\Windows\System32\SecurityHealth folder (empty incl hidden folders/files) still show "Standard hardware not supported" in Windows Security -> Device Security. The workaround above does not fix this, even temporarily until a proper fix is released.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-10-26T09:49:08+00:00

    I'm also facing same issue since 1-2 Months, After the 22H2 Update. I've all the standard security settings enabled. Such as TPM 2.0, Secure Boot, Intel Virtualization and etc. Earlier it was working fine, all the core isolation, memory integrity and other were showing and working fine and as of now all are disabled and it irritates a lot. 7-8 Times I've Reset the Windows 11 with ISO File Still Not Fixed.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-10-21T05:48:05+00:00

    UEFI has always been enabled, and during re-install it was on, as was secure boot, virtualization and TPM 2.0. I'm not sure if windows would boot with it off. And as I said, earlier beta builds were fine this summer, with all HW security features installed (I had to disable the WD driver to get it to work). Just after the latest re-install of a dev build did it all get disabled. This appears to be a somewhat common issue, and there are various threads on it. It is frustrating, and re-installing all apps isn't something I'm going to do again right now.

    I have seen various people claim that moving or deleting subdirectories in the \Windows\System32\SecurityHealth directory fixes this, but this directory is empty for me.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments