Whynotwin11

WhyNotWin11 command line switches explained

Every switch in WhyNotWin11 2.7.0.0, read from its source code, with working examples for silent checks, skipped checks and exit codes.

  • Updated
  • Checked against WhyNotWin11 2.7.0.0
Feature image for the guide: WhyNotWin11 command line switches explained

Most people use WhyNotWin11 by double-clicking it and reading the results window. Behind that window is a complete command-line interface that lets you run checks silently, skip specific requirements, test another drive, export reports and update the program. For IT technicians and anyone checking more than one PC, these switches turn WhyNotWin11 into a scriptable inventory tool.

This guide documents every switch in WhyNotWin11 2.7.0.0. The list was read directly from the program's source code for that release, so it reflects exactly what the 2.7.0.0 build accepts.

How to run WhyNotWin11 from the command line

  1. Open Command Prompt or PowerShell.
  2. Change to the folder that contains the program, for example:
Change folder · Command Prompt
cd %USERPROFILE%\Downloads
  1. Run the program with one or more switches:
Example · Command Prompt
WhyNotWin11.exe /export TXT

In PowerShell, prefix the file name with .\ so PowerShell runs the program from the current folder:

Example in PowerShell · PowerShell
.\WhyNotWin11.exe /export TXT

The program still shows a User Account Control prompt, because it needs administrator rights to read the TPM and Secure Boot state.

The built-in help

Running WhyNotWin11.exe /? shows a help window with this syntax:

Syntax · Text
WhyNotWin11 [/drive DRIVE:] [/export FORMAT [FILENAME]] [/extras DATA] [/force] [/fuonly] [/silent] [/skip CHECK] [/update [BUILD]]

/h and /help show the same window.

All switches at a glance

SwitchShort formWhat it does
/drive DRIVE:/dRuns the disk checks against another drive letter
/export FORMAT [FILENAME]/e, /formatSaves results as CSV, TSV or TXT
/extras DATA/exAdds extra columns to an export
/force/fIgnores the program's own system requirements
/fuonly/fuChecks Windows 11 feature-update compatibility only
/silent/sRuns without the window and reports through the exit code
/skip CHECK/scSkips a comma-separated list of checks
/update [release or dev]/uDownloads the latest release or development build
/?/h, /helpShows the help window

/drive — check another disk

By default WhyNotWin11 checks the drive Windows is running from. /drive points the disk checks at a different drive letter, which is useful in Windows PE or when a second disk will become the system disk.

Drive · Command Prompt
WhyNotWin11.exe /drive D:

The value must be a drive letter followed by a colon. Anything else causes an "Invalid" message and exit code 87.

/export — save results to a file

/export writes the results to a file in one of three formats.

FormatBest for
CSVSpreadsheets and inventory tools
TSVSpreadsheets, avoiding problems with commas in values
TXTReading, printing or attaching to a support ticket

File naming rules

  • No file name: the report is named after the computer, such as DESKTOP-01.CSV, in the current folder.
  • A file name: the report is saved under that name.
  • A folder: the report is saved in that folder and named after the computer.
Export examples · Command Prompt
WhyNotWin11.exe /export CSV
WhyNotWin11.exe /export TXT C:\Reports\office-pc.txt
WhyNotWin11.exe /export CSV C:\Reports\

/export works with or without /silent. Without /silent, you get both the window and the file.

/extras — add columns to an export

/extras adds information to the exported report. Give one or more values separated by commas, without spaces.

ValueAdds
BUILDWindows build number
KEYBOARDKeyboard layout
LANGUAGEOperating system language
MUIDisplay language
OSOperating system version
USERSigned-in user name
Extras · Command Prompt
WhyNotWin11.exe /silent /export CSV C:\Reports\ /extras BUILD,OS,USER

Remember that USER adds account names to the file. Store and share such reports carefully.

/silent — run without the window

/silent runs all checks without showing the results window. The answer is returned as the program's exit code:

  • 0 means the computer is compatible.
  • A non-zero code means at least one requirement was not met.
  • 87 means a switch or value was typed incorrectly.

Reading the exit code in PowerShell

Exit code · PowerShell
(Start-Process .\WhyNotWin11.exe -ArgumentList '/silent' -PassThru -Wait).ExitCode

Reading the exit code in Command Prompt

Exit code · Command Prompt
start /wait WhyNotWin11.exe /silent
echo %errorlevel%

Combine /silent with /export when you need to know which checks failed, not just whether the PC is compatible.

/skip — leave out specific checks

/skip removes checks from the run. Use the exact names below, separated by commas without spaces.

NameSkips
ArchArchitecture
BootBoot method
CPUCPU compatibility, core count and frequency
CPUCompatCPU compatibility only
CPUCoresCPU core count only
CPUFreqCPU frequency only
DirectXDirectX 12 and WDDM 2
DiskDisk partition type
RAMRAM
SecureBootSecure Boot
StorageStorage
TPMTPM version
ConfigBoot method, partition type and Secure Boot
HardwareArchitecture, CPU checks, DirectX and RAM
Skip · Command Prompt
WhyNotWin11.exe /skip TPM,SecureBoot

Skipped checks show "Check Skipped" in the results. Skipping a check hides it from the report; it does not change whether Windows Update considers the PC eligible.

/fuonly — feature-update compatibility

On a PC that already runs Windows 11, the hardware checks are less interesting than whether the next feature update will install. /fuonly reads Windows' own feature-update compatibility indicators, which Windows stores in the registry under its upgrade experience indicators, instead of running the hardware tests.

Feature update only · Command Prompt
WhyNotWin11.exe /fuonly

When you open WhyNotWin11 on a Windows 11 PC, it also offers to switch to this mode.

/force — ignore the tool's own requirements

WhyNotWin11 itself needs at least Windows 8.1 or Windows PE. /force tells it to run on systems it does not support.

Force · Command Prompt
WhyNotWin11.exe /force

The developer states that no support is given for /force. Use it only in lab or Windows PE situations where you understand the limits.

/update — download a newer build

CommandResult
WhyNotWin11.exe /updateDownloads the latest stable release as WhyNotWin11_Latest.exe in the same folder
WhyNotWin11.exe /update releaseSame as above
WhyNotWin11.exe /update devDownloads the latest development build as WhyNotWin11_dev.zip

Development builds are unstable and must be updated by hand. Verify the SHA-256 of any new file before running it.

Practical recipes

Quick compatibility answer for a script

Compatible? · PowerShell
$code = (Start-Process .\WhyNotWin11.exe -ArgumentList '/silent' -PassThru -Wait).ExitCode
if ($code -eq 0) { 'Compatible' } else { "Not compatible (exit code $code)" }

Collect reports from many PCs on a share

Network share · Command Prompt
\\server\tools\WhyNotWin11.exe /silent /export CSV \\server\share\win11\ /extras BUILD,OS

Each PC writes its own file named after the computer, so reports never overwrite each other.

Check a disk in Windows PE before installing Windows

Windows PE · Command Prompt
X:\Tools\WhyNotWin11_x86.exe /drive C: /export TXT X:\Tools\

Use the x86 build on 32-bit Windows PE.

Group Policy settings

Administrators can also control the program's interface through registry policy values under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Robert Maehl Software\WhyNotWin11. The 2.7.0.0 source reads values including NoUpdate, NoSocials, NoSettings, NoProgress, NoAppName, SetAppName and ForcedMUI. These change what the window shows; they do not change the checks.

Exit codes at a glance

Exit codeMeaning
0Run completed; in silent mode, the PC is compatible
87Invalid parameter — a switch is missing its value or the value is not recognised
Other non-zeroIn silent mode, at least one requirement was not met

Scripts should treat 0 as "compatible", 87 as "fix the command" and anything else as "not compatible — read the export for details".

Writing a simple batch script

A small batch file makes it easy for colleagues to run the same check the same way every time.

check-win11.cmd · Batch
@echo off
set REPORTS=\\server\share\win11
"%~dp0WhyNotWin11.exe" /silent /export CSV %REPORTS%\ /extras BUILD,OS
if %errorlevel%==0 (
  echo This PC meets the Windows 11 requirements.
) else if %errorlevel%==87 (
  echo The command was typed incorrectly.
) else (
  echo This PC does not meet every requirement. See the report in %REPORTS%.
)
pause

Place the batch file next to WhyNotWin11.exe. %~dp0 refers to the folder the batch file is in, so the script works from a USB stick or a network share.

Writing a PowerShell wrapper

PowerShell makes it easy to add the result to a log:

Check-Win11.ps1 · PowerShell
$exe  = Join-Path $PSScriptRoot 'WhyNotWin11.exe'
$code = (Start-Process $exe -ArgumentList '/silent','/export','CSV',"$env:TEMP\" -PassThru -Wait).ExitCode
$line = "{0:yyyy-MM-dd HH:mm}  {1}  exit {2}" -f (Get-Date), $env:COMPUTERNAME, $code
Add-Content -Path "$env:TEMP\win11-checks.log" -Value $line

Run the script from an administrator PowerShell session so the TPM and Secure Boot values are complete.

Common mistakes

  • Putting a space in a /skip list. Use TPM,SecureBoot, not TPM, SecureBoot.
  • Misspelling a check name. Names such as SecureBoot and CPUCompat must match exactly, otherwise the program stops with exit code 87.
  • Forgetting the format after /export. /export needs CSV, TSV or TXT.
  • Expecting /skip to make a PC eligible. It only changes the report.
  • Running without elevation in scripts. Without administrator rights, some checks cannot read their data.
  • Using an old build. Older versions accept fewer switches and carry older processor lists.

Running WhyNotWin11 from management tools

Many organisations already have a way to run commands on many PCs, such as Group Policy startup scripts, Configuration Manager, Intune or a remote monitoring tool. WhyNotWin11 fits into these well because it is a single file with predictable switches.

Points to plan

  • Where the file lives. Copy a verified WhyNotWin11.exe to each PC, or run it from a read-only network share that every computer can reach.
  • Which account runs it. Use the local system account or an administrator account, so the TPM and Secure Boot checks can read their data.
  • Where reports go. Point /export at a share where computer accounts can write, or at a local folder that your tool collects afterwards.
  • What counts as success. Use exit code 0 as "compatible", and keep the CSV reports for the details.
  • How often to run it. Once is usually enough for planning; run again after firmware changes or hardware upgrades.

A note on updates in managed environments

Administrators who distribute a specific version may prefer the program not to offer updates. The NoUpdate policy value hides the update prompt in the interface, while /update remains available for deliberate use.

Checking the version from the command line

To confirm which build you are scripting with, right-click the file, choose Properties and open the Details tab, or read the version in PowerShell:

File version · PowerShell
(Get-Item .\WhyNotWin11.exe).VersionInfo.FileVersion

For the current release this returns 2.7.0.0. Record the version in your inventory notes, because processor lists and switches can change between releases.

Frequently asked questions

Do switches need a particular order?

No. WhyNotWin11 reads switches one after another, so you can combine them in any order, as long as each switch is followed by its own value.

Why do I get exit code 87?

A switch is missing its value or has an invalid one — for example /export without a format, or a misspelled check name after /skip.

Can I run WhyNotWin11 silently without the UAC prompt?

Run it from an already elevated process, such as an administrator PowerShell window or a management tool running as system.

Are these switches the same in older versions?

Several of them date back to the 2.4 series, and newer ones were added later. This list matches 2.7.0.0; check /? on any other version.

Can I use lower-case and upper-case switches?

The examples in the program's help use lower-case switches and upper-case export formats. Use the same spelling as the help to avoid surprises.

Where does the report go if I give no folder?

Into the current working folder of the command, named after the computer.

Can I check several drives at once?

/drive takes one drive letter per run. Run the program again for each drive you want to test.

Can I combine /fuonly with /export?

Yes. WhyNotWin11.exe /fuonly /export TXT checks feature-update compatibility and saves the result, which is useful for keeping records on PCs that already run Windows 11. Combine it with /silent if you do not need the window.