'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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-03T19:50:29+00:00

    I am pretty sure this may be hardware specific. All 3 of my new intel 1100 builds worked after a fresh install of windows 11. The MSI 390 Gaming Plus system could not be fixed back to its former glory no matter what was done to it.

    BTW the 390 system was the only one that Windows memory checker worked without any issues on reboot. This leads me to believe that the old memory checker inside of Windows may have a security conflict with the new security implementations.

    I can assure you that a lot of folks have this broke and many of us tested software and hardware for a living.

    It's ok when older hardware gets kicked to the curb, but the promise was the 390 MOBOs were compliant.

    Buckle up since more changes are in the pipeline to hide stuff in different places. Settings has changed again.

    My last build forced dynamic drives on my unit, and I cannot figure out what I did or didn't do to deserve that. LOL

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-01-03T20:03:30+00:00

    I did a total clean installment of windows 11 and still the same problem

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2023-01-11T16:49:49+00:00

    Worked very well! Finally. I have gone through tons of proposed fixes but none has worked until now. Thank you!

    Should the 1.0.2207.20002-0 folder be kept in the SecurityHealth folder after installing the earlier version of windows security?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments