Whynotwin11

How to download and run WhyNotWin11 safely

Pick the right build, confirm it is the developer's file, get past SmartScreen the safe way and read your first report.

  • Updated
  • Checked against WhyNotWin11 2.7.0.0
Feature image for the guide: How to download and run WhyNotWin11 safely

WhyNotWin11 is one of the most useful free tools for anyone still deciding whether a PC can move to Windows 11. It reads your hardware and firmware settings and shows eleven separate results, so you can see exactly which requirement stands in the way. Because it needs administrator rights to read details such as the TPM and Secure Boot state, it is worth taking a few minutes to make sure the file you run is the genuine one.

This guide walks through the whole process: choosing the correct build, downloading it from a trustworthy source, proving the file is unmodified, getting past Microsoft Defender SmartScreen without lowering your protection, running the checks and understanding what the program leaves behind on your PC. Everything here was checked against WhyNotWin11 2.7.0.0, the current stable release.

What WhyNotWin11 is and who makes it

WhyNotWin11 is a free, open-source Windows utility created by independent developer Robert C. Maehl, known as rcmaehl on GitHub. It is written in AutoIt and released under the GNU Lesser General Public License, version 3 (LGPL-3.0). The full source code is public, which means anyone can inspect what it does or compile it themselves.

The program is not made by Microsoft and is not an official compatibility verdict. Its value is detail: where a simple checker might say only that a PC is not ready, WhyNotWin11 lists every requirement on its own line with the value it detected.

What it checks

WhyNotWin11 tests eleven items:

  • Architecture (64-bit processor and 64-bit Windows)
  • Boot method (UEFI or Legacy BIOS)
  • CPU compatibility (is the exact model on Microsoft's supported list?)
  • CPU core count (two or more)
  • CPU frequency (1 GHz or faster)
  • DirectX 12 and WDDM 2.0 graphics driver
  • Disk partition type (GPT or MBR)
  • RAM (4 GB or more)
  • Secure Boot (capable or not)
  • Storage (64 GB or larger system drive)
  • TPM version (2.0 required)

Step 1: Choose the right build

Version 2.7.0.0 is published in two builds. They are the same program compiled for different processor architectures.

BuildFile nameSizeUse it when
64-bit (x64)WhyNotWin11.exe2.22 MB (2,329,088 bytes)Your Windows is 64-bit — almost every PC from the last decade
32-bit (x86)WhyNotWin11_x86.exe2.10 MB (2,206,208 bytes)Your Windows is 32-bit, or you boot a 32-bit Windows PE

How to tell which Windows you have

  1. Open Settings.
  2. Go to System, then About.
  3. Read the line called System type.

If it says "64-bit operating system, x64-based processor", download WhyNotWin11.exe. If it says "32-bit operating system", download the x86 file. Keep in mind that a 32-bit Windows will always fail the Architecture check, because Windows 11 exists only as a 64-bit system. If the same line says "x64-based processor", your hardware is 64-bit capable and a clean 64-bit installation would solve that particular failure.

There is no ARM64 build of WhyNotWin11 2.7.0.0 in the official release.

Step 2: Download from a trustworthy source

The official home of WhyNotWin11 is the rcmaehl/WhyNotWin11 repository on GitHub, and its Releases page carries the stable files. Copies on other websites can be perfectly genuine, but you can only be sure when the site tells you the exact file name, size and SHA-256 hash so you can compare.

On whynotwin11.app the files are stored as unmodified, byte-for-byte copies of the official 2.7.0 release. The SHA-256 of each copy was calculated and compared with fresh downloads from the version-pinned GitHub release addresses, and they matched.

Sources to avoid

  • Repacks and "installers" — WhyNotWin11 is a single portable .exe. Anything that arrives as a setup wizard with extra offers is not the developer's release.
  • Download wrappers — some portals deliver their own downloader program that then fetches the real file. Skip these.
  • Forks presented as new editions — GitHub hosts several forks and mirrors. They are not the official project, even if the name looks similar.
  • Very old versions — several portals still list 2.6.x releases. Older builds have older processor lists and may report a newer CPU as unsupported.

Step 3: Verify the file before the first run

A SHA-256 hash is a 64-character fingerprint of a file's exact bytes. If even one byte changes, the hash changes completely. Comparing the hash of your download with the published value is the most reliable way to prove you have the genuine file.

Calculate the hash in PowerShell

  1. Open File Explorer and go to your Downloads folder.
  2. Click the address bar, type powershell and press Enter. A PowerShell window opens in that folder.
  3. Run the command below.
Hash check · PowerShell
Get-FileHash .\WhyNotWin11.exe -Algorithm SHA256

For the 32-bit build, replace the file name with WhyNotWin11_x86.exe.

Compare with the published values

FileExpected SHA-256
WhyNotWin11.exe433bca5da906c35029a7cdf55f0739553602649f58acd2b9cdebafdeaba23edb
WhyNotWin11_x86.exefadced08bac46a94b6556a5eda522b2bd60d90a143e282ca80d6741be9765d25

PowerShell prints the hash in capital letters; that does not matter. Every character must otherwise be identical. If the hash is different, delete the file and download it again from a trustworthy source. Do not run a file whose hash does not match.

Check the signature status

Right-click the file and choose Properties. Signed programs show a Digital Signatures tab naming the publisher. WhyNotWin11 2.7.0.0 does not have that tab, because this release is not code-signed. That is expected, and it is exactly why the hash comparison matters: the hash replaces the certificate as your proof of origin.

Step 4: Handle SmartScreen safely

When you open an unsigned program that has not been downloaded by many people, Microsoft Defender SmartScreen may show a blue window titled "Windows protected your PC". This is a reputation warning, not a virus detection. SmartScreen simply does not have enough history about the file.

The safe path

  1. Confirm the SHA-256 matches the published value first.
  2. In the SmartScreen window, select More info.
  3. Check that the app name shown is WhyNotWin11.exe.
  4. Select Run anyway.

If the hash does not match, close the window and delete the file. Never turn off SmartScreen or your antivirus to run a tool. Allow only the single file you have verified.

If your antivirus removes the file

Some security products flag small, unsigned AutoIt programs with heuristic detections. If the file disappears after downloading:

  1. Open Windows Security.
  2. Go to Virus & threat protection and then Protection history.
  3. Find the entry for WhyNotWin11 and note the detection name.
  4. If the original download's hash matched, choose Actions and then Restore, or allow that one file.

Step 5: Run WhyNotWin11

WhyNotWin11 is portable. There is no installer and nothing to set up.

  1. Double-click WhyNotWin11.exe.
  2. At the User Account Control prompt, choose Yes. Administrator rights let the program read the TPM, Secure Boot and disk details. Without them, some checks cannot finish.
  3. Wait a few seconds while it reads your hardware. A progress window may appear while it gathers system information.
  4. Read the results window.

Reading the first report

Each of the eleven lines shows a coloured status box, the name of the check and the value detected — for example "TPM 2 Detected", "GPT Not Detected" or "8 Cores 16 Threads". Green means the requirement is met, red means it is not, and a warning colour or question mark means the result is borderline or the check could not complete. Each line also has an information button explaining the requirement.

The bottom of the window lists details such as the computer name, motherboard, processor and graphics card. These help when you compare several PCs or ask someone for advice.

Step 6: Know what it leaves on your PC

WhyNotWin11 does not install itself and does not change any Windows, firmware or disk setting. It only reads information. It does, however, use a working folder:

  • On start, it unpacks its language files into %LocalAppData%\WhyNotWin11.
  • When the PC is online, it downloads the latest Intel, AMD and Qualcomm supported-processor lists and a PCI device list from the project into the same folder. Offline, it uses copies built into the program.
  • It writes a report file only when you ask it to export results.
  • With the /update switch it downloads a newer build next to the current file.

You can delete the %LocalAppData%\WhyNotWin11 folder at any time; it is recreated the next time you run the program.

Tips for technicians and multiple PCs

Run it from a USB stick

Because WhyNotWin11 is a single file, you can carry it on a USB stick and run it on each PC you look after. Keep both builds on the stick if you work with older 32-bit installations.

Use it before Windows is installed

Version 2.7.0.0 adds full Windows PE support. Technicians can boot a Windows PE environment and check hardware before any operating system is on the disk. Use the x86 build if your Windows PE image is 32-bit.

Save a copy of the results

To keep a record, run:

Export · Command Prompt
WhyNotWin11.exe /export TXT

Without a file name, the report is named after the computer. CSV and TSV formats are also available for spreadsheets.

Keeping WhyNotWin11 up to date

Processor support lists change over time, and new WhyNotWin11 releases add detection improvements. There are three simple ways to stay current.

Let it refresh its lists

When the PC is connected to the internet, WhyNotWin11 downloads the latest supported-processor lists at start-up. For most people this is enough, because the CPU list is the part that changes most often.

Use the built-in update switch

Running WhyNotWin11.exe /update downloads the newest stable release and saves it as WhyNotWin11_Latest.exe in the same folder. Treat that new file exactly like a fresh download: check its hash against a trustworthy published value before you run it.

Use winget

If you prefer a package manager, Windows Package Manager can install and upgrade the program with the package ID rcmaehl.WhyNotWin11. The command winget upgrade --id rcmaehl.WhyNotWin11 -e fetches a newer version when one is available in the winget catalogue.

Whichever method you choose, avoid "testing" or nightly builds unless you need a specific fix. They are unstable by design and must be updated by hand.

Troubleshooting common problems

ProblemLikely causeWhat to do
Nothing happens after double-clickAntivirus blocked or removed the fileCheck Protection history; verify the hash; restore the single file
TPM or Secure Boot shows a question markProgram ran without administrator rightsRun again and choose Yes at the UAC prompt
Results differ inside a virtual machineThe VM's virtual hardware is being checkedCheck the VM's TPM and Secure Boot settings, or run on the physical PC
A new CPU shows as unsupportedOld processor listConnect to the internet and run again, or use the latest release
Program refuses to start on an old systemSystem below the tool's minimum requirementsThe tool needs at least Windows 8.1 or Windows PE

Summary

Choose the build that matches your Windows, download it from a source that publishes hashes, verify the SHA-256, pass SmartScreen only after a match, and run the program with administrator rights.

Frequently asked questions

Is WhyNotWin11 safe to download?

The genuine release is open source and widely used. The safety question is really about getting the genuine file, which is why you compare the SHA-256 hash with the published value before running it.

Does WhyNotWin11 need an internet connection?

No. It works offline using the processor lists built into the file. When online, it downloads newer lists so recently released CPUs are recognised.

Will running WhyNotWin11 change my BIOS or settings?

No. It only reads information. Any changes to firmware, disks or drivers are things you do yourself afterwards, if you choose to.

Can I run it on Windows 11?

Yes. It runs on Windows 8.1, Windows 10, Windows 11 and Windows PE. On a Windows 11 PC it is useful for checking whether the machine meets the requirements for future feature updates.

What should I do after reading the results?

Note which lines are red. TPM, Secure Boot, boot method, partition type and graphics driver failures are often fixable with settings or updates. Processor failures are hardware limits that software cannot change.