My PC fails DX12 test, even though my GPU supports feature level 12_1 (according to GPU-Z). I'm currently using Windows 8.1, which does not support DX12.

So I decided to see how the app would react when installed on Insider Build 21390 x86 and while all other detections are fine. The CPU reports as 4-bit

when i ran your latest version it gave all green checks except ram(0gb)

My CPU is being detected as 800MHz, which is it's minimum frequency with power saving:

This might be related to Hyper-V being enabled.

Hi, word correction, it's "compatibility"

WDDM2 is not detected on my R9 290, but DXDIAG say that i've WDDM 2.7

This is probably out of scope, I have 9933MB of RAM at my disposal.
It probably also includes swap, because it would be 18125 for me.
So it is possibly related to #6, I guess?

Microsoft removed soft-floor/hard-floor requirements and just made it on, saying only tpm >=2.0 is allowed.
Reference: https://docs.microsoft.com/en-us/windows/compatibility/windows-11/

Fix Discord reported issue of Get-Disk Failing
See attached
message.txt

Windows 11 requires Secure Boot be available, not enabled:

Both screenshots taken on the same machine obviously

This program does not appear to have the ability to check CPU specs, and it shows all CPUs as ?

• Add social buttons for PayPal GitHub and more
• Add note for hiring
• Fully implement high contrast (#4)
• (#29)
• (#32)
• Add command line switches for IT admins (#106)
• (#50)
• (#70)
• (#195)

I have 4 GB RAM but since it reports the compatibility based on usable RAM, it is showing not compatible. Please adjust it to show compatibility based on installed RAM.

Version 2.1.0 provides the wrong type of partition information (gpt cannot be detected), while the previous version correctly detected gpt support, as well as the diskpart list list disk command line.

The check should be able to handle TPMs under version 2.0, however the WMI call may return odd data that will need to be investigated

Something's not quite right in the way it's being detected at the moment, I just ran the app in a clearly unsupported machine, but that requirement was regarded as passed:

The title and text for the things present in the system is pixelated by the way, was it intentional?

And being pedantic here but...

• If the boot type is legacy, Secure Boot can't be enabled or disabled, that category should read "Incompatible" maybe.
• Same for TPM, rather than not activated it'd be better if it read "TPM not detected, disabled/not present"
• What's with the PascalCase all around 😜

I know you've already got an item for Supported CPUs on your to-do list, but in case you haven't found it already here is the official list from Microsoft: https://docs.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements

Thanks for your nice tool btw!

The tool shows that I don't have WDDM2 on this PC and Windows 11 is not supported on my PC, which is not true, because I have WDDM3 in the newest Insider Dev build (21390) which is newer than WDDM2, please add WDDM3 check too in the tool!
Thank you!

Not a huge issue for me but people using higher scaling than me for higher res monitors are likely going to have issues with the UI being a set size and not adjusting to scaling. [This is what it looks like at 120%]https://i.imgur.com/3oAViaV.png(url)

If WhyNotWin11 shows the TPM status "TPM Not Activated", does this mean that there actually is one that can be activated? I checked my BIOS but can find an option to activate a TPM.

I have the red X for Directx/WDDM2 but a good machine.

Using dxdiag (which might be good to link to on your app for others) I was able to confirm that I am in fact running on Direct X 12 but only WDDM1.2

If these could be seperated it might mean more when 'soft' requirments are better understood.

Finally a key to the errors or a tool tip for each might help others less techy.

Good work though.

T

This software is good but it only works on x86 processors. Even though it can run on WOA because of the compatibility layer, it can't provide comprehensive information. The WOA ecosystem is growing, so native ARM64 version may be needed.

The supported Qualcomm processors are shown below.

https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-qualcomm-processors

I got Surface Go 2 with Pentium Gold 4425Y.
This CPU is quite strange - it's listed in Windows 11 list as supported, but it's actually 7th gen Pentium Kaby Lake CPU.
WhyNotWin11 app 2.2.0.0 reports for this CPU "?" on the CPU generation line, I guess this can be fixed?

This app shows a fail on Secure Boot - the Windows 11 system requirements say that the computer just has to be Secure Boot-capable (not that it has to be on, it just has to have the support for it).

Additionally, Microsoft's tool says my computer is Windows 11-compatible despite Secure Boot being disabled.

I have TPM 2.0 and its enabled and Secure boot is enabled and the PC is plenty fast enough but the windows upgrade tool says no, you must buy a new pc. Its like windows 95 all over again!

I believe the 3.9 RAM is fine, but the tool doesnt agree.

A summary table would be great to show what's possible:

*) Red=no; yellow=minimum requirements; green=full ready
**) red=x32 OS; green=x64 OS (and Win11 ready/min. requirements)
***) Red=Not Win11 ready; Green=Win11 ready/min. requirements

Hello,
I am currently running the latest dev insider preview build of Windows 10, which includes support for WDDM 3 which is also what my GPU driver supports. The tool checks only for WDDM 2 and not above. This is a rather niche issue though but I thought I'd mention it regardless. An example of the output I receive is attached although it is the output you would expect. Thank you for making this tool!

The CPU Compatibility list is coming from the Systems Integrator page, not an actual requirement for Windows 11 support. See the same page for Windows 10 - https://docs.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements Notice how there's a lot of missing CPUs that install Windows 10 just fine? Don't equate Systems Integrator requirements with OS requirements. These are ONLY to receive the "Windows Genuine Badge" for systems integrators - https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors

Ok, this is getting crazy now...story is changing constantly from MS camp. Best to wait?

While checks are running the update and close button aren't working.

We should compile for x86 instead of x64. Otherwise architecture checks makes no sense and user can't get ifo that x86 system are not compatible for direct upgrade.

Hello,

Great tool. But it seems you're missing the gpedit.msc check. Because the only thing I can remember is having modified one single setting in gpedit.msc for my VPN to work correctly. 🙃

I think that the CI is pretty bad, I have been working a bit on improving it but I don't know Windows/Powershell that much and I hope that due to this project's popularity someone who knows better will see it.
So couple of points I think are worth improving:

• Use more (GitHub provided) variables so the CI is more flexible (example ${{ github.repository }} which is used now)

• Change manual git clone to actions/checkout (it's pretty easy, but for some reason not always as reliable)

• Change manual autoit download+install to use some package manager (or just a faster/better/more elegant way, I tried chocolatey and it worked but was very slow, scoop worked much better, but with pretty small size of autoit tools and the fact that first you need to get scoop itself I don't know if it brings any time benefits)
  ^ Caching is used now

• Remove the ugly (in my opinion) need for Start-Sleep -s 10. This is "because it returns back to shell before it completes". and by "it" I mean the autoit compiler/tools. I tried different methods, for example loop that checks if file exists but it either hanged the GitHub runner or was really slow (and still needed wait command anyway). Again, I might be missing something obvious here.

• Print hash of produced binary (and then use it in release)

• Automatically upload artifacts on release.

WDDM 3.0 shown as incompatible

FYI -- The most recent artifact of WhyNotWin11_x86.exe is flagged as a virus (Program:Win32/Wacapew.C!ml) by Microsoft/Windows Defender.

https://www.virustotal.com/gui/file/d93b3da670d96e80d2a3ec0bbea61f7b33b974604a723f3791b515204cc41337/detection

More info on autoit forums
https://www.autoitscript.com/forum/topic/34658-are-my-autoit-exes-really-infected/

Can you check the requirement for display?
As well the check on processor has a "?": Microsoft has obviously been hacked internally by Microsoft China, that silently modified the CPU support for ALL existing supported versions of Windows (7, 8, 8.1, 10, Home/Pro/Server/Enterprise/IOT...)
The Microsoft eligibility program was made by Microsoft China, using rules applicable only to PR China for the specific versions of Windows distributed in PR China (with many restrictions and differences).
Win 11 alpha tests have been made only internally by MS China, (including the leaked version that appeared on their site for some Chinese manufacturers): this version was evidently made only to test the program for manufacturers of new products. This should have had NO consequences on the existing contracted licences for the rest of the world.

Windows 11 eligibility has simply NEVER been tested by Microsoft for use by any one else than Chinese manufacturers for new PCs. But pushing that version is simply an abuse, because it has also silently dropped the support for all existing versions.

Microsoft must restore their support pages for Win7/8/8.1/10 (and related server/IOT versions) and clearly state that Win11 is still NOT ready and will not be available at fall outside the PR China market with their specific licences.

And Microsoft must drop their trust in their PR-Chinese subsidiary, clearly under influence of the PR China government, jsut interested to boost their sales (as if they needed it! There's not even enough supply to satisfy the demand on CPUs, RAMs, Graphics cards, SSD for billions new PCs that Microsoft want to waste with its current plan).

Windows 11 is simply not ready, it has NEVER been tested for deployment outside Chinese manufacturers or designers for new PCs. Microsoft has to admit it, and restore the existing support that has been maliciously and severey hacked by MS China!

But now Microsoft is lying and this LIE must end very fast, before it causes massive damages. All worldwide deployment plans have to be cancelled. They are FAKE.

I downloaded the exe file from the releases file and ran it. Nothing happened by the File Explorer stopped responding.

I restarted Windows Explorer and tried this several times. Same thing happens. Anyone else experiencing this?

I'm running dev channel
Edition Windows 10 Pro
Version Dev
Installed on ‎5/‎7/‎2021
OS build 21376.1
Experience Windows 10 Feature Experience Pack 321.11803.0.3

As in the image states that UEFI/Secure Boot capable I have it enabed but from some reason Windows reports it as off

Please provide compiled releases for people who can't compile it.

This check should look on the OS Architecture. An x86 OS running on x64 can't be upgraded. Only a new installation is possible in this case.

Thank you for the utility, but can you try and address https://www.virustotal.com/gui/ issues please?

Whats the reason behind the weird window settings?

I just quickly changed

$hGUI = GUICreate("WhyNotWin11", 800, 600, -1, -1)
;GUISetBkColor(0xF8F8F8)

Now the window can be dragged, minimized and closed normally and there isn't this weird line at the bottom anymore.

;$hExit = GUICtrlCreateLabel("X", 760, 10, 30, 30, $SS_CENTER+$SS_CENTERIMAGE)
;GUICtrlSetFont(-1, 24, 400)

Can be removed

I have three drives and all have a "Partition style" of "GUID Partition Table (GPT)" as reported by the Windows 10 Disc Management Tool. WhyNotWin11 v 2.1.0.0 still shows "GPT Not Detected" in the Disc Partitioning category with a failed status.

Example of the drive properties as reported by the Windows 10 Disc Management Tool. All other drives have the same entry there.

WhyNotWin11 report:

Running the latest 471.11 (June 22, 2021) drivers and Windows 10 build 21390 (May 26, 2021 dev channel).

Any ideas?

Check C:\ but also check other partitions and drives and report how many have enough space.