Windows 11 compatibility is no longer a simple check for free disk space — it’s a security and firmware gate that determines whether your PC is eligible for the supported upgrade path, and understanding those gates is essential before you attempt to move from Windows 10 to Windows 11.
Background / Overview
Microsoft rewrote the official floor for consumer Windows in Windows 11: the company requires a 64‑bit processor on a supported list,
TPM 2.0,
UEFI with Secure Boot, at least
4 GB RAM and
64 GB storage, plus DirectX 12‑capable graphics and a modern driver model. These minimums were designed to raise the platform security baseline and enable hardware-backed protections such as BitLocker keys stored in a TPM and Virtualization‑based Security (VBS). This change is the practical reason millions of PCs that ran Windows 10 perfectly well may be denied the “free” upgrade: the barrier is not only performance or storage, it’s platform security and firmware capability. Many relatively recent laptops and desktops shipped with firmware options that can be enabled to meet Windows 11 requirements, but others — particularly machines built before 2018 — may lack the necessary TPM/UEFI support entirely.
Microsoft’s lifecycle calendar also imposes a deadline with consequences. Windows 10 mainstream support ended October 14, 2025, after which security updates and free technical assistance ceased; Microsoft offered a limited one‑year consumer Extended Security Update (ESU) bridge for customers who could not move to Windows 11 immediately. That timeline makes the compatibility check a time‑sensitive decision many users and IT teams must confront now.
Windows 11 system requirements — what they really mean
The checklist (minimum vs. recommended)
- Processor: 1 GHz or faster with 2+ cores, 64‑bit, and on Microsoft’s supported CPU list (Microsoft maintains explicit compatibility lists for Intel, AMD and selected ARM/Qualcomm chips).
- RAM: 4 GB minimum (practical recommendation: 8 GB+).
- Storage: 64 GB minimum (SSD strongly recommended for performance).
- Firmware: UEFI with Secure Boot capability; legacy BIOS/CSM is not supported without conversion.
- TPM: Trusted Platform Module (TPM) version 2.0 — discrete or firmware/fTPM (Intel PTT or AMD fTPM). This is mandatory for a supported upgrade.
- Graphics: DirectX 12 compatible with WDDM 2.x driver.
- Display: >9" diagonal with at least 720p (practically a non-issue for most PCs).
These are the baseline
installation requirements. Microsoft and most hardware vendors recommend higher specs for a smoother experience: a modern multicore CPU (8th Gen Intel / Ryzen 2000 and later or equivalent),
8 GB RAM for everyday multitasking, and an SSD for snappier boot and app performance.
Why TPM 2.0 and Secure Boot are non‑negotiable to Microsoft
TPM 2.0 provides a hardware root of trust for cryptographic keys and attestations; Secure Boot prevents unsigned or tampered boot components from loading. Microsoft built Windows 11’s security model assuming these primitives exist, because they enable stronger protections against firmware and boot‑level attacks, and make features like BitLocker and Windows Hello more resilient. The result: many security mitigations require hardware support, and Microsoft treats that support as a precondition for being counted as a “Windows 11 PC.”
Supported processors and the CPU list — why it matters
Microsoft does not accept “meets the spec in theory” as sufficient for processor eligibility: in practice, the CPU must be from a supported family and generation. That’s why Microsoft publishes explicit processor lists for Intel, AMD and Qualcomm chips. If your CPU isn’t on the list, Microsoft may allow installation via unsupported workarounds but explicitly warns that such systems may be blocked from receiving future updates and security patches. Examples of how companies describe the list:
- Intel support tends to start with 8th‑generation Core processors for many PC classes, with newer generations fully supported.
- AMD support generally begins with Ryzen 2000 series and later.
- Qualcomm’s Windows on ARM chips are selectively supported.
These lists are periodically updated; for the most accurate determination, check Microsoft’s supported‑processors documentation, because a CPU model that was unsupported in 2021 may have been added later (or vice versa) depending on testing and drivers.
How to check if your PC can run Windows 11 — step‑by‑step
Microsoft’s official tool for a definitive check is the
PC Health Check (sometimes called PC Integrity Check). It scans your device, reports whether it can run Windows 11, and explicitly lists any blockers (TPM, Secure Boot, CPU compatibility, storage, etc.. The tool can be found via Windows Update or downloaded directly from Microsoft.
- Download or open PC Health Check: use the Start menu or go to Microsoft’s download link to install the latest version.
- Launch and click Check now. The app inspects the OS, firmware and hardware and returns a clear pass/fail and the exact reasons for any failure.
- If the result is “This PC can run Windows 11,” you can wait for Windows Update to offer the in‑place upgrade or use Microsoft’s Installation Assistant / Media Creation Tool to proceed. If not, the report tells you which specific requirements failed.
Alternative third‑party tools exist (WhyNotWin11, WiseCleaner Checkit) and are useful for deeper diagnostics, but they are not official and should be used with caution. The PC Health Check app remains the authoritative, supported method for eligibility checks.
Common blockers — and how to fix them (what’s practical and what isn’t)
1) TPM 2.0 shows as missing or disabled
- Check with tpm.msc (press Win+R → tpm.msc). If the TPM is present it should report Spec Version 2.0. Many modern boards expose TPM as fTPM (AMD) or PTT (Intel) — firmware options that are frequently disabled at first. Enabling fTPM/PTT in UEFI will often resolve the blocker.
- Desktop motherboards sometimes accept add‑on discrete TPM modules; for laptops this isn’t usually possible. If the board truly lacks TPM support, the realistic options are ESU, replacement or switching to another OS.
2) Secure Boot / UEFI vs Legacy BIOS
- Check with msinfo32 (Win+R → msinfo32) and confirm BIOS Mode = UEFI and Secure Boot State = On. If the system is in Legacy/CSM mode, conversion to UEFI (MBR → GPT) using Microsoft’s MBR2GPT tool is possible on many systems and preserves data if prerequisites are met. After conversion, enable UEFI boot and Secure Boot in firmware. This is a one‑time, careful operation — back up first.
3) Unsupported CPU
- If your CPU is functional but not on Microsoft’s supported list, the upgrade is effectively blocked for official servicing. Community workarounds — registry edits, modified installation media — can install Windows 11, but Microsoft warns these installs may not receive updates and are unsupported. For many users, the most responsible choices are to delay the upgrade, enroll in ESU (if available) or replace the hardware.
4) Insufficient RAM or storage
- 4 GB RAM is the minimum, but performance will be poor; 8 GB or more is far more practical. Storage minimum (64 GB) is driven by Windows image size and temporary expansion during upgrades — using an SSD greatly improves real‑world responsiveness. Upgrading RAM or swapping in an SSD are both straightforward, cost‑effective fixes for many desktops and laptops.
If your PC is not compatible — real options and tradeoffs
- Stay on Windows 10 temporarily: Microsoft provided a consumer ESU bridge extending critical security updates for up to one year past October 14, 2025 in some scenarios. ESU enrollment may require linking devices to a Microsoft account and is explicitly temporary — it is a bridge, not a long‑term solution.
- Fix the firmware or hardware where feasible: enabling fTPM/PTT or Secure Boot in BIOS/UEFI, adding RAM or installing an SSD, or fitting a discrete TPM module on some desktop boards can convert an ineligible machine into an eligible one. These are often the simplest, lowest‑cost actions for users willing to open their machines or change firmware settings.
- Replace the PC: For many households and companies, especially where the CPU is unsupported or TPM is absent, a new Windows 11‑ready PC may be the most straightforward path. OEMs now ship most new systems with Windows 11 preinstalled and enabled security features.
- Install an alternative OS: Linux distributions (Ubuntu, Fedora, Linux Mint) or ChromeOS Flex are viable alternatives that receive regular security updates and may extend the functional life of older machines. This is a practical option for users whose workflows are primarily web‑centric.
- Use unsupported workarounds: These can install Windows 11 on incompatible hardware but carry real and ongoing risks: blocked feature updates, security update denial, and no official support from Microsoft. Generally recommended only for testing or non‑critical systems.
Real risks of installing Windows 11 on unsupported hardware
- No guaranteed updates: Microsoft may block cumulative updates or security patches on unsupported machines, creating a significant long‑term risk for devices that process sensitive data.
- Stability and driver compatibility: Unsupported CPUs or older hardware may lack vendor drivers that are tested for Windows 11, producing performance regressions, device instability, or peripheral failures.
- Compliance and enterprise risk: Organisations running unsupported OS installations may run afoul of compliance requirements or contractual obligations that demand supported platforms for regulated data. Unsupported systems can increase insurance and regulatory exposure.
- False economy: The perceived savings from keeping old hardware and forcing an unsupported install can be eclipsed by the costs of downtime, mitigations, and eventual replacement if a security incident occurs.
A practical, safe upgrade checklist (step‑by‑step)
- Inventory and backup (Do this first)
- Create a full disk image and an additional file‑level backup to external storage or cloud (OneDrive/Windows Backup). Export browser bookmarks and application licences. Verify backups are restorable.
- Confirm current build and updates
- Ensure the device is running a fully patched Windows 10 baseline (Windows 10 version 22H2 where relevant). Install pending updates and reboot until fully patched. This reduces upgrade issues.
- Run PC Health Check (official)
- Install and run PC Health Check, click Check now and record any blockers. If the report flags TPM or Secure Boot as disabled, check firmware.
- Fix simple blockers in UEFI/BIOS
- Enable Intel PTT or AMD fTPM for the TPM, and enable Secure Boot if available. If the system uses legacy BIOS, evaluate MBR2GPT conversion and UEFI switching (back up first).
- Evaluate fixes vs replacement
- If a firmware toggle or inexpensive hardware upgrade (RAM/SSD) clears the blocker, proceed; if the CPU is unsupported or TPM absent, weigh ESU, alternative OS migration, or replacing the device.
- Upgrade path (supported methods)
- If eligible: use Windows Update, the Windows 11 Installation Assistant, or Media Creation Tool for a clean install. In‑place upgrades preserve apps and data most of the time, but keep a verified backup.
- Post‑upgrade checks
- Install OEM drivers, re‑enable third‑party security tools, and run Windows Update until no new updates are pending. Confirm TPM and Secure Boot are active, and test critical apps.
Strengths and benefits of Microsoft’s approach — and the counterarguments
Strengths
- Tighter baseline security: The TPM + Secure Boot requirement reduces the attack surface for boot‑ and firmware‑level exploits and enables hardware isolation features that materially improve resilience.
- Clear upgrade path where hardware supports it: For many devices built from 2018 onward, enabling firmware features yields eligibility, and the official tooling (PC Health Check) makes the path explicit.
- Future‑ready platform assumptions: By enforcing a modern hardware floor, Microsoft can ship features that assume hardware attestation, which benefits security and platform capabilities long‑term.
Counterarguments / Risks
- Economic and environmental friction: Stricter requirements force replacement of otherwise usable hardware and generate e‑waste and cost for consumers and organizations. Critics highlighted this as a significant tradeoff when Windows 11 launched.
- Support gap for otherwise capable machines: Some older CPUs are perfectly capable of running modern workloads but are excluded because they aren’t on the supported list; this creates frustration and perceived arbitrariness.
- Short‑term complexity for users: Enabling firmware features, converting disks to GPT, or adding TPM hardware can be intimidating for non‑technical users and raises the risk of errors if backups aren’t taken.
Final verdict — practical guidance for Windows users and admins
- Run PC Health Check now. It’s the fastest way to know whether your machine is supported and shows precise blockers if it is not.
- If your PC fails only firmware toggles (TPM/Secure Boot), enabling them is usually a safe, supported fix — but back up first and follow vendor instructions.
- If the CPU is unsupported, treat any workaround as temporary and high‑risk; factor in the cost of potential loss of security updates and consider replacement or migration.
- Plan migrations and replacements proactively: Windows 10’s support ended on October 14, 2025, and continued usage without ESU raises measurable security and compliance risk. Use ESU as a limited bridge only when necessary.
- For organizations, test the upgrade on non‑critical systems first, verify application compatibility, and stage rollouts to manage driver and vendor issues — don’t assume a single desktop will behave exactly like a fleet of mixed hardware.
Windows 11 compatibility is fundamentally about security posture as much as raw performance. The tools and guidance are clear: run the official checks, enable firmware features if you can, and choose the upgrade path that balances risk, cost and longevity. For users who can’t or won’t move immediately, ESU or alternative operating systems provide options — but they are bridges, not destinations. The practical, responsible approach is to verify eligibility, back up thoroughly, and plan a migration strategy that protects both data and continuity.
Source: AddictiveTips
Windows 11 Compatibility Check – Can Your PC Run It?