Install WhyNotWin11 with winget and export results to CSV, TSV or TXT
Install and update WhyNotWin11 with Windows Package Manager, then collect readable reports from one PC or a whole office.

If you manage more than one Windows PC, downloading WhyNotWin11 by hand and reading each results window gets slow quickly. Two features make the job far easier: installing and updating WhyNotWin11 with Windows Package Manager (winget), and exporting results to CSV, TSV or TXT files that you can collect and compare in a spreadsheet.
This guide covers both, from a single home PC to a small office. It applies to WhyNotWin11 2.7.0.0 and the winget package rcmaehl.WhyNotWin11.
Part 1: Installing WhyNotWin11 with winget
What winget is
Windows Package Manager, usually called winget, is Microsoft's command-line tool for finding, installing and updating software. It is delivered with the App Installer component on current Windows 10 and Windows 11 systems. Each package in the catalogue has a manifest that points to the publisher's official download.
The WhyNotWin11 package ID is rcmaehl.WhyNotWin11. Its manifest points at the official GitHub release files: WhyNotWin11.exe for 64-bit systems and WhyNotWin11_x86.exe for 32-bit systems.
Check that winget is available
Open Command Prompt or PowerShell and run:
winget --versionIf Windows says the command is not recognised, update App Installer from the Microsoft Store and try again.
Look at the package before installing
winget show --id rcmaehl.WhyNotWin11 -eThis shows the version in the catalogue, the publisher, the licence and the download address. The -e (exact) flag makes sure winget matches only this package ID and not something with a similar name.
Install
winget install --id rcmaehl.WhyNotWin11 -ewinget downloads the file from the official release, checks it against the hash recorded in the manifest and installs it. If the catalogue lists more than one architecture, winget picks the one that matches your system. To force the 32-bit build:
winget install --id rcmaehl.WhyNotWin11 -e --architecture x86Confirm the installation
winget list --id rcmaehl.WhyNotWin11Update later
winget upgrade --id rcmaehl.WhyNotWin11 -eTo see every package with an available update on the PC:
winget upgradeRemove
winget uninstall --id rcmaehl.WhyNotWin11 -eThings to know about winget
- The catalogue is updated by pull requests, so a new WhyNotWin11 release can take a few days to appear.
- winget verifies the downloaded file against the SHA-256 in the manifest. A mismatch stops the installation.
- Corporate networks sometimes restrict winget through policy. Ask your administrator if commands are blocked.
Part 2: Exporting results
Why export
The results window is ideal for one PC. A file is better when you need to:
- keep a record before and after changing firmware settings;
- share results with a technician or helpdesk;
- compare a group of computers;
- plan which PCs can be upgraded and which need replacing.
The three formats
| Format | Separator | Best for |
|---|---|---|
| CSV | Comma | Spreadsheets and inventory tools |
| TSV | Tab | Spreadsheets when values contain commas |
| TXT | Plain text | Reading, printing, attaching to a ticket |
TSV support was added in version 2.6.1.1.
Export from a single PC
From the folder that contains WhyNotWin11:
WhyNotWin11.exe /export CSVThe results window opens as usual and the report is saved too. Without a file name, the report is named after the computer, such as DESKTOP-01.CSV.
Choose a name or folder
WhyNotWin11.exe /export TXT C:\Reports\before-changes.txtWhyNotWin11.exe /export CSV C:\Reports\When you give a folder, the file inside it is named after the computer.
Export without the window
WhyNotWin11.exe /silent /export CSV C:\Reports\The program runs all checks without showing a window, writes the report and returns an exit code: 0 for compatible, non-zero otherwise.
Add extra columns
/extras adds information to the export. Separate values with commas and no spaces.
| Value | Column added |
|---|---|
| BUILD | Windows build number |
| OS | Operating system version |
| LANGUAGE | Operating system language |
| MUI | Display language |
| KEYBOARD | Keyboard layout |
| USER | Signed-in user name |
WhyNotWin11.exe /silent /export CSV C:\Reports\ /extras BUILD,OSPart 3: Collecting reports from a group of PCs
Prepare a shared folder
- Create a folder on a server or NAS, for example \\server\share\win11.
- Give the computers or users write permission to it.
- Put a verified copy of WhyNotWin11 in a read-only tools share, or install it with winget on each PC.
Run the export on each PC
WhyNotWin11.exe /silent /export CSV \\server\share\win11\ /extras BUILD,OSUNC paths work for exports; a fix for UNC export paths was included in version 2.6.0.0. Each machine writes its own file, named after the computer, so reports do not overwrite each other.
Run it automatically
You can run the same command from a startup script, a scheduled task or a remote management tool. Run it with administrator or system rights, otherwise the TPM and Secure Boot values may be incomplete.
Combine the reports
- Open Excel or another spreadsheet program.
- Import the CSV files, or use a data import feature to combine all files in the folder.
- Add a filter to the header row.
- Sort by the checks that matter most, such as CPU Compatibility and TPM Version.
Turn the data into a plan
| Group | Typical pattern | Action |
|---|---|---|
| Ready | Every check passes | Schedule the Windows 11 upgrade |
| Settings | Only TPM, Secure Boot, Boot Method, Partition Type or graphics fail | Fix settings, re-export, then upgrade |
| Parts | RAM or Storage fail on upgradable PCs | Add memory or replace drives |
| Replace | CPU Compatibility fails | Plan replacement or Extended Security Updates |
Part 4: Before-and-after records
When you change firmware settings, export a report before and after:
WhyNotWin11.exe /export TXT C:\Reports\before.txtWhyNotWin11.exe /export TXT C:\Reports\after.txtComparing the two files shows exactly which lines changed, which is useful for documentation and for troubleshooting if something unexpected happens.
Privacy and housekeeping
- Exported reports contain the computer name and hardware details. With /extras USER they also contain account names.
- Store reports on a share with appropriate permissions.
- Delete reports you no longer need.
- Do not post full reports publicly if they include user or computer names from your organisation.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| winget not recognised | App Installer missing or outdated | Update App Installer from the Microsoft Store |
| winget finds several packages | Search was not exact | Use --id rcmaehl.WhyNotWin11 -e |
| Export file not created | No write permission to the folder | Choose a folder you can write to, or run as administrator |
| Exit code 87 | Missing or invalid switch value | Check the format name (CSV, TSV or TXT) and spelling |
| TPM or Secure Boot blank in reports | Run without elevation | Run with administrator or system rights |
Installing several tools at once with winget
If you prepare PCs regularly, winget can install a whole toolkit in one step. Create a list on a reference PC and import it on others.
Export a list of installed packages
winget export -o C:\Tools\toolkit.jsonInstall everything on another PC
winget import -i C:\Tools\toolkit.jsonEdit the JSON file to keep only the packages you want, including rcmaehl.WhyNotWin11. This is a quick way to give every technician the same set of tools.
Reading an exported CSV
Each row in the report describes one requirement and the value WhyNotWin11 found, alongside identifying information such as the computer name. When you add /extras, the extra columns appear in the same file.
Tips for spreadsheets
- Import the file as comma-separated (CSV) or tab-separated (TSV) data rather than opening it directly, so long values stay in single cells.
- Freeze the header row and add filters.
- Use conditional formatting to colour failed checks, but keep the text values visible so nobody relies on colour alone.
- Keep one sheet per inventory date so you can see progress over time.
Good habits for a small office
- Keep one verified copy of WhyNotWin11 on a read-only share, or install it on each PC with winget.
- Record the version used for each inventory. Processor lists change between releases.
- Run checks after changes. Re-export after enabling TPM or converting disks to confirm the fix.
- Separate personal data. Avoid /extras USER unless you need it.
- Clean up. Delete old reports once decisions have been made.
A worked example: a ten-PC office
Here is how a small office might use both features together.
- Prepare. On the administrator's PC, run winget install --id rcmaehl.WhyNotWin11 -e and confirm the version with winget list.
- Share. Copy the verified executable to \\server\tools\ with read-only permissions, and create \\server\share\win11\ for reports.
- Run. On each PC, run \\server\tools\WhyNotWin11.exe /silent /export CSV \\server\share\win11\ /extras BUILD,OS from an administrator prompt or a management tool.
- Review. Combine the ten CSV files in a spreadsheet and sort them into ready, settings, parts and replace groups.
- Fix. Enable TPM and Secure Boot or convert disks on the "settings" PCs during a planned maintenance window.
- Confirm. Run the same command again and compare the new reports with the first set.
- Upgrade. Upgrade the PCs that now pass, and budget for replacements.
This approach turns a scattered task into a short, documented project with a clear record of what changed on each machine.
Understanding winget's trust model
winget does not host software itself. Each package is described by a manifest in a public community repository that Microsoft moderates. The manifest records where the installer is downloaded from and its SHA-256 hash. When you install, winget downloads the file from that address and compares its hash with the manifest before running anything.
For WhyNotWin11 this means:
- the file comes from the official GitHub release, not from a third-party mirror;
- a tampered or replaced file would fail the hash comparison;
- new releases appear after a manifest update is submitted and accepted, which can take a few days.
winget also shows the licence and publisher information from the manifest, so winget show --id rcmaehl.WhyNotWin11 -e is a quick way to confirm what you are about to install.
Exporting before and after a Windows 11 upgrade
Exports are also useful after the upgrade itself. On a PC that already runs Windows 11, run:
WhyNotWin11.exe /fuonly /export TXTThis records whether Windows considers the PC ready for the next feature update. Keeping that report alongside the original inventory gives you a complete history for each machine.
Frequently asked questions
Is the winget version the same file as the GitHub release?
Yes. The manifest points to the official release files and records their hashes, which winget checks during installation.
Can I use winget and the downloaded file side by side?
Yes. They are the same program. Just make sure you know which copy you are running when you compare versions.
Which export format should I choose?
CSV for spreadsheets, TSV if values contain commas, and TXT when a person will read it.
Do exports work in Windows PE?
Yes. Write the file to a USB drive or a mapped network location, because the Windows PE drive is temporary.
Does winget need administrator rights?
Many packages can be installed per user, but WhyNotWin11 itself needs administrator rights when it runs. Use an administrator terminal if winget asks for elevation.
Can I schedule regular exports?
Yes. Create a scheduled task that runs WhyNotWin11 with /silent /export CSV and your folder, with highest privileges.
Why are some cells empty in my export?
The run did not have administrator rights, or a check was skipped. Re-run with elevation and without /skip.
Can I install a specific older version with winget?
winget lets you request a version with the --version option, if that version is still listed in the catalogue. For checking Windows 11 readiness, the newest version is almost always the right choice because it has the most current processor lists.