“This PC can’t run Windows 11” is the gatekeeper message that stops the upgrade before it starts. The PC Health Check app runs through Microsoft’s requirement list — CPU, RAM, storage, UEFI, Secure Boot, TPM 2.0 — and if anything fails, you get this message, sometimes with specifics and sometimes infuriatingly vague.
Here is what most people discover: their laptop is perfectly capable, but TPM or Secure Boot is simply turned off in the BIOS. Manufacturers shipped millions of machines with these features disabled by default. The fixes below walk through identifying the actual failed check and enabling what is missing, which resolves the large majority of these blocks.
Why this happens
- TPM disabled in BIOS. The hardware exists but is switched off — the number one cause.
- Secure Boot disabled or unsupported boot mode. Legacy/CSM boot instead of UEFI.
- CPU not on Microsoft’s supported list. Older processors fail the check regardless of capability.
- Insufficient RAM or storage. Under 4 GB RAM or 64 GB storage fails outright.
- Outdated PC Health Check results. The app sometimes caches old results; re-running after BIOS changes matters.
- MBR-partitioned system disk. Legacy partition style incompatible with UEFI/Secure Boot requirements.
How to fix it
Work through these in order, re-running the compatibility check after each change.
Fix 1: See exactly which check failed
Do not guess — the checker tells you.
- Download the PC Health Check app from Microsoft’s website (linked via Microsoft Support ) if you do not have it.
- Run it and click Check now.
- Click See all results to expand the full list — note precisely which items show red.
- The fix for each red item is below; green items need no action.
Fix 2: Enable TPM 2.0 in the BIOS
The most common fix.
- Restart and enter the BIOS (F2 or Del during boot; F10 on many HPs, F1 or Enter then F1 on Lenovos).
- Look under Security or Advanced for TPM, Intel PTT, or AMD fTPM and set it to Enabled.
- Save and exit.
- In Windows, press
Win + R, typetpm.msc, and confirm Status reads “The TPM is ready for use” with specification version 2.0.
Fix 3: Enable Secure Boot (and UEFI mode)
The second most common fix.
- In the BIOS, find Secure Boot (usually under Security or Boot) and set it to Enabled.
- Make sure the boot mode is UEFI, not Legacy or CSM.
- Before switching boot modes, check your current setup: open System Information (
msinfo32) and look at BIOS Mode and the disk’s partition style in Disk Management (GPT vs MBR). - If the disk is MBR, convert it first from an admin Command Prompt:
mbr2gpt /validatethenmbr2gpt /convert— back up first, as with any disk operation. - Save BIOS changes, exit, and re-run the check.
Fix 4: Update the BIOS
Newer firmware sometimes adds or fixes TPM/Secure Boot support.
- Check your current BIOS version in System Information.
- Compare with the latest on the manufacturer’s site: Dell , HP , Lenovo .
- Install the update with the charger plugged in; do not interrupt it.
- Re-enter the BIOS afterward — updates sometimes reset TPM/Secure Boot to defaults — and re-enable as needed.
Fix 5: Free storage and verify RAM
If the check flags storage or memory:
- Ensure at least 64 GB total storage with ample free space; run Disk Cleanup with system files.
- Confirm installed RAM in Settings > System > About — under 4 GB fails the check.
- On laptops with upgradeable RAM, adding a stick is cheap and easy.
Fix 6: Bypass checks only as an informed last resort
For genuinely unsupported CPUs where you accept the risks:
- Understand the tradeoff: Microsoft may withhold updates and does not support these installs.
- The documented workaround involves creating the
AllowUpgradesWithUnsupportedTPMOrCPUregistry value — research the current, exact procedure from reputable sources before attempting it. - Back up everything first; unsupported installs are harder to recover when they break.
Brand-specific walkthroughs: can’t run Windows 11 on Lenovo , on Dell , and the full step-by-step compatibility guide . Our troubleshooting overview covers edge cases.
Fix 7: Check for firmware-level blocks and re-run the checker cleanly
Sometimes the checker itself is the problem, or a firmware quirk hides the TPM.
- In the BIOS, look for a TPM Device Selection option — on some boards it toggles between discrete TPM and firmware TPM, and only one is visible to Windows.
- If TPM was already enabled but
tpm.mscshows nothing, try switching between PTT/fTPM options and rebooting between changes. - Uninstall the PC Health Check app, download the latest version fresh, and re-run the check — older builds had bugs that misreported results on some laptops.
- Run the check while plugged into AC power; a few firmware features report differently on battery.
Closing
“This PC can’t run Windows 11” is usually “this PC can run Windows 11 but a BIOS setting says otherwise.” Check exactly what failed, enable TPM 2.0 and Secure Boot in UEFI mode, update the BIOS if needed, and re-run the checker — that sequence clears the block for the overwhelming majority of laptops. Only when the CPU itself is genuinely unsupported do you face a real hardware decision, and even then it is worth weighing your options calmly rather than forcing an unsupported install you will regret. When in doubt, the manufacturer’s support page for your exact model is the authoritative word on what the board supports.
