Editorial review: 4 October 2026 UTC. This guide was reviewed against the linked primary sources. Software installation, firmware changes, disk conversion and hands-on compatibility testing were not performed for this review.
A failed PC Health Check result needs a diagnosis before a fix. A disabled security feature, an unsupported processor and a delayed Windows Update offer are different problems. Start by saving the exact failed requirement and your computer model; buying RAM or switching firmware settings cannot solve every failure.
October deadline: Microsoft’s Windows 11 release table lists 13 October 2026 as the end of updates for version 24H2 Home and Pro, with Enterprise and Education continuing until 12 October 2027. A PC that already runs Windows 11 still needs a supported version. See the edition-specific 24H2 support guide.
Read the result before changing the PC
- Open Microsoft’s PC Health Check support page and use its download link if the app is absent. Select Check now and expand the results. The download was not retrieved or signature-tested for this review.
- Record the exact model, CPU name, RAM and Windows edition. Settings → System → About gives a useful starting record. Run
winverto record the Windows version. - Run
msinfo32to inspect BIOS Mode and Secure Boot State, andtpm.mscto inspect the TPM specification version. These inspection steps are instructions for your PC, not results measured by us. - Keep a copy of the failure text. If PC Health Check passes but Windows Update does not offer an upgrade, go to the assessment-refresh section below; do not assume the CPU is unsupported.
What each requirement means
| Requirement | Meaning | Next check |
|---|---|---|
| Processor | Compatible processor: at least 1 GHz, two cores, and an approved CPU. | Record the exact model and use the eligibility result and manufacturer’s support information. Speed alone does not establish support. |
| RAM | At least 4 GB. | Check whether the model permits memory upgrades; soldered memory may prevent this. |
| Storage | A 64 GB or larger storage device. | This is device capacity, not a universal requirement for 64 GB of free space. Installation and later updates still need free space. |
| Firmware | UEFI and Secure Boot capability. | Inspect boot mode before changing it. Legacy mode can conceal capability on a UEFI-capable PC. |
| TPM | TPM 2.0. | Check specification version, not just whether a security processor exists. |
| Graphics and display | DirectX 12-compatible graphics with WDDM 2.0; 720p display larger than 9 inches, 8 bits per colour channel. | Check the graphics driver and display specifications with the manufacturer. |
The Microsoft requirements page also states that Home and Pro for personal use need internet access and a Microsoft account during initial setup. Passing the minimums does not measure how well your workload will run.
TPM not found: distinguish disabled from unavailable
Microsoft’s TPM guide says a missing compatible TPM can mean it is disabled. On supported hardware the firmware option may be labelled Intel PTT, AMD fTPM or Security Device Support; use the instructions for your exact model instead of assuming every firmware menu matches.
If tpm.msc reports a specification below 2.0, the current configuration fails the requirement. Ask the manufacturer whether that model has a supported TPM 2.0 or firmware upgrade path. Enabling a TPM 1.2 device alone does not turn it into 2.0, and buying an arbitrary plug-in TPM module is not a compatibility plan.
Before a firmware or TPM change, save your encryption recovery key somewhere accessible without this PC and make a backup. Do not clear the TPM as an eligibility fix. Its stored keys may be needed to access encrypted data. Microsoft’s TPM maintenance guidance includes backup and administrator precautions. For a managed computer, have the administrator check policy and recovery access first.
Secure Boot and Legacy mode: inspect first
For an upgrade from Windows 10, Microsoft’s Secure Boot guidance distinguishes being Secure Boot capable from having it enabled, while recommending enabling it for protection. An “Off” reading does not by itself mean the motherboard lacks the capability.
A Legacy BIOS-mode installation needs particular care. Switching the firmware to UEFI before the system disk and boot files are ready can leave Windows unable to boot. Check the model’s UEFI support and the system disk’s partition style in Disk Management. Do not change storage-controller mode, reset firmware defaults or delete partitions just to make the eligibility result green.
When MBR2GPT is relevant, and when to stop
Microsoft MBR2GPT documentation describes conversion of an MBR system disk to GPT. It is not a CPU or TPM workaround and cannot convert arbitrary non-system data disks. Conversion requires a supported layout and UEFI-capable firmware; after conversion the firmware must boot in UEFI mode.
Before considering conversion, identify the actual Windows system disk, save the BitLocker recovery key, create a recoverable backup and prepare a boot-recovery route. Do not assume the system disk is disk 0. Validation and conversion are separate operations: /validate checks eligibility, whereas /convert changes the disk. A successful validation does not demonstrate that your backup can be restored.
Microsoft lists layout restrictions, including no extended/logical partition and at most three primary MBR partitions. BitLocker requires a documented protector-handling procedure, not simply forgetting to re-enable protection afterwards. Read the complete procedure for your configuration or get competent help before converting. If validation fails, inspect setupact.log and setuperr.log; do not delete a recovery partition to force a pass. This guide intentionally does not provide a blind disk-conversion command.
PC Health Check passes, but Windows Update disagrees
After supported hardware or firmware changes, Microsoft’s assessment refresh instructions say Windows Update eligibility information can take up to 24 hours to refresh. Run PC Health Check again. If the result stays inconsistent, follow Microsoft’s Task Scheduler procedure: Task Scheduler Library → Microsoft → Windows → Application Experience → Microsoft Compatibility Appraiser → Run, wait until it returns to Ready, then check Windows Update.
A refreshed result does not guarantee an immediate offer. Microsoft also uses compatibility safeguard holds and rollout checks. If an eligible PC has a hold, investigate the named driver or application issue rather than forcing an unsupported upgrade. The release table now lists 26H2 as generally available on 29 September 2026; 26H1 is for certain new devices and is not offered as an in-place update from 24H2 or 25H2. See the Windows version comparison before choosing installation media.
If the hardware still cannot qualify
A bypass does not create official hardware support or guarantee future updates. Compare Windows 10 ESU and alternative operating systems before replacing a working installation. Microsoft’s consumer ESU page currently ends eligible security-update coverage on 12 October 2027; ESU does not restore feature improvements or general technical support. Use the ESU eligibility and regional enrollment guide for the current conditions.
For installation-tool choices, read Rufus, Flyoobe and Media Creation Tool compared. Record which requirement actually failed before deciding whether any of those tools is relevant.
