How to Fix “This PC Can’t Run Windows 11” Compatibility Problems

Introduction

Few messages in computing are as frustrating as the one that appears during a Windows 11 upgrade: “This PC can’t run Windows 11.” Microsoft introduced strict hardware requirements for Windows 11, including TPM 2.0, UEFI Secure Boot, a supported 64-bit processor, at least 4 GB of RAM, and 64 GB of storage. When any of these conditions are not met, the installer blocks the upgrade before it even begins. This guide explains how to diagnose and fix those compatibility problems, whether you are a home user with an older desktop or an IT administrator managing a fleet of mixed hardware.

The truth is that many systems flagged as incompatible are technically capable of running Windows 11 well. The block is often caused by a disabled firmware setting rather than missing hardware. Other times, a genuinely older CPU or absent TPM chip forces a decision: upgrade the hardware, stay on Windows 10, or use a documented workaround. We will cover all three paths, with clear warnings about the risks involved. You will learn how to check each requirement, enable the necessary firmware options, prepare your data safely, run the upgrade, and verify that everything works afterward.

Before you begin, keep one principle in mind: always verify software compatibility with your hardware architecture. Windows 11 ships in x86-64 and ARM64 builds. A Surface Pro X or other ARM-based device needs ARM64 media, while a standard Intel or AMD machine needs x64. Downloading the wrong image leads to failed boots and confusing errors. Also, keep your current operating system updated before installation. Installing updates on Windows 10 or Windows 11 beforehand prevents dependency conflicts and reduces the chance that the upgrade process stalls midway.

Prerequisites

Gather the following before you change any settings or download any tools. Skipping this stage is the most common reason people end up with a failed upgrade and an unbootable machine.

• A Windows 10 or Windows 11 PC with administrative rights. You cannot modify firmware or run the PC Health Check tool as a standard user.
• The official PC Health Check app from Microsoft, which reports exactly which requirement is failing.
• A built-in TPM management console or a way to enter UEFI/BIOS firmware settings. On most machines this is a key pressed at boot, such as F2, F10, Del, or Esc.
• A backup of important files, either to an external drive or cloud storage. Firmware changes and upgrades carry some risk.
• At least 64 GB of free disk space, plus extra room for the old Windows installation if you want to roll back.
• An internet connection and a Microsoft account for the upgrade, or installation media if you prefer a clean install.
• For IT administrators: a hardware inventory, Group Policy or Intune access, and a test device before broad deployment.

Confirm your processor architecture as well. Open Settings, then System, then About. Look for “System type.” It will read “x64-based processor” or “ARM-based processor.” This single line determines which Windows 11 image and which driver packages you need. Mixing architectures causes installation failure and wasted time.

Preparation

Preparation protects your data and your time. Start by running the PC Health Check app. It produces a plain-language list showing TPM, Secure Boot, RAM, storage, and CPU status. Note every red item, because you will address them one by one.

Next, update your current operating system fully. On Windows 10, go to Settings, Windows Update, and install every available update, including optional firmware and driver updates. Vendors often ship BIOS updates that enable TPM 2.0 or improve Secure Boot support. Keeping your operating system updated before installation prevents dependency conflicts with the upgrade assistant and with .NET components that the installer relies on.

Create a restore point and back up your files. If you plan to enable TPM or Secure Boot, check whether your drive uses BitLocker. Enabling these features can trigger a BitLocker recovery prompt, so suspend BitLocker protection before making changes, then resume it afterward. Have your recovery key available.

For IT administrators, prepare a pilot group, document current BIOS versions, and confirm that your management tools support Windows 11. Verify that your line-of-business applications are compatible with the new OS, and check architecture requirements for any ARM64 devices in your fleet. Build a short rollback plan: know how to revert firmware settings and restore the previous OS image if something goes wrong.

Installation Steps

The following procedure walks through diagnosing and resolving compatibility blocks, then completing the upgrade. Work through each step in order.

Step 1: Review prerequisites and compatibility

Reconfirm that you meet every requirement before touching firmware. Windows 11 needs a 1 GHz or faster 64-bit processor with two or more cores, 4 GB of RAM, 64 GB of storage, UEFI firmware with Secure Boot capability, TPM version 2.0, and a DirectX 12-compatible graphics adapter. Check your exact CPU model against Microsoft’s supported processor list, because some older chips are blocked even when other requirements are met.

Run PC Health Check again and write down each failure. If TPM is missing or version 1.2, you likely need a firmware change. If Secure Boot is off, that is a firmware setting. If the CPU is unsupported, you face a hardware decision. Also confirm your architecture: x64 or ARM64. Finally, ensure your PC can reach Windows Update, since the upgrade assistant downloads several gigabytes.

Step 2: Prepare the environment

Enter UEFI/BIOS and set the platform correctly. The exact menus differ by vendor, but the goals are the same. Enable UEFI boot mode and disable legacy or CSM mode if your drive is GPT. Turn on Secure Boot. Enable the TPM or Platform Trust Technology (PTT) option, which may be listed under Security, Advanced, or a CPU-specific name such as AMD fTPM or Intel PTT. Save and exit.

Back on the desktop, confirm the changes took effect. Run tpm.msc and check that the status reads “The TPM is ready for use” with specification version 2.0. In System Information, verify that Secure Boot State is “On.” If your machine has a firmware TPM that cannot reach version 2.0, a discrete TPM module may be required. Suspend BitLocker before rebooting so the drive does not lock.

Step 3: Configure core settings

With firmware sorted, configure Windows itself. Make sure the system drive is partitioned as GPT and booting in UEFI mode. You can check this in Disk Management or with msinfo32. If your disk is MBR, converting it to GPT is possible but risky; use Microsoft’s MBR2GPT tool only after a full backup, and only on a system whose firmware supports UEFI.

Free up storage so you have more than the 64 GB minimum. Uninstall unused applications, clear temporary files, and move large media to external storage. Verify that your Windows Update service is running and that no policy blocks driver installation. For administrators, push the required firmware and TPM settings through your management platform where supported, and stage the Windows 11 upgrade for the pilot ring so you can observe results before broad rollout.

Step 4: Run the main installation procedure

Now run the upgrade. The simplest route is the Windows 11 Installation Assistant from Microsoft’s website. It checks compatibility, downloads the image, and upgrades your existing installation while preserving files and apps. Accept the license terms, choose to keep personal files and apps, and let the process run. It typically takes 30 to 90 minutes and reboots several times.

If the assistant refuses to run, download the ISO and use a USB tool to create installation media. Confirm you downloaded the correct architecture. For a clean install, boot from the media, choose Custom, select the GPT system partition, and proceed. IT administrators can use known deployment tools to push the image across managed devices, applying driver packages matched to each hardware model. Avoid unofficial bypass scripts unless you fully accept that you are running Windows 11 on unsupported hardware, which forfeits official updates and support guarantees.

Step 5: Verify the installation

After the final reboot, confirm success. Open Settings, then System, then About, and check that Windows 11 is listed with the correct build. Run tpm.msc to confirm TPM 2.0 is present and ready. Check System Information for Secure Boot State “On.” Open Device Manager and look for warning icons on display, network, and storage devices; missing drivers are common right after an upgrade.

Test core functions: connect to the network, play audio, use a webcam, and print a document. Run Windows Update several times so pending firmware and driver updates install. Finally, re-enable BitLocker if you suspended it, and confirm that your recovery key is stored safely.

Step 6: Configure post-install options

Finish by tuning the system for daily use. Reinstall any applications that did not survive, and confirm their compatibility with Windows 11. Check privacy and security settings, enable automatic updates, and configure backups. If you are an administrator, enroll devices in your management platform, apply baseline security policies, and record which devices required firmware changes so future deployments go faster.

Review performance for a few days. If the machine feels slow, check for background tasks left over from the upgrade, outdated drivers, or insufficient RAM. Consider adding memory if you are near the 4 GB minimum, since Windows 11 runs noticeably better with 8 GB or more.

Post-Installation

Once Windows 11 is running, keep it healthy. Maintain a regular update schedule so security patches and driver updates install promptly. Monitor storage, since Windows 11 and its updates require headroom. Periodically open the PC Health Check app to confirm that your system still meets requirements, especially after firmware updates.

For environments with mixed hardware, document what worked. Note which models needed a BIOS update, which required a TPM module, and which could not be upgraded at all. This record saves hours on the next refresh cycle. Always verify software compatibility with your hardware architecture before deploying new applications, and test ARM64 builds separately from.