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.

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
- Open Command Prompt or PowerShell.
- Change to the folder that contains the program, for example:
cd %USERPROFILE%\Downloads- Run the program with one or more switches:
WhyNotWin11.exe /export TXTIn PowerShell, prefix the file name with .\ so PowerShell runs the program from the current folder:
.\WhyNotWin11.exe /export TXTThe 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:
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
| Switch | Short form | What it does |
|---|---|---|
| /drive DRIVE: | /d | Runs the disk checks against another drive letter |
| /export FORMAT [FILENAME] | /e, /format | Saves results as CSV, TSV or TXT |
| /extras DATA | /ex | Adds extra columns to an export |
| /force | /f | Ignores the program's own system requirements |
| /fuonly | /fu | Checks Windows 11 feature-update compatibility only |
| /silent | /s | Runs without the window and reports through the exit code |
| /skip CHECK | /sc | Skips a comma-separated list of checks |
| /update [release or dev] | /u | Downloads the latest release or development build |
| /? | /h, /help | Shows 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.
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.
| Format | Best for |
|---|---|
| CSV | Spreadsheets and inventory tools |
| TSV | Spreadsheets, avoiding problems with commas in values |
| TXT | Reading, 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.
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.
| Value | Adds |
|---|---|
| BUILD | Windows build number |
| KEYBOARD | Keyboard layout |
| LANGUAGE | Operating system language |
| MUI | Display language |
| OS | Operating system version |
| USER | Signed-in user name |
WhyNotWin11.exe /silent /export CSV C:\Reports\ /extras BUILD,OS,USERRemember 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
(Start-Process .\WhyNotWin11.exe -ArgumentList '/silent' -PassThru -Wait).ExitCodeReading the exit code in 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.
| Name | Skips |
|---|---|
| Arch | Architecture |
| Boot | Boot method |
| CPU | CPU compatibility, core count and frequency |
| CPUCompat | CPU compatibility only |
| CPUCores | CPU core count only |
| CPUFreq | CPU frequency only |
| DirectX | DirectX 12 and WDDM 2 |
| Disk | Disk partition type |
| RAM | RAM |
| SecureBoot | Secure Boot |
| Storage | Storage |
| TPM | TPM version |
| Config | Boot method, partition type and Secure Boot |
| Hardware | Architecture, CPU checks, DirectX and RAM |
WhyNotWin11.exe /skip TPM,SecureBootSkipped 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.
WhyNotWin11.exe /fuonlyWhen 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.
WhyNotWin11.exe /forceThe 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
| Command | Result |
|---|---|
| WhyNotWin11.exe /update | Downloads the latest stable release as WhyNotWin11_Latest.exe in the same folder |
| WhyNotWin11.exe /update release | Same as above |
| WhyNotWin11.exe /update dev | Downloads 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
$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
\\server\tools\WhyNotWin11.exe /silent /export CSV \\server\share\win11\ /extras BUILD,OSEach PC writes its own file named after the computer, so reports never overwrite each other.
Check a disk in Windows PE before installing Windows
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 code | Meaning |
|---|---|
| 0 | Run completed; in silent mode, the PC is compatible |
| 87 | Invalid parameter — a switch is missing its value or the value is not recognised |
| Other non-zero | In 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.
@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%.
)
pausePlace 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:
$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 $lineRun 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:
(Get-Item .\WhyNotWin11.exe).VersionInfo.FileVersionFor 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.