How to verify the WhyNotWin11 file: SHA-256, signature and SmartScreen
Prove that the file you downloaded is the developer's release, read its signature status correctly and handle security warnings without lowering your protection.

Before you run any tool that inspects your firmware and disks with administrator rights, you should be certain it is the file its developer published. With WhyNotWin11 this matters even more, because the program is popular, free and frequently re-uploaded by third-party download sites. Some of those copies are genuine; others are wrapped in installers or replaced by older builds.
This guide explains how to prove a WhyNotWin11 download is genuine using a SHA-256 hash, how to read its signature status correctly, what the Microsoft Defender SmartScreen warning really means, and how to deal with antivirus alerts without lowering your protection. Every value below applies to WhyNotWin11 2.7.0.0.
Why file verification matters
A downloaded program can differ from the developer's release for several reasons:
- Tampering — someone has added unwanted or malicious code.
- Repackaging — a download site has wrapped the file in its own installer with extra offers.
- Corruption — the download was interrupted or damaged.
- Wrong version — the site still offers an old build under a new name.
Visual checks such as the program icon or file name cannot catch any of these. A cryptographic hash can.
What a SHA-256 hash is
SHA-256 is a hashing algorithm that turns any file into a 64-character string of letters and numbers. It has two properties that make it ideal for verification:
- Deterministic — the same file always produces the same hash, on any computer.
- Sensitive — changing a single byte of the file produces a completely different hash.
When a trustworthy source publishes the SHA-256 of a file, you can calculate the hash of your copy and compare. A perfect match means your file is byte-for-byte identical to the one the source checked.
The published values for WhyNotWin11 2.7.0.0
| File | Architecture | Size | SHA-256 |
|---|---|---|---|
| WhyNotWin11.exe | 64-bit (x64) | 2,329,088 bytes | 433bca5da906c35029a7cdf55f0739553602649f58acd2b9cdebafdeaba23edb |
| WhyNotWin11_x86.exe | 32-bit (x86) | 2,206,208 bytes | fadced08bac46a94b6556a5eda522b2bd60d90a143e282ca80d6741be9765d25 |
These hashes were calculated from the official GitHub release files of tag 2.7.0 and from the copies hosted on whynotwin11.app; both sets matched.
Method 1: PowerShell Get-FileHash
PowerShell has a built-in command for hashing files. It is the clearest method for most people.
Steps
- Open File Explorer and go to the folder that contains the download, usually Downloads.
- Click the address bar, type powershell and press Enter.
- Run the command for your build:
Get-FileHash .\WhyNotWin11.exe -Algorithm SHA256 | Format-ListGet-FileHash .\WhyNotWin11_x86.exe -Algorithm SHA256 | Format-List- Look at the line labelled Hash.
Compare automatically
Comparing 64 characters by eye is error-prone. Let PowerShell do it:
(Get-FileHash .\WhyNotWin11.exe -Algorithm SHA256).Hash -eq '433bca5da906c35029a7cdf55f0739553602649f58acd2b9cdebafdeaba23edb'The result is True when the file matches and False when it does not. The comparison is not case-sensitive, so capital letters in PowerShell's output do not matter.
Method 2: Command Prompt certutil
If you prefer Command Prompt, the built-in certutil tool calculates hashes too.
certutil -hashfile WhyNotWin11.exe SHA256certutil prints the hash on its own line. Compare it with the published value in the same way. Both tools produce the same hash for the same file.
Method 3: File Explorer and third-party tools
Some file managers and archive tools can show hashes from a right-click menu. They work, but they add another program you need to trust. The two built-in methods above are enough for almost everyone.
Reading the signature status correctly
Many Windows programs carry an Authenticode digital signature that names the publisher and proves the file has not changed since it was signed. You can see it in the file's properties.
Check in File Explorer
- Right-click the file and choose Properties.
- Look for a tab called Digital Signatures.
If the tab is present, it lists the signer and lets you view the certificate. WhyNotWin11 2.7.0.0 does not show this tab, because the release is not code-signed.
Check in PowerShell
Get-AuthenticodeSignature .\WhyNotWin11.exe | Format-List Status, StatusMessageFor this release the expected status is NotSigned.
What "not signed" does and does not mean
- It does mean Windows cannot confirm the publisher automatically.
- It does mean SmartScreen and some antivirus products are more cautious.
- It does not mean the file is malicious. Many open-source tools are unsigned because certificates cost money and require yearly renewal.
- It does mean the SHA-256 comparison is your main proof that the file is genuine.
Understanding the SmartScreen warning
Microsoft Defender SmartScreen checks programs you download against a reputation service. When a file is unsigned and has not been seen by many users, SmartScreen shows a blue window titled "Windows protected your PC".
What the message really says
SmartScreen is telling you it does not know the file well enough to vouch for it. It is not reporting a detected virus. A file that SmartScreen recognises as malicious is blocked with a different, stronger message.
The safe way through
- Verify the SHA-256 first. Do not skip this step.
- In the SmartScreen window, select More info.
- Confirm the app name is WhyNotWin11.exe (or the x86 file name) and the publisher shows as unknown.
- Select Run anyway.
If the hash does not match, choose Don't run and delete the file.
What not to do
- Do not disable SmartScreen in Windows Security.
- Do not turn off "Check apps and files" permanently.
- Do not run a file you have not verified just because a forum suggests it is safe.
Handling antivirus detections
Heuristic scanners look for suspicious behaviour patterns rather than known malware. Small, unsigned AutoIt programs that read system information sometimes trigger them. Third-party packages of WhyNotWin11 have also been flagged in the past and later revised by their packagers.
Step-by-step
- Open Windows Security.
- Go to Virus & threat protection.
- Select Protection history.
- Open the WhyNotWin11 entry and note the threat name and the affected file path.
- If you verified the original file's hash and it matched, choose Actions and then Restore.
- If the program keeps being removed, add an exclusion for that single file only — not for the whole Downloads folder.
When to stop
If the detection name refers to a specific known malware family rather than a generic heuristic, or if your file's hash does not match, do not restore it. Download again from a trustworthy source and compare the hash.
Verification checklist
Use this short list every time you download a new version:
- The file name matches exactly: WhyNotWin11.exe or WhyNotWin11_x86.exe.
- The file size matches the published size.
- The SHA-256 matches the published hash, checked with PowerShell or certutil.
- The file is a single .exe, not an installer or a ZIP from an unknown source.
- The signature status is what you expect for that version.
- Only after all of the above, run it and accept the UAC prompt.
Verifying future releases
When a new version of WhyNotWin11 appears, the hashes above no longer apply. For a new release:
- Download the files from the official rcmaehl/WhyNotWin11 Releases page.
- Calculate their hashes.
- Compare with a second, independent source that publishes hashes for that version.
- Check the signature status again — future releases may be signed.
The GitHub Releases page shows file names and sizes, but historically has not listed SHA-256 values for WhyNotWin11. That is why an independent site that calculates and publishes them is useful.
Checking the hash on another computer
You may download WhyNotWin11 on one machine and carry it to another on a USB stick, or download it on a Mac or Linux PC for a technician's toolkit. The hash is the same on every operating system.
On macOS
Open Terminal in the folder with the file and run:
shasum -a 256 WhyNotWin11.exeOn Linux
Most distributions include the sha256sum tool:
sha256sum WhyNotWin11.exeAfter copying to a USB stick
Copying a file does not change its contents, so the hash stays the same. If you want to be thorough, calculate it again on the target PC before the first run. A different hash after copying points to a faulty USB stick or an incomplete copy.
Common mistakes when comparing hashes
Hash checks are simple, but a few mistakes come up again and again.
- Comparing the wrong file. Browsers sometimes save a second download as WhyNotWin11 (1).exe. Make sure you hash the file you intend to run.
- Comparing with the wrong version. The values on this page apply to 2.7.0.0 only. A newer or older release has different hashes.
- Mixing up the builds. The x64 and x86 files have different hashes. Compare each file with its own value.
- Checking only the first few characters. Two different files can share a short prefix. Compare the full 64 characters, or use the automatic PowerShell comparison.
- Trusting a hash from the same page as a suspicious download. A hash only proves something when it comes from a source you trust. If a site you do not trust offers both the file and the hash, a matching result proves very little.
Signed and unsigned software, explained
Code signing uses a certificate issued to a developer or company. When a program is signed, Windows can show the publisher's name and detect any change made after signing. Large software companies sign almost everything they publish.
Independent open-source developers often do not. Certificates cost money, must be renewed regularly and require identity checks. Many respected tools are distributed unsigned for these reasons, and their users rely on published hashes and public source code instead.
For WhyNotWin11 2.7.0.0 the situation is clear:
| Question | Answer for 2.7.0.0 |
|---|---|
| Is the file code-signed? | No |
| Is the source code public? | Yes, under LGPL-3.0 |
| Is a SHA-256 published for each build? | Yes, on this site |
| Does SmartScreen warn? | It may, because the file is unsigned and less common |
If a future release is signed, the Digital Signatures tab will name the signer. Check that the name is what you expect before trusting the signature.
Keeping a verified copy
Once you have a verified file, keep it. A verified copy on a USB stick or a read-only network share saves you from downloading and checking again every time you need the tool.
- Store the file together with a small text note of its version and SHA-256.
- Recalculate the hash occasionally, especially if the USB stick is old or has been used on many PCs.
- Replace the copy when a new release appears, and verify the new file in the same way.
- Do not rename the file to something generic; keeping WhyNotWin11.exe makes it obvious what it is.
For teams, a shared verified copy also means everyone runs the same version, so results from different PCs can be compared fairly.
Summary
Calculate the SHA-256 with PowerShell or certutil, compare it in full with a trusted published value, and expect version 2.7.0.0 to be unsigned. Only after a match should you use More info and Run anyway in SmartScreen, or restore a single quarantined file. Never lower your protection globally.
Frequently asked questions
Is SHA-256 better than MD5 or SHA-1?
Yes. MD5 and SHA-1 are older algorithms with known weaknesses. SHA-256 is the standard choice for verifying downloads today.
My hash is in capital letters and the published one is in small letters. Is that a problem?
No. Hashes are hexadecimal numbers, and letter case does not change their value.
Can a fake file have the same SHA-256?
Producing a different file with the same SHA-256 is not practically possible with current technology. A match is strong evidence the files are identical.
Why does a genuine tool trigger security warnings?
Because it is unsigned and less common than mainstream software. Reputation systems are cautious with unknown files, which is reasonable. Your hash check fills that gap.
Do I need to verify the file every time I run it?
No. Verify once after downloading. If the file stays on your PC or USB stick unchanged, the result still applies.
Does winget verify the file for me?
Yes. When you install WhyNotWin11 with winget, it compares the downloaded file with the SHA-256 recorded in the package manifest and stops if they differ. That gives you the same kind of protection as a manual hash check.