“This PC Can’t Run Windows 11” on Your Lenovo? Here’s the Fix
You ran Microsoft’s PC Health Check, full of hope, and it cheerfully announced your perfectly good Lenovo “can’t run Windows 11.” Before you start shopping for a new laptop: on Lenovos, this message is wrong more often than it’s right. The hardware is usually fine — it’s the BIOS settings (TPM hiding under the name “Security Chip,” Secure Boot switched off) that trip the check.
This guide walks through the real requirements, shows you exactly where Lenovo hides the relevant BIOS settings on ThinkPads, Ideapads, and Legions, and tells you honestly what to do if your machine genuinely doesn’t qualify. If setup itself is failing rather than the check, see our guide to Windows 11 installation failures .
Why this happens
- TPM is disabled or set to 1.2. Lenovo BIOSes call it “Security Chip,” and many shipped with it off or on the older 1.2 mode.
- Secure Boot is off. Required by Windows 11, but disabled on machines that shipped with Legacy boot or were tweaked for Linux.
- The BIOS is in Legacy/CSM mode. Windows 11 requires UEFI; Compatibility Support Mode must be off.
- The CPU genuinely isn’t supported. Microsoft’s CPU list cuts off older generations (pre-8th-gen Intel, pre-Ryzen 2000 AMD) even if they’re fast enough.
- The BIOS is outdated. Old firmware can misreport TPM status to the checker.
- PC Health Check itself was buggy. Early versions gave false failures; make sure you’re running the latest version from Microsoft.
How to fix it
Work through these in order — most Lenovos pass after Fix 1 and 2.
Fix 1: Run PC Health Check and note what failed
Don’t guess; let the tool tell you exactly which requirement failed.
- Download the latest PC Health Check app from Microsoft’s Windows 11 page and run it.
- Click Check now and read the results carefully — it lists each requirement with a pass/fail.
- Screenshot or note the failures. TPM, Secure Boot, and processor are the big three.
- If everything passes but the installer still complains, your installation media is probably old — recreate it from the Windows 11 download page .
Fix 2: Enable the Security Chip (TPM 2.0) in Lenovo BIOS
This single setting fixes the majority of Lenovo failures.
- Shut down fully, power on, and press F1 (ThinkPad) or F2 (Ideapad/Legion) repeatedly to enter BIOS setup.
- Go to the Security tab. Find Security Chip (older BIOS) or Security Chip Selection (newer ThinkPads).
- Set it to Enabled, or select TPM 2.0 if there’s a 1.2/2.0 choice. Also enable Security Chip sub-options like Intel PTT if present (PTT is Intel’s firmware TPM — it counts).
- On AMD Lenovos, look for AMD fTPM Switch under Security or Advanced and enable it.
- Save and exit (F10), then re-run PC Health Check.
Fix 3: Enable Secure Boot and UEFI mode
The second most common blocker.
- Re-enter BIOS (F1/F2) and go to the Security tab (ThinkPad) or Boot tab.
- Set Secure Boot to Enabled. If it’s greyed out, first set UEFI/Legacy Boot to UEFI Only and disable CSM Support.
- On ThinkPads: Security > Secure Boot > Secure Boot = Enabled, with UEFI/Legacy Boot under the Startup tab set to UEFI Only.
- Save, exit, and re-run the check. Note: switching from Legacy to UEFI on an existing Windows 10 install requires converting the disk to GPT first (Microsoft’s
mbr2gpttool) or Windows won’t boot.
Fix 4: Update the Lenovo BIOS
Old firmware misreports capabilities to the checker.
- Find your serial number (bottom sticker, or in Lenovo Vantage under Device).
- Go to Lenovo Support , enter the serial, and check for BIOS updates under Drivers & Software.
- Install via Lenovo Vantage (easiest — it handles the flash) or download the BIOS Update Utility — always on AC power.
- After flashing, re-check that TPM and Secure Boot are still enabled (updates can reset them), then re-run PC Health Check.
Fix 5: Verify CPU and RAM requirements honestly
Sometimes the answer is genuinely no — here’s how to confirm.
- Check your CPU against Microsoft’s supported processor lists (search “Windows 11 supported Intel/AMD processors” on Windows support ).
- Verify 4GB+ RAM: Settings > System > About shows installed RAM.
- If the CPU is the only failure and it’s a generation or two too old, the machine can still run Windows 11 via documented bypasses — but expect possible update issues, and weigh that against a machine that meets the spec.
- If multiple core requirements fail on very old hardware, the pragmatic move is a clean Windows 10 install or a hardware upgrade, not a fight with the installer.
Fix 6: Use Lenovo Vantage to prep the system
Lenovo’s own tool smooths the path.
- Install Lenovo Vantage from the Microsoft Store if it’s not present.
- Run System Update inside Vantage to pull firmware and driver updates — outdated firmware is a sneaky check-failure cause.
- Use Vantage’s Hardware Scan to confirm no underlying hardware faults are confusing the issue.
- Related boot-mode confusion (UEFI vs Legacy) also causes installation failures — the same BIOS screens are involved.
Fix 7: Do a clean compatibility retest
Finish with a clean, definitive test.
- Update PC Health Check to the latest version (Microsoft fixed early false-failure bugs).
- Re-run the check after all BIOS changes — it should now pass on any supported Lenovo from the last several years.
- If it passes, proceed with the Windows 11 install via Windows Update or the Installation Assistant.
- If one requirement still fails despite correct settings, reset the BIOS to defaults (F9 in BIOS, then re-enable TPM/Secure Boot) — a corrupted BIOS setting can report wrong values to the checker.
Closing
“This PC can’t run Windows 11” on a Lenovo is usually the BIOS telling a white lie — the Security Chip is off, Secure Boot is off, or the firmware is old. Flip the right switches in the Security tab, update the BIOS, and the check that failed yesterday passes today. And if your CPU genuinely misses the list, at least you’ll know it’s the silicon, not a setting. For a full checklist of every compatibility-check failure and its fix beyond Lenovo-specific settings, see our general “This PC can’t run Windows 11” troubleshooting guide .
