Whynotwin11

WhyNotWin11 results explained: every check, pass and fail

A line-by-line reading of the WhyNotWin11 report: what each of the 11 checks measures, what pass, fail and the question mark mean, and which red lines you can fix.

  • Updated
  • Checked against WhyNotWin11 2.7.0.0
Feature image for the guide: WhyNotWin11 results explained: every check, pass and fail

When WhyNotWin11 finishes its scan, it shows a single window with eleven lines. Each line is one Windows 11 requirement, a coloured status box and the value the program actually found on your PC. Reading that report correctly is the difference between knowing you need a new computer and realising you only need to change two firmware settings.

This guide explains the WhyNotWin11 results window line by line: what each check measures, what Microsoft requires, what a pass or a fail usually means, and which failures can be fixed. It is based on WhyNotWin11 2.7.0.0 and Microsoft's published Windows 11 minimum requirements.

The layout of the results window

The window has three areas.

The title and status column

At the top the program reports that your Windows 11 compatibility results are below. Each row begins with a small coloured box. The colour is always paired with the text of the result, so you do not have to rely on colour alone.

The check names and detected values

The middle of each row names the check, and the right-hand box shows what was detected — for example "64 Bit CPU 64 Bit OS", "Legacy", "TPM 2 Detected" or "195 GB C:". This value is the most important part of the report because it tells you exactly what WhyNotWin11 found.

The guides sidebar

The left side of the window links to short help topics built into the program, including Windows 11 requirements, converting a disk to GPT, enabling the TPM and enabling Secure Boot.

The information buttons and system details

Each row ends with an information button that explains the requirement. Along the bottom, the window shows the computer name, motherboard, processor and graphics adapter, which helps when you compare several PCs.

The summary message

Above the eleven lines, WhyNotWin11 gives an overall verdict in plain words. In the English interface of version 2.7.0.0 the messages include:

  • "Your Computer is ready for Windows 11 and its updates." — every check passed.
  • "Your Computer is NOT ready for Windows 11" — at least one check failed.
  • A note that Windows Update may take up to 30 days to agree with a passing result, and that the Windows Installation Assistant can be used instead.
  • On a PC that already runs Windows 11, an offer to check feature-update compatibility instead.

What the status colours mean

StatusMeaningWhat to do
GreenThe requirement is metNothing
Red with a crossThe requirement is not metRead the value and decide whether it is a setting or hardware
Yellow or warningBorderline or partly metRead the detail; some are acceptable
Question mark or "Check Timed Out"The check could not finishRun as administrator, outside a virtual machine, and try again
"Check Skipped"You skipped it with the /skip switchRun without /skip to include it

The eleven checks one by one

1. Architecture

Windows 11 needs: a 64-bit processor and a 64-bit operating system.

Typical values: "64 Bit CPU 64 Bit OS", "64 Bit CPU 32 Bit OS".

Windows 11 has no 32-bit edition. If the processor is 64-bit but Windows is 32-bit, the line fails. The fix is a clean installation of 64-bit Windows after a full backup; there is no in-place conversion from 32-bit to 64-bit Windows.

2. Boot Method

Windows 11 needs: UEFI firmware.

Typical values: "UEFI", "Legacy".

"Legacy" means Windows starts through the old BIOS compatibility path, often called CSM. Most PCs from the last ten years support UEFI, but Windows was installed in Legacy mode. The usual fix is to convert the system disk to GPT with Microsoft's MBR2GPT tool and then switch the firmware to UEFI.

3. CPU Compatibility

Windows 11 needs: a processor on Microsoft's supported Intel, AMD or Qualcomm list.

Typical values: "Listed as Compatible", "Not Supported", "Unable to Check List" or "Error Accessing List".

WhyNotWin11 compares your exact processor model with the lists. When the PC is online, it downloads the newest lists before checking. A fail here is a hardware limit and cannot be changed with settings.

4. CPU Core Count

Windows 11 needs: two or more cores.

Typical values: "8 Cores 16 Threads".

Almost every PC sold in the last decade passes. A single-core processor is the only common reason for a fail.

5. CPU Frequency

Windows 11 needs: 1 GHz or faster.

Typical values: "3600 MHz".

The program reads the processor's rated speed. Very old or very low-power chips are the only usual fails.

6. DirectX 12 and WDDM 2

Windows 11 needs: graphics compatible with DirectX 12 and a WDDM 2.0 or newer driver.

Typical values: "DirectX 12 and WDDM 2", "DirectX 12 and WDDM 3", "No DirectX 12, but WDDM2", "DirectX 12, but no WDDM2", "No DirectX 12 or WDDM2" or "DxDiag Errored".

The program reads the DirectX feature level your graphics hardware supports, which is separate from the DirectX software version shown in Windows. This line often fails only because Windows is using a generic display driver. Installing the current driver from the graphics maker usually turns it green. If the newest driver still reports an older driver model, the graphics hardware is too old.

7. Disk Partition Type

Windows 11 needs: a GPT system disk for UEFI boot.

Typical values: "GPT Detected" or "GPT Not Detected".

"GPT Not Detected" means the system disk uses MBR. MBR2GPT can convert it without deleting your files, but you must back up first and switch the firmware to UEFI afterwards.

8. RAM Installed

Windows 11 needs: 4 GB or more.

Typical values: "8 GB", "32 GB".

Desktops and many laptops can take more memory. Thin laptops often have memory soldered to the board, in which case it cannot be upgraded.

9. Secure Boot

Windows 11 needs: a Secure Boot capable PC.

Typical values: "Enabled", "Supported" or "Disabled / Not Detected".

WhyNotWin11 reads the Secure Boot state from Windows. If Secure Boot is enabled, or supported but switched off, the requirement for capability is met. If Windows cannot find Secure Boot at all — usually because it is booting in Legacy mode — the line fails.

10. Storage Available

Windows 11 needs: a 64 GB or larger storage device.

Typical values: "195 GB C: 6 Drive(s) Meet Requirements".

The check looks at the size of the system drive. Small eMMC tablets and very old SSDs are the usual fails.

11. TPM Version

Windows 11 needs: Trusted Platform Module version 2.0.

Typical values: "TPM 2 Detected", a lower TPM version, "TPM Status Error" or "Disabled / Not Detected".

Most PCs from roughly 2017 onward have a firmware TPM built into the processor (Intel PTT or AMD fTPM) that is simply switched off. Turning it on in the firmware usually fixes the line. TPM 1.2-only hardware cannot be upgraded in software unless the PC maker offers a firmware update.

Sorting your red lines into groups

Once you know what failed, group the red lines. This tells you whether the PC can be upgraded with settings, with a part, or not at all.

Group A: settings you can change

  • TPM disabled in firmware
  • Secure Boot unsupported because of Legacy boot
  • Boot Method shows Legacy
  • Disk Partition Type shows MBR
  • DirectX 12 and WDDM 2 fails because of an old or generic driver

Group B: parts you might replace

  • RAM below 4 GB on a PC with free or replaceable slots
  • Storage below 64 GB on a PC with a replaceable drive
  • Graphics hardware too old for DirectX 12 on a desktop with a slot for a new card

Group C: hardware limits

  • CPU Compatibility "Not Supported"
  • Fewer than two cores or below 1 GHz
  • TPM 1.2-only hardware without a manufacturer update

Three example reports

Real reports usually mix green and red lines. These examples show how to read them.

Example 1: an older desktop installed in Legacy mode

The report shows Boot Method "Legacy", Disk Partition Type "GPT Not Detected" and Secure Boot "Disabled / Not Detected". Everything else is green, including CPU Compatibility.

All three red lines come from the same cause: Windows was installed in Legacy mode on an MBR disk. Converting the disk with MBR2GPT, switching the firmware to UEFI and enabling Secure Boot usually turns all three green. This PC is a good candidate for Windows 11.

Example 2: a laptop with the TPM switched off

Only the TPM Version line is red, showing "Disabled / Not Detected". The processor is a recent model listed as compatible.

The processor almost certainly has a firmware TPM. Enabling Intel PTT or AMD fTPM in the firmware settings should fix the only failure.

Example 3: a fast PC with an unsupported processor

CPU Core Count shows 8 cores, CPU Frequency is well above 1 GHz, but CPU Compatibility shows "Not Supported". TPM and Secure Boot may also be fine.

The processor is fast enough in everyday terms, but it is not on Microsoft's list. No setting can change this. The realistic options are staying on Windows 10 with Extended Security Updates, replacing the processor or the PC, or accepting the risks of an unsupported installation.

Fixing in the right order

Several fixes depend on each other. Doing them in the wrong order can leave a PC that will not start. The safe sequence is:

  1. Back up your files and note any BitLocker recovery key.
  2. Convert the system disk from MBR to GPT with MBR2GPT.
  3. Switch the firmware from Legacy/CSM to UEFI.
  4. Enable Secure Boot in the firmware.
  5. Enable the firmware TPM (Intel PTT or AMD fTPM).
  6. Install the latest graphics driver.
  7. Run WhyNotWin11 again.

When the results look wrong

Checks show a question mark

WhyNotWin11 needs administrator rights to read TPM and Secure Boot data. Run it again and choose Yes at the User Account Control prompt.

You are inside a virtual machine

In a virtual machine, the program sees virtual hardware. TPM and Secure Boot depend on the virtual machine's settings, not on the physical PC.

You are connected over Remote Desktop

Remote sessions use a virtual display adapter. Since version 2.6.1.0 WhyNotWin11 makes an exception for RDP display adapters, but for the clearest graphics result run it at the PC itself.

A brand-new processor shows as unsupported

Older builds carry older processor lists. Connect to the internet so the program can download the current lists, or use the latest release.

Saving the report

To keep a copy, export the results to a text or spreadsheet file:

Export · Command Prompt
WhyNotWin11.exe /export CSV

Without a file name, the report is named after the computer. TSV and TXT formats are also supported.

Summary

Read the detected value on every line, not just the colour. Group red lines into settings, parts and hardware limits, fix settings in the safe order, and run WhyNotWin11 again. Export the report so you have a record of what changed.

Frequently asked questions

Does a single red line mean Windows 11 cannot be installed?

Windows Update offers Windows 11 only when every requirement is met. A single red line can still be fixable, so read the value before deciding.

Why does Secure Boot pass even though it is disabled?

Windows 11 requires a Secure Boot capable PC. WhyNotWin11 treats "supported but disabled" as meeting that requirement. Turning it on is still recommended.

My TPM line passes but PC Health Check disagrees. Why?

The two tools read the same data but at different times and with different permissions. Run WhyNotWin11 as administrator, restart PC Health Check, and compare again.

Are the system details at the bottom of the window sent anywhere?

No. They are shown locally. They only leave your PC if you export and share the report yourself.

Why does the window say Windows Update may take 30 days?

Windows Update decides eligibility on its own schedule. After you fix a requirement, it can take some time before the Windows 11 offer appears. WhyNotWin11 points out that Microsoft's Installation Assistant can be used instead of waiting.