I'm sorry Microsoft but 2.6GHz base, 3.1GHz multi core turbo, and 3.5GHz single core turbo is plenty fast for me............. and you. Even your app says so.![]()
Have you been missing the news? Certain W11 security features rely on Processor features that if enabled, had way too much overhead on older Processor generations, at which point Microsoft drew the line. But yeah, in theory it should work anyways if somehow you bypass whatever checks there are.
The point is that there's no one easy explanation for why the CPU support list is the way it is, and we're left guessing about the rationale. And this is why that cynical argument about Windows 11—that it's a ploy to sell new PCs to people who don't need them yet—resonates. Never mind that Windows 10 will continue to receive security updates through at least 2025 and that its ubiquity (and underlying similarity to Windows 11) means that most major apps will continue to support it for years.
Microsoft's communication on this subject raises too many questions and provides too few satisfactory answers. And for computers that are already out there, installing Windows 11 doesn't seem to actually improve security in any way that wasn't already possible with Windows 10—getting more people to enable Secure Boot and TPM 2.0 on their self-built systems is good for the platform's security as a whole, but these features are already enabled on Windows 10 PCs made and sold by major OEMs. And that accounts for the vast majority of PCs out there, particularly in businesses and governments that stand to gain the most from improved security.
You missed this paragraph...
According to the first link, you can lose 30-40% performance on unsupported Processors. That is quite sizeable, and can't be simply hidden under the rug. Just imagine the headlines, "New Windows version makes the system up to 40% slower than Windows 10 on a few year old computers". Reminds me of when Nested Virtualization (To run a VM inside a VM) was first introduced, it worked, but without certain Processor features was slow as hell.Microsoft hasn't spelled this out as clearly as it could, but the best rationale for the processor requirement is that these chips (mostly) support something called "mode-based execution control," or MBEC. MBEC provides hardware acceleration for an optional memory integrity feature in Windows (also known as hypervisor-protected code integrity, or HVCI) that can be enabled on any Windows 10 or Windows 11 PC but can come with hefty performance penalties for older processors without MBEC support. We've covered HVCI and MBEC in more detail here.
ehm, i installed yesterday the latest insider build on a A6-9500...
Performance? How well does it run and how usable is 11?
I suspect they are shocked at how many sandy bridges and ivy bridges, if not older, are still in active use running Windows 10 21H1 and maybe this is their response.
(This is the problem with MS making Windows upgrades free instead of much pricier than OEM licences - now they don't have any financial incentive to care about your old hardware)
Yup! 4 cores/8 threads and wicked fast with 32gb overclocked RAMSkylake? Win10 21H1 still runs okayish on Core2quads with an SSD and 4GB mini.
From a business perspective, they'd certainly prefer if you went with one of their 365 products.
Again: MBEC instructions.I still dont understand the cpu requirement
According to the article @zir_blazer linked, OEMs don't even turn on the feature because of fears of loss of performance, among other things.Again: MBEC instructions.
On AMD with Zen+, Intel 8th gen.
Assuming MBEC support was Microsoft's goal here, there are two big problems. The first is that not all processors that support it are on the Windows 11 support list (most notably 7th-generation Intel Core CPUs). Some processors that are on the list don't appear to support MBEC (namely AMD's Ryzen 2000-series CPUs and their Zen+ architecture). This may be why Microsoft doesn't explicitly call out MBEC support in any of its posts on the Windows 11 requirements; you have to dig further into the company's documentation to have it spelled out that HVCI works best with MBEC and that MBEC is only available in Intel Kaby Lake or AMD Zen 2 processors and newer.
The other problem is that HVCI isn't even enabled by default in Windows 11. To enable it, open the Windows Security app, navigate to Device security, click Core isolation details, and turn on Memory integrity. This is the exact same way the feature already works in Windows 10. Microsoft does advise OEMs to enable it by default on new systems with 11th-generation Intel Core or AMD Zen 2 processors and newer, though, even then, it's not a strict requirement. This is, again, the state of the feature as it currently exists in Windows 10.
I know many ways to install Win 11, the issue is support through Windows update and who knows what else may crop up.
The point was that this is the "official" way released by Microsoft for the released version of W11, not some cobbled up way based on pre-release versions of W11.I know many ways to install Win 11, the issue is support through Windows update and who knows what else may crop up.
The point was that this is the "official" way released by Microsoft for the released version of W11, not some cobbled up way based on pre-release versions of W11.
And, yes, installing W11 on any device not officially supported relieves Microsoft of supplying updates or support for that device.
You missed this paragraph...
According to the first link, you can lose 30-40% performance on unsupported Processors. That is quite sizeable, and can't be simply hidden under the rug. Just imagine the headlines, "New Windows version makes the system up to 40% slower than Windows 10 on a few year old computers".
I wonder how long before some enterprising hacker writes a tool to lie about the hardware to Windows, making it think that it's running on supported hardwareAnd, yes, installing W11 on any device not officially supported relieves Microsoft of supplying updates or support for that device.