'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: Newest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2023-03-08T16:45:13+00:00

    Hello.

    Apologies for my bad english.

    That issue (Standard hardware security not supported), from what I've been researching, is caused by an Update for Windows Security Platform.

    It appears that Windows 11 22H2 (build 22621) is not compatible with a previously installed Windows Security Platform update in version 22H1 (build 22000). Although this does not affect all computers because it largely depends on the installed hardware and BIOS settings, as well as the type of installation: in a clean installation there is no such problem.

    Specifically, it is the KB5007651 update, May 2022 for Windows 11 22H1, which already had many installation problems at the time. Logically, the computers updated after Windows 11 22H2 maintain that update that is now not compatible and that causes this problem in Windows Security.

    The ideal solution has to be implemented by Microsoft through a new update for the Windows Security Platform for Windows 11 22H2.

    However, there is a workaround until Microsoft releases the new update: delete the KB5007651 update folder:

    1. Access the following path: C:\Windows\System32\SecurityHealth
    2. Delete the folder 1.0.2109.27002-0 with all its content (be careful with deleting other folders)
    3. Reboot the system.

    Hi Enric,

    Thank you for this thoughtful post. I have spent hours searching for a workaround to this issue on a new i9-13900KF/Z790 platform that was falsely showing "[standard] hardware security not supported" when everything, including BitLocker was working just fine. I did come up a workaround like yours that expected there to be files in the SecurityHealth directory, but mine was, like many others, empty because of a fresh install of Windows 11.

    This is most definitely a bug introduced with a later release of the security platform update. By downgrading to a prior version you posted above, downloading the file, and following the exact procedure you posted, I was able to restore proper functionality, as shown below. Before this all I would see is the "[standard] hardware security not supported" message.

    This does beg the question however - since this is well known now, why is it that it has not been fixed yet by Microsoft? (Not a question for you, just a rhetorical question.)

    In any case, thank you again. For anyone else reading, this workaround works perfectly when your SecurityHealth folder is empty.

    Thanks again!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Enric Cortés 39,445 Reputation points Volunteer Moderator
    2023-03-02T22:26:40+00:00

    Yes, indeed, in a domain network with several computers to fix, it may be faster to use Hiren's BootCD.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-02T19:22:05+00:00

    Just a quick update on my earlier comment. The procedure listed in this thread does still work for fixing the issue. Biggest challenge I have is deleting the contents of the C:\Windows\System32\SecurityHealth folder. It won't work if you can't do that. Between being on a domain account, taking permissions, switching to local admin, booting in Safe Mode, changing ownership of the folder, trying to delete through PowerShell, putting in the Bitlocker key every time I boot in Safe Mode, etc., it's a pain. Easier to just boot off a Hiren's BootCD PE (flash drive) and delete it through that.

    https://www.hirensbootcd.org/usb-booting/

    I thought I had this fixed on all our machines, but apparently one disk image still has the error baked in. Need to update our disk image with the fix. 🤦

    Was this answer helpful?

    0 comments