CPU Compatibility List Discussion

[seiggy]

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?

[ghost]

Was going to reply in #83 - will put it here instead:

I agree it would be useful to have links to the requirements within WhyNotWin11.

Note that these links should be culture sensitive.

I think if you strip out the culture code their website takes care of it, so it would be: Requirements: https://www.microsoft.com/windows/windows-11-specifications Intel: https://docs.microsoft.com/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors AMD: https://docs.microsoft.com/windows-hardware/design/minimum/supported/windows-11-supported-amd-processors

[gjsman]

@Masamune3210 This is not true, actually, and is just misinformed Windows users. MacOS Monterey was a recent bump to the specs in requiring 2015 and newer PCs for most models (except for the 2013 Mac Pro and 2014 Mac mini). However, when Apple drops support for old computers in a new MacOS release, a shocking number of Windows users are ignorant that Apple gives an additional 2-3 years of security updates to previous releases of MacOS.

So, let's say I had a MacBook Pro from Late 2013. I got Big Sur in November 2020. That means I'll have until late 2022 - early 2023 with security updates. On average, about a decade of support. Far more than those people who bought a Surface Studio 2 before the event to learn it will have no major updates and only four years left of security updates. It's more than those users who bought 7th gen chips in 2017, who are hitting the end of the road in 2025 with only eight years of support.

In total, if you look at the averages, if you buy an Apple machine you get about a decade of support on average. My grandparents bought an iMac in 2011 and it just lost official support this year. And frankly, considering it's been a decade and it has 4GB of 1333mhz memory, a very old dual-core Core i5, a 512MB Radeon and a spinning hard drive, I'm OK. And if I really wanted it, I could use the tool, but I can fully understand why Apple wouldn't push us higher versions of MacOS because it truly is old.

[chrisn1992]

@seiggy This is not correct. The list is linked from the official hardware requirements on docs.microsoft.com.

~Where do you read that the list is only for getting the badge?~

MS itself links to the list on docs.microsoft from the official Win11 announcement website.

Even the "Health Check App" released by MS will report that an 7th gen CPU with PTT, Secure Boot and UEFI turned on is fine to upgrade.

I have a 7th gen CPU with a true TPM chip, Secure Boot and UEFI turned on and the app reports it's not fine to upgrade.

WhyNotWin11 or PCHealthCheck from Microsoft?

PCHealthCheck by MS, in the "WhyNotWin11" app is everything green except the CPU.

Same for me, I have a AMD Ryzen 5 1400 Quad Core, works perfectly fine, yet it's not in the list and get the same error on WhyNotWin11, as well as not supported on the pc health check, the rest is green -.-

The issue is that they're sharing the Hardware Developer documentation as the supported CPU list. Which has never been the full list of CPU's supported by the OS for upgrades / enthusiast builds. Only for System Integrators. So it's seriously a massive misstep by whoever is handling the messaging right now. For example, check out the list of "Supported CPUs" for Windows 10 21H1 - https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-10-21h1-supported-intel-processors notice the fact that Intel 5th Gen and previous are all missing, though they all work fine with 21H1 and are eve listed as supported by Intel - https://www.intel.com/content/www/us/en/support/articles/000006105/processors.html

So I'd seriously expect their messaging to change early next week as communication within MS figures out they've published the wrong support list.

Product team is slamming that OEM requirements for the Windows 11 stickers to our face and says we have to bear with it. I guess because they only use pre-built PC provided by OEM, so OEMs are actually slamming this bs to our face. If we want Windows 11, we must buy their pre-built PC.

Those Hardware configuration docs are meant for OEM to make pre-built PC. No the Product team is using that to judging who can use Windows 11. Fishy and BS.

Wrong, Microsoft's Vice President of Product Management has said:

"The supported Windows 11 CPU list I posted applies to both new and upgraded systems." https://twitter.com/dispensa/status/1408573147285135366

And when asked the following question: "Does this mean if a chip, like the 7700k has TPM 2.0 but is not on your list, will not be able to upgrade to Windows 11?"

He responded with: "Yeah, Windows 11 is only supported on the CPU list I posted above. There are more requirements than just TPM 2.0 support (and all supported chipsets should have TPM 2.0, so that's not generally a blocking requirement)." https://twitter.com/dispensa/status/1408580116393848839

Literally it is the soft-blocking for OEM, not enduser, the Product team messes this sh!t up. And he said "not blocking requirement".

so these requirements are for "certification for oems" I would say. If they were for OEMs why are DIY machines being held up to this bizzare CPU whitelist standard on the PC Health app and the documentation on MS' website?

Literally product team behind the app messes up everything, they don't even know how to identify pre-built and self-built, OEM and End-user. The docs sites are literally for Windows ADK.

Even the "Health Check App" released by MS will report that an 7th gen CPU with PTT, Secure Boot and UEFI turned on is fine to upgrade.

Many 7th CPU is not passing the check. 6th is not passing the check. Many unsupported CPU is passing the test. That app is the whole mess. WhyNotWin11 only gives me Yellow CPU Compatibility, which the app in turn should give me the passing status. No. MS says no!

[Masamune3210]

@Masamune3210 This is not true, actually, and is just misinformed Windows users. MacOS Monterey was a recent bump to the specs in requiring 2015 and newer PCs for most models (except for the 2013 Mac Pro and 2014 Mac mini). However, when Apple drops support for old computers in a new MacOS release, a shocking number of Windows users are ignorant that Apple gives an additional 2-3 years of security updates to previous releases of MacOS.

So, let's say I had a MacBook Pro from Late 2013. I got Big Sur in November 2020. That means I'll have until late 2022 - early 2023 with security updates. On average, about a decade of support. Far more than those people who bought a Surface Studio 2 before the event to learn it will have no major updates and only four years left of security updates. It's more than those users who bought 7th gen chips in 2017, who are hitting the end of the road in 2025 with only eight years of support.

In total, if you look at the averages, if you buy an Apple machine you get about a decade of support on average. My grandparents bought an iMac in 2011 and it just lost official support this year. And frankly, considering it's been a decade and it has 4GB of 1333mhz memory, a very old dual-core Core i5, a 512MB Radeon and a spinning hard drive, I'm OK. And if I really wanted it, I could use the tool, but I can fully understand why Apple wouldn't push us higher versions of MacOS because it truly is old.

its only recently that Microsoft has started dropping support for windows versions in short timeframes, xp and 7 both were supported weeeellll after the newer versions of windows were out

[micwoj92]

its only recently that Microsoft has started dropping support for windows versions in short timeframes, xp and 7 both were supported weeeellll after the newer versions of windows were out

Let's see:

Windows xp support: 2001-2014 windows vista support: 2006-2017 Windows 7 support: 2009-2020 windows 8 support: 2012-2023 windows 10 support: 2015-2025 (actually LTSB/LTSC versions even longer, but still 10 years, so 2019 version till 2029 etc)

Your statement is false.

[rcmaehl]

Was going to reply in #83 - will put it here instead:

I agree it would be useful to have links to the requirements within WhyNotWin11.

Note that these links should be culture sensitive.

I think if you strip out the culture code their website takes care of it, so it would be: Requirements: https://www.microsoft.com/windows/windows-11-specifications Intel: https://docs.microsoft.com/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors AMD: https://docs.microsoft.com/windows-hardware/design/minimum/supported/windows-11-supported-amd-processors

Will do.

[Okwizi]

@gjsman , whatever will come out won't be that different from the build, and like other users here have said, Win 11 features aren't outstanding from Win 10, the UI is the only significant change in my opinion. Also, there will always be ways to install Win 11 on older PCs, doesn't really matter if it's a build or final software. What does matter though is what you get from Win 11, is it really an upgrade or downgrade? I personally run Linux Ubuntu on dual boot, so if Win 11 still doesn't make a big difference from Win 10 after the expiration of security updates, I'll just stick to Win 10 or replace the OS with another one if I really wanted to.

[Masamune3210]

Im confused how supporting an OS that game out in 2009 until 2020, when its successor came out in 2012 makes that statement false but whatever, you seem very set in your belief. Would you want to support old versions of a software as complicated as Windows until the end of time? Because I wouldn't

[micwoj92]

Im confused how supporting an OS that game out in 2009 until 2020, when its successor came out in 2012 makes that statement false but whatever, you seem very set in your belief. Would you want to support old versions of a software as complicated as Windows until the end of time? Because I wouldn't

Because Windows 10 came out in 2015, and will be supported up to 2029, when successor came will come out in 2021/2022.

That's about the same timeframe, so your statement "its only recently that Microsoft has started dropping support for windows versions in short timeframes" is false.

[gjsman]

@micwoj92 Windows 10 is only supported until 2025, not 2029.

[micwoj92]

@gjsman Isn't 2019 LTSC up to 2029?

[gjsman]

@micwoj92 LTSC, when licensed as part of Windows 10 Enterprise, is licensed until 2029. Every other Windows 10 version, including Enterprise, dies in 2025.

https://docs.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro

https://docs.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-and-education

[micwoj92]

Oh, thanks for the info. Wasn't aware of that.