'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 No 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 No comments

189 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-11-14T06:13:35+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.

    are u sure they are gonna do it im having the same issue

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Enric Cortés 39,445 Reputation points Volunteer Moderator
    2022-11-05T19:26:38+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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-11-03T06:14:16+00:00

    Reinstalling Windows 11 will not solve this and it's a waste of time as you say. So is messing around with virtualisation settings and group policy. Even after applying all updates up to build 755 (as at 3 Nov 2022), the hardware is still not detected correctly on some computers, so just ignore it until a bug fix is released.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-11-02T09:16:05+00:00

    Image

    Is Microsoft aware of this issue and working on it?

    * Moved from Virus & Malware

    Hii. I am also facing the same issue. My device meets all the requirements still it is showing this. This problem was not before. Is this a bug? Anyone found any solution?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments