Introducing Windows 11

John Pombrio said:

When I tried to download the Github win 11 checker, Chrome gave me this "Unconfirmed 715703.crdownload" instead of the actual file name of "WhyNotWin11.exe" because Chrome will not allow you to download and .exe file. Just change the name and extension and it works fine.
Release 2.0.1 - Day 1 Patch . rcmaehl/WhyNotWin11 . GitHub

When I used Edge (DEV build) I had to give permission for it to download.

On my old PowerSpec desktop I checked in Device Manager and found I had no security devices listed. I checked in the Bios and found that I could turn on the Intel firmware TPM. I also saw that Secure Boot was enabled. Tonight when I ran WhyNotWin 11 it showed Secure Boot was disabled. When I went back into the Bios I saw that Secure Boot was listed as Enabled. I also saw a setting for the OS and it was set to Other OS. I clicked on it and I had a option for Windows UEFI mode. I selected it and saved the change. Now WhyNotWin 11 shows Secure Boot enabled. It also shows in DirectX support as Not DirectX 12. When I run dxdiag it shows DirectX 12. I guess I'll just have to wait for the official release to see if I can install Windows 11 on it.

Maybe it has already been said in other posts of this thread — did not read the whole thread — but it seems for some PCs, if TPM is enabled in BIOS settings, that could make your PC pass the "PC Health Check" even though it did not before. And that goes whether it is TPM 2.0 (the recommended one) or TPM 1.2.

I will certainly later on give it a try on my production machine which did not pass the test.

2.1.0 - More checks

(released this 3 hours ago)

Releases · rcmaehl/WhyNotWin11 · GitHub

I just installed and ran PC Health Check on my old PowerSpec and got the This PC can Run Windows 11. I'm not sure why WhyNotWin 11 gave me a DirectX 12 error. Tomorrow or Sunday I'll check my Acer Spin laptop with WhyNotWin 11 and see what it finds.

John Pombrio said:

Only a few server-type mobos have a TPM chip installed on them which the corporations use for company-wide security. Most consumer boards do not. Instead, Intel and AMD have implemented TPM onto their CPUs in their firmware. Discrete is for a mobo's TPM header and a TPM module, firmware means onboard the CPU. In any case, according to MS, all three options (dongle, mobo chip, and CPU) for TPM acts in exactly the same way for Windows.

Making any kind of TPM implementation mandatory because of Windows Hello and Bitlocker is ridiculous, unless using those is also mandatory. My Z170 motherboard has a TPM header, but it's unlikely it has firmware support for it. The manual printed in 2016 makes no mention of Intel PTT, but it is running the latest (and last) BIOS. I may look for it in the UEFI at some point, but it's not running in a strict UEFI mode even though secure boot is enabled. That may hide PTT settings.

Support for local accounts is also doubtful, for Home edition anyway.

Ghot said:

What is the make and model of your motherboard?


Here are the links for the Win 11 compatibility checkers...

Microsoft: https://aka.ms/GetPCHealthCheckApp

GitHub: Releases . rcmaehl/WhyNotWin11 . GitHub

I've purposefully left out all hardware details for privacy's sake, and in this case the exact model is irrelevant. It's an ASUS, and ASUS had a patchy history of software level TPM support, it's completely random and the original price range of the board makes no difference. Microsoft may back down on the requirement, or maybe there will be a workaround, but Windows 11 has plenty other perplexing design choices that make Linux all the more tempting.

We've been running this sh*t OS on sh*t hardware for decades!!! Why all of a sudden the stringent requirements?!?!?!

MS is becoming so fecking anal about security!!!