Standard Hardware Security Not Supported in Windows 11

Standard hardware security not supported means Windows Security found at least one of its five requirements missing: TPM 2.0, Secure Boot, DEP, UEFI MAT, or support for memory integrity.

Find the missing one from Windows first, then switch it on in the PC's UEFI settings. If everything checks out and the message showed up right after Reset this PC, the summary line itself is stuck, and that case needs heavier fixes.

What the five requirements are

The line sits at the bottom of Windows Security > Device security. Microsoft's Device protection page says: "This means that your device does not meet at least one of the requirements of standard hardware security."

TPM 2.0 is the security processor, a chip or firmware feature that holds your encryption keys. Secure Boot lets the PC load only signed startup software. Both are switches in the UEFI, the setup screen your PC shows before Windows starts.

DEP (Data Execution Prevention) stops code from running in memory set aside for data. UEFI MAT, the memory attributes table, is a firmware feature that tells Windows which memory holds code, and only your PC maker can add it.

Memory integrity support is the fifth. It runs inside a walled-off area made with hardware virtualization, so virtualization has to be on in your UEFI, or Windows can't offer memory integrity at all.

Diagram of the five standard hardware security requirements, TPM 2.0, Secure Boot, DEP, UEFI MAT and virtualization for memory integrity, with where to check each one in Windows

1. Check each requirement from Windows

Open Windows Security > Device security. If the page has no Security processor section, your TPM is off or missing. If it has one, open Security processor details and look for Specification version 2.0.

Next, press Win+R, type msinfo32 and press Enter. On the System Summary page, BIOS Mode should say UEFI and Secure Boot State should say On. If BIOS Mode says Legacy, the PC starts the old way and Secure Boot can't run.

Then open Task Manager, select Performance and pick CPU. Virtualization appears under the graph, as Enabled or Disabled. Disabled is enough on its own to cause the message, because memory integrity can't run without it.

Drawing of the Windows Security Device security page with Core isolation, Security processor and Secure boot sections and the Standard hardware security not supported line at the bottom

Finally, back on the Device security page, open Core isolation details. A Memory integrity switch you can turn on means virtualization works; if a driver blocks it, our memory integrity guide covers that case.

With BitLocker or device encryption turned on, find your recovery key before you head into the firmware. Changes to the TPM or Secure Boot can make your PC ask for the key at the next start.

2. Turn on virtualization in the UEFI

Open Settings > System > Recovery and select Restart now next to Advanced startup. Choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart, and your PC starts into its firmware settings.

Intel PCs call the setting Intel Virtualization Technology, VT-x or VMX. AMD PCs call it SVM Mode or AMD-V. It usually sits under Advanced or CPU Configuration. Switch it on, then save and exit.

Change only the settings you came for while you're in there. The firmware screen controls how the PC starts, and a wrong change elsewhere can stop Windows from loading. Back in Windows, Task Manager should now show Virtualization: Enabled.

3. Turn on the TPM

In the same firmware screens, check the Advanced, Security or Trusted Computing menu for the TPM switch. Its name depends on the maker.

Look for Security Device, Security Device Support, TPM State, AMD fTPM switch, AMD PSP fTPM, Intel PTT or Intel Platform Trust Technology. Switch it on, then save and exit.

Back in Windows, press Win+R and run tpm.msc. A status that says it's ready for use, with Specification Version 2.0 under the manufacturer details, means it's done. A version under 2.0 can't meet the standard.

4. Turn on Secure Boot

Secure Boot needs your PC to start in UEFI mode, not Legacy or CSM (the old BIOS-style startup). If msinfo32 already says UEFI, switch Secure Boot on in the firmware's Boot or Security menu, then save and restart.

If it says Legacy, stop there. Switching a Legacy install to UEFI makes Windows unbootable unless its disk is converted from the older MBR layout to GPT first. Our Secure Boot guide walks through that in the right order.

5. Check DEP, then update the firmware

DEP is on unless someone turned it off. Run bcdedit from an administrator Command Prompt, then find the nx line. AlwaysOff means DEP is off; set it back with this and restart:

bcdedit /set {current} nx OptIn

UEFI MAT comes from the firmware itself, so a newer BIOS or UEFI version from your PC maker's support site is the only way to add it. Read the update notes for your model first, and leave a laptop on its charger for the whole update.

6. After a reset, when everything checks out

One owner saw the message after every Reset this PC on Windows 11 22H2, on hardware that met all the requirements. A clean install of Windows 10 followed by the upgrade to Windows 11 cleared it, but the next reset brought it back.

Advisers suggested a repair install, which reinstalls Windows 11 over itself and keeps your files. Another owner tried it and still had the message, so don't count on it.

A third owner rolled the Windows Security app back to an older version and reported "all errors gone". It meant changing permissions on a protected System32 folder, though, which I wouldn't do on a PC you depend on.

When TPM 2.0, Secure Boot and virtualization all check out and memory integrity can be switched on, the hardware is doing its part, whatever the line at the bottom says. All that's left is to report it through the Feedback Hub app.

A different message you might see

System Information's Device Encryption Support line can list reasons such as Un-allowed DMA capable bus/device(s) detected. That's about automatic BitLocker drive encryption, not this message. One adviser mixed the two up.

When the message won't change

If the TPM, Secure Boot or virtualization switch is missing from your firmware, ask the PC maker whether an update adds it. Older PCs with TPM 1.2 or no TPM at all can't reach standard hardware security, whatever you change in Windows.

The Short Version

Three checks find the missing piece: the security processor, msinfo32's Secure Boot State and Task Manager's Virtualization line. Turn on whatever is off in the UEFI. If all pass after a reset, only the summary line is stuck.

Checked November 19, 2026.

If you have any business, I can build it online

Hi, I’m Hamza. I’ve been building websites and online shops for business owners since 2019, and I also built this site you’re reading.

Tell me what business you have or what you’re working on. I’ll look into how much it can grow online, and then we talk. You don’t have to buy anything or hire me first.

Chat with me on my site and I’ll show you proof of businesses I’ve helped and how they’ve grown.

Written by Isaac Smith

Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.

More from Isaac Smith

Leave a Comment