Windows 11 Compatibility Check: Audit Every PC in Your Fleet

# Why this matters now Windows 10 stopped receiving free security updates in October 2025. Machines still on Windows 10 are either on paid Extended Security Updates (ESU) or accumulating risk. ESU pricing for commercial customers doubles each year they renew, so the cost of keeping devices on Windows 10 grows on a predictable schedule. That makes a compatibility audit the immediate priority for IT teams.

# What decides whether a PC can run Windows 11 Microsoft's published minimum requirements mix standard specs with firmware settings and an approved processor list. The items that determine upgrade eligibility are:

• Processor: 1 GHz or faster, 2+ cores, on a compatible 64-bit CPU or SoC (must be on Microsoft's approved list).
• Memory: 4 GB RAM.
• Storage: 64 GB or larger device.
• System firmware: UEFI with Secure Boot capability.
• Security: TPM version 2.0.
• Graphics: DirectX 12 compatible with WDDM 2.0 driver.
• Display: 720p or higher, over 9 inches diagonal, 8 bits per color channel.
• Connectivity: internet access and Microsoft account required for some configurations.

Two parts of that list are the hardest to audit at scale: the approved CPU list and firmware/security settings (UEFI, Secure Boot, TPM 2.0). Those requirements live in silicon and firmware, so they're not always present on spec sheets or captured in legacy inventories.

# Single PC vs fleet A compatibility check on one laptop is quick—about two minutes on the machine in front of you. The same check becomes a project when you have hundreds or thousands of devices because you need per-device firmware and processor data.

Most inventories were not set up to report UEFI, Secure Boot, TPM version, or whether a processor is on Microsoft's compatibility list. That means your inventory may show CPU model, RAM, and storage but still leave you unable to answer the central question: which machines can actually run Windows 11?

# How to get a fleet-wide count

• Start by identifying which inventory tools can report firmware and TPM data. If your current hardware inventory cannot report UEFI, Secure Boot, TPM version, and exact CPU model strings, you will need to extend its collection or add a tool that reads those fields.
• Collect per-device values for UEFI vs BIOS, Secure Boot state, TPM presence and version, and the CPU model string. For the CPU, cross-check the exact model against Microsoft's compatibility list.
• Aggregate results to classify devices into: immediately upgradeable, upgradeable after firmware changes (for example, enabling Secure Boot or TPM), or non-upgradeable (hardware lacks required features or has an unsupported CPU).

# Next steps for IT teams

• Use the fleet classification to decide device-by-device whether to upgrade to Windows 11, enable ESU for a limited period, or replace hardware.

# Bottom line