"This PC Doesn't Meet Windows 11 System Requirements": Fix Every Check

"This PC doesn't currently meet Windows 11 system requirements" almost always means one specific thing failed — TPM 2.0, Secure Boot, or your CPU generation — not that your whole machine is too old. Open PC Health Check, click See all results, and it will name the exact line item. Here's the part almost nobody expects: PC Health Check can say your PC is fully compatible while Windows Update, on the very same machine, still shows the error — because the two are checking different things, and one of them is often just wrong.

Jake had a customer's laptop on his bench for three days — a $150 "upgrade it to Windows 11 before the Windows 10 security updates stop" job he'd already quoted and already been paid for. Every time he ran the upgrade, the same line came back: this PC doesn't currently meet Windows 11 system requirements. No further explanation. He'd never seen the words TPM or Secure Boot before that week.

That's the actual problem with this error: it's accurate but useless on its own. Windows Update shows it as a dead end with no detail, and the PC Health Check app — the tool that's supposed to explain it — is a separate download most people never open. Everything below works through the message check by check, in the order they actually come up, starting with the one that blocks the most PCs.

What "This PC Doesn't Currently Meet Windows 11 System Requirements" Actually Means

This is a compatibility message, not a corruption error and not a licensing error. Windows checks a fixed list of hardware requirements before it will offer the upgrade, and if even one item fails, you get the same generic sentence regardless of which item it was. You'll see it in two places, worded slightly differently: as "This PC doesn't currently meet Windows 11 system requirements" inside the PC Health Check app, and as "This PC doesn't currently meet all the system requirements for Windows 11" on the Windows Update page itself, right under where the feature update would normally appear.

Here's the full list Windows checks. Most PCs fail exactly one of the first three.

Step 1 — Find Out Exactly Which Requirement Failed

Guessing wastes time. Do this first, every time:

1. Download the official PC Health Check app from Microsoft's Windows 11 page (it's a small installer, separate from Windows Update).
2. Open it and click Check now under "Introducing Windows 11".
3. If the result is "This PC doesn't currently meet Windows 11 system requirements," click See all results. It will list every check with a pass or fail beside it — not just a single generic line.
4. Note every item marked as failing. Some PCs fail two or three at once, and fixing only one won't clear the error.

Ethan's take: "Don't touch the BIOS until you've done this. I've watched people spend an evening enabling TPM in the firmware, reboot, run the upgrade again, and get the exact same error — because Secure Boot was also failing and they never checked for it. See all results tells you everything that's wrong in one pass."

Fixing "TPM 2.0 Required" — By Far the Most Common Block

TPM stands for Trusted Platform Module — a small security processor that stores encryption keys and verifies your PC hasn't been tampered with before Windows loads. Windows 11 requires version 2.0 of it. Almost every CPU sold since roughly 2016 has a TPM 2.0 implementation built into the chip itself — AMD calls theirs fTPM, Intel calls theirs PTT (Platform Trust Technology) — but PC and motherboard makers frequently ship it turned off by default, especially on machines built before Windows 11 existed as a target.

First, confirm what you actually have. Press Win + R, type tpm.msc, and press Enter. This opens the TPM Management console — a built-in Windows tool for viewing and configuring the module. If it reports "Compatible TPM cannot be found," the chip is either disabled in firmware or genuinely absent. If it shows a specification version, check whether it reads 2.0 or 1.2; anything below 2.0 does not meet the requirement.

1. Go to Settings > System > Recovery, and under Advanced startup click Restart now. (On older Windows 10 builds this same option lives under Settings > Update & Security > Recovery.)
2. Choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. This reboots straight into your PC's firmware setup screen instead of making you mash a function key at the exact right moment.
3. Inside the firmware, look under a menu usually labeled Advanced, Security, or Trusted Computing. The setting itself may be called Security Device, Security Device Support, TPM State, AMD fTPM switch, AMD PSP fTPM, Intel PTT, or Intel Platform Trust Technology — the wording varies by motherboard vendor.
4. Enable it, save, and exit. The PC reboots automatically.
5. Recheck with tpm.msc to confirm it now shows a ready 2.0 module, then rerun PC Health Check.

If you don't recognize any of these labels once you're in the firmware, check your PC manufacturer's support site for that exact model — menu layouts differ enough between Dell, HP, Lenovo, and custom-built boards that a generic screenshot rarely matches what you're looking at.

Fixing "Secure Boot" and "UEFI" Failures

Secure Boot only works with UEFI firmware, not the older Legacy BIOS / CSM (Compatibility Support Module) boot mode. If your PC was originally set up years ago, or came with Windows 7 or early Windows 10, there's a real chance it's still booting in Legacy mode even though the firmware itself supports UEFI. Windows 11 requires "Secure Boot capable" firmware, and Legacy/CSM mode fails that check outright, regardless of whether Secure Boot itself is toggled on.

Check which mode you're on first: open the Run box, type msinfo32, and press Enter. In System Summary, look for "BIOS Mode." It will say either UEFI or Legacy.

If it says Legacy, you cannot just flip a switch in the firmware — the drive itself has to be converted from MBR (Master Boot Record) partitioning to GPT (GUID Partition Table) first, or Windows won't boot afterward.

1. Back up anything irreplaceable first. This step touches the partition structure of your boot drive.
2. If BitLocker or Device Encryption is on, suspend it (see the warning above) before converting.
3. Open Command Prompt as Administrator and run mbr2gpt /validate /allowFullOS to confirm the drive is eligible for conversion without data loss.
4. If validation passes, run mbr2gpt /convert /allowFullOS. This is a built-in Windows tool designed to do this conversion in place, without reinstalling.
5. Reboot into UEFI Firmware Settings the same way described in the TPM section above, switch Boot Mode from Legacy/CSM to UEFI, and enable the Secure Boot option (sometimes buried under a Security or Boot tab).
6. Save, exit, and confirm Windows still boots normally before doing anything else.

Fixing "Processor Not Supported" (the CPU List Problem)

This is the one that has no BIOS setting to flip. Windows 11 checks your processor against a specific approved list, not just raw specs — roughly Intel 8th generation and newer, AMD Zen 2 (Ryzen 3000 series) and newer, and Qualcomm Snapdragon 850 and newer. A processor can be fast, 64-bit, and have plenty of cores and still fail this check, because the list is about which CPUs include the specific security hardware Windows 11 leans on, not about raw performance.

Find your exact processor name under Settings > System > About, then compare it against Microsoft's published Windows 11 supported processors list for your CPU brand. There is no registry tweak or firmware setting that adds your CPU to the list — if it isn't on it, the only paths forward are a hardware change or the bypass route covered further down.

Ethan's take: "This is the one that annoys people most, because it feels arbitrary. It isn't — every CPU on that list has a specific hardware security feature baked in, and the ones that don't get left off. Doesn't make it less frustrating when a perfectly good six-year-old machine gets shut out over it."

Fixing RAM, Storage, and Graphics Failures

These three rarely trip up PCs bought in the last several years, but when they do, they're the cheapest fixes on this whole list.

RAM below 4 GB. Check installed memory under Settings > System > About. On a desktop, this usually means adding a stick; on most modern laptops, RAM is soldered and non-upgradable, which turns this into a hardware-replacement decision rather than a five-minute fix.

Storage below 64 GB. This shows up mostly on older budget tablets and thin laptops built around small eMMC storage. Check free and total space under Settings > System > Storage. If the drive itself is smaller than 64 GB, no amount of cleanup fixes the underlying check — you need a larger drive or a different device.

Graphics not meeting DirectX 12/WDDM 2.0. Genuinely rare on anything with integrated graphics from the last decade. If you see this specific failure, it usually means an outdated graphics driver rather than hardware that can't do it — check for an updated driver from your GPU or laptop manufacturer before assuming the hardware itself is the problem.

When Every Box Is Checked and It Still Says You Don't Qualify

This is the counterintuitive part from the top of this post, and it trips up more people than any single hardware check. PC Health Check will report "This PC meets Windows 11 requirements" — TPM good, Secure Boot good, CPU on the list — and Windows Update, checking the same machine, still shows the compatibility error. These are two separate systems asking two separate questions. PC Health Check evaluates your hardware directly. Windows Update relies on its own eligibility appraisal, cached locally, which can go stale or get corrupted independently of anything actually wrong with your PC.

When that happens, treat the PC Health Check result as the accurate one and work around Windows Update rather than trying to convince it:

Run the built-in Windows Update Troubleshooter first, under Settings > System > Troubleshoot > Other troubleshooters. If that doesn't resolve it, reset the Windows Update components manually: stop the Windows Update and Background Intelligent Transfer services from an elevated command prompt (net stop wuauserv and net stop bits), rename the SoftwareDistribution and catroot2 folders under C:\Windows, then restart both services. Windows rebuilds those folders from scratch and re-evaluates eligibility on the next check.

If the error persists after that, skip Windows Update's own opinion entirely. Download the Windows 11 Installation Assistant or build install media through the Media Creation Tool directly from Microsoft — both perform their own independent compatibility check at install time, and on a genuinely compatible PC, the upgrade proceeds regardless of what the stale Windows Update page still claims.

Windows 11 vs Windows 10 — Where the Requirements Actually Differ

Windows 10 never enforced TPM 2.0, Secure Boot, or a CPU approval list at install time — it would run on almost anything with a 1 GHz processor and 1 GB of RAM. That gap is exactly why so many PCs that ran Windows 10 fine for years suddenly hit this error the moment they try to move to Windows 11: the hardware didn't get worse, the requirements got stricter.

One honest fact worth sitting with if you're still deciding whether to fight this error at all: Windows 10 support ended on October 14, 2025. Windows 10 22H2 still boots, still activates, and still runs, but it no longer receives free security updates. If your PC genuinely can't meet Windows 11's requirements, that isn't a reason to panic about tonight — it's a reason to plan the next step deliberately, which is covered in the section below.

The Bypass Route — Installing Anyway, and What It Actually Costs You

Microsoft explicitly does not recommend installing Windows 11 on hardware that fails these checks, but it also hasn't removed the registry-based escape hatches, which means they're a real option — just one with real trade-offs.

For a clean install with no TPM present whatsoever, the LabConfig method is the one that actually works, because it's the only one that doesn't require some minimum TPM version to already exist:

1. Boot from Windows 11 install media. At the first setup screen, press Shift + F10 to open a command prompt.
2. Type regedit and press Enter.
3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup.
4. Right-click Setup, choose New > Key, and name it LabConfig.
5. Inside LabConfig, create DWORD (32-bit) values named BypassTPMCheck, BypassSecureBootCheck, and, if needed, BypassRAMCheck and BypassCPUCheck, setting each to 1.
6. Close the Registry Editor and continue the install normally.

If you're upgrading in place instead of doing a clean install, and the only failures are TPM version or CPU model (not a total absence of TPM), Microsoft's own documented workaround is a single registry value: set AllowUpgradesWithUnsupportedTPMOrCPU to 1 as a DWORD under HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup, then rerun the upgrade through Windows Update or the Installation Assistant.

Ethan's take: "I'll set this up on my own spare hardware without blinking. On a customer's machine, or on anything running a business? No. If an update someday breaks it, you're the one explaining why, not Microsoft."

If Your PC Genuinely Can't Run Windows 11

If your processor is the blocker and buying new hardware isn't on the table right now, you're not out of options and you're not unprotected by default. Windows 10's Consumer Extended Security Updates (ESU) program is still open for enrollment as of this writing. Enroll through Settings > Windows Update > Enroll now — it requires Windows 10 version 22H2 and a Microsoft account signed in (a local account won't work). Enrollment covers up to 10 devices under one account.

You have three ways to get it: free, if you sync your settings through Windows Backup; free, in exchange for 1,000 Microsoft Rewards points; or a one-time payment of roughly $30 (regional pricing varies, and it's free without the backup requirement in the EEA). Coverage originally ran to October 2026, but Microsoft extended consumer ESU by an additional year in June 2026, so enrolled devices are now covered into October 2027.

The straightforward alternative, if the PC is due for replacement anyway, is simply that: new hardware, which comes with a CPU already on the approved list and TPM 2.0 already enabled from the factory, with none of this to think about at all.

Frequently Asked Questions

What exactly does "This PC doesn't currently meet Windows 11 system requirements" mean?

It means at least one item on Windows 11's fixed hardware checklist — most often TPM 2.0, Secure Boot, or your CPU generation — failed the automated check. It's a generic message that doesn't name the specific failure on its own.

How do I find out which specific requirement my PC is failing?

Download PC Health Check from Microsoft, click Check now, then click See all results. It lists every requirement individually as pass or fail, rather than the single generic sentence.

My PC has a TPM chip installed — why does it still say TPM isn't detected?

Firmware TPM (fTPM on AMD, PTT on Intel) is built into most CPUs from the last decade, but manufacturers frequently ship it disabled by default. Windows genuinely can't see a TPM that's switched off in the BIOS, so it reports it as not detected.

What's the difference between fTPM/PTT and a physical TPM module?

A physical TPM is a separate chip on the motherboard. fTPM and PTT do the same job in firmware, built into the CPU itself, with no extra hardware needed. Windows 11 accepts either, as long as it reports as version 2.0 and is enabled.

Is TPM 1.2 good enough for Windows 11?

No. Windows 11 requires version 2.0 specifically. TPM 1.2 fails the check even though it's a real, working TPM. Check your version with tpm.msc.

Can I buy and install a TPM 2.0 chip on an older motherboard?

Only if your specific motherboard has a physical header for one and the manufacturer sells a matching module for that board — this isn't universal or standardized, so check your exact model before buying anything. Most people are better served checking for a firmware TPM setting first, since it's usually already present and just switched off.

What does "Secure Boot capable" mean if my PC boots in Legacy/CSM mode?

Secure Boot only works with UEFI firmware. If your PC is set to Legacy or CSM boot mode, it fails the Secure Boot check regardless of what the firmware itself is capable of, until the drive is converted to GPT and the boot mode is switched to UEFI.

Will switching my drive from MBR to GPT for Secure Boot delete my files?

Using the built-in mbr2gpt tool, no — it's designed to convert in place without reinstalling Windows or losing data. Back up first regardless, since this changes core partition structure, and validate with mbr2gpt /validate before converting.

How do I know if my processor is on the official Windows 11 CPU list?

Find your exact CPU model under Settings > System > About, then check it against Microsoft's published supported processor lists for Intel, AMD, or Qualcomm. Roughly, that means Intel 8th generation or newer, AMD Zen 2 (Ryzen 3000 series) or newer, and Snapdragon 850 or newer.

Why does PC Health Check say my PC is compatible but Windows Update still shows the error?

These are two different systems. PC Health Check evaluates your hardware live; Windows Update relies on a cached eligibility result that can go stale. Trust PC Health Check's result and reset Windows Update's cache, or install directly through the Installation Assistant instead.

Is it safe to bypass the TPM and CPU checks to install Windows 11 anyway?

It works, but it's officially unsupported. Microsoft explicitly does not recommend it, and it comes with real trade-offs: a permanent desktop watermark and no guarantee the device keeps receiving updates.

Will a PC installed via the bypass method still get security updates?

Usually, at least initially, but Microsoft has stated these devices may be excluded from receiving updates at any point, and that policy isn't something bypassed devices can rely on staying consistent long-term.

Does an unsupported Windows 11 install show a watermark on the desktop?

Yes. Installs on hardware that fails the official checks display a "System requirements not met" watermark in the corner of the desktop, and it doesn't go away on its own.

Should I bypass the checks, or just enroll in Windows 10 ESU instead?

If the PC genuinely fails the CPU or TPM requirement, ESU is the more stable choice for anything you depend on daily — it keeps you on fully supported Windows 10 with security updates through October 2027, with no watermark and no risk of a future update breaking an unsupported configuration.

Does Windows 11 Home really require a Microsoft account even if my hardware is fine?

Yes, on personal setups. Windows 11 Home, and Windows 11 Pro when set up for personal use, both require internet connectivity and a Microsoft account during initial device setup, separate from the hardware checks covered above.

If my CPU is the actual blocker, what's the cheapest real fix?

There isn't a software fix for the CPU check itself. Your realistic options are the unsupported bypass route, Windows 10 ESU to buy time on fully supported updates, or replacing the hardware — and which one makes sense depends entirely on whether this is a daily-driver machine or something you're comfortable experimenting on.

Revision note. Written September 2026, covering Windows 11 and Windows 10. Let me know if it doenst work, we will check and fix it together!!