Preparing for Insider Preview Builds of Windows 11 - ***UPDATED 6/28***

Hello Windows Insiders! Today we announced Windows 11, and we know you are excited to get your hands on it. You can check out all the details on how to prepare for Windows 11 Insider Preview builds on our blog post.

Once you've reviewed the blog, please use this post to ask any related questions you may have.

We are excited to hear your feedback!!

-The Windows Insider Team

***UPDATE***

For users who are receiving the following message in your Windows Insider Settings:

Your PC does not meet the minimum hardware requirements for Windows 11. Your device may continue to receive Insider Preview builds until Windows 11 is generally available, at which time it is recommended to clean install to Windows 10.

We've made an update to Settings to resolve some issues. Please reboot your device to ensure you have the latest update.

Your new hardware requirements are obsurd. I have 2 PC's that doesn't meet the requirements for Windows 11. My Laptop should as it came out last year, but no that isn't the case because the CPU isn't supported. It even has a TPM 2.0 Chip. My Desktop computer that came with Windows 10 doesn't meet the requirements due to having no TPM 2.0 Chip, no compatible CPU. The only PC in the house that is Windows 11 compatible, is my mother's new computer. Oh and Microsoft was supposed to keep improving Windows 10 and not abandon it like they did with so many other Operating Systems. I may go to Apple and buy me an iMac and a MacBook. Apple supports old hardware unlike Microsoft. If I see a chance in the requirements, and they are more lenient towards old hardware, I might be willing to be a Microsoft customer again. But until then, I don't think so. You are losing a lot of customers, Microsoft. Nobody wants to go buy a brand new PC every time a new OS of Windows rolls out. STOP and Listen to your customers!

Sorry but for now Wiondows 11 does not supprt "discrete" TPM2.0 chips, only "firmware TPM" using UEFI BIOS firmware using a single security profile, and storing the secured keys inside some non-volatile and protected memory of the processor.

Plug any discrete (and more powerful and more secure) TPM2.0 chip on any system using even one of the "supported" processors, this won't work: you still MUST disable the discrete TPM and only use the "fTPM" inside the processor... even if it is also less performant (implemented by code running in a "UEFI capsule" using CPU ressources). TPM chips (which may be connected ion a dedicated LPC port of the motherboard, or inside a fast USB or Firewire or other PCI express adapter, or inside SSD and RAID controlers, or could even be made inside DRAM modules), have dedicated hardware and have hardware better protection than CPU; and they are more easily replacable when needed (without having to change the CPU and/or motherboard, which is costly and requires resintalling the system and buying new licences for everything.

When will Microsoft stop this stupidity for supporting windows 11 only with a "fTPM" inside CPUs? This design was just made for smartphones and small tablets (or very small iOT devices and Raspberry things), just becuase it allowed a reduction of size and manufacturing costs if manufacturer can avoid an extra connector, not for desktops, servers, and high-end notebooks. But "fTPMs" are weak, and easily attackable by side-channel attacks based on time/performance of software or scripts running in any process or thread.

Side-channel attacks are very complex to avoid inside the CPU itself (and avoiding them with mitigation in kernels or in the CPU microfirmware is generally costly in terms of performance on large servers). It's much easier to isolate a discrete TPM which already has builtin and external hardware defenses. a fTPM inside a CPU (and running only on specific cores with NUMA) even at if this is a TPM2.0, is LESS secure than any discrete TPM (even if the latter implements only TPM1.2).

In addition the fTPM has severe problems in terms of deployment: future PCs will have many TPM banks and if needed you'll had more TPM devices to support specific applications notably containers and lamda functions.

Intel has released the new graphic drivers with full compatibility for Windows 11, and the list of the supported CPUs start from the 6th generation.

So, Microsoft you don't have an excuse for not supporting also the 6th generation.

Download Intel® Graphics - Windows® DCH Drivers

Platform (OS Support)

6th Gen Intel® Core™ processor family (Codename Skylake) (19H1)
7th Gen Intel® Core™ processor family (Codename Kaby Lake) (19H1)
8th Gen Intel® Core™ processor family (Codename Kaby Lake-R, Coffee Lake) (19H1)
9th Gen Intel® Core™ processor family (Codename Coffee Lake-R) (19H1)
Apollo Lake (19H1)
Amber Lake  (19H1)
Gemini Lake  (19H1)
Whiskey Lake  (19H1)
Comet Lake  (19H1)
10th Gen Intel® Core™ processor family (Codename Ice Lake) (19H1)
Intel® Core™ Processor with Intel® Hybrid Technology (Codename Lakefield) (19H2+)
Intel® Pentium® Processor family (Codename Jasper Lake) (19H2+)
Intel® Celeron® Processor family (Codename Jasper Lake) (19H2+)
11th Gen Intel® Core™ processor family (Codename Tiger Lake) (19H2+)
Intel® Iris® Xe Dedicated Graphics family (Codename DG1) (20H1+)
11th Gen Intel(R) Core(TM) processor family (Codename Rocket Lake) (20H2+)
11th Gen Intel® Core™ processor family (Codename Tiger Lake -H) (20H2+)

Intel® Atom®, Pentium® and Celeron® processor family (Codename Elkhart Lake) (RS5)

This is not the correct answer: TPM20 was already working in Windows 10, no longer in Windows 11.

Microsoft silently made changes, ignoring the TPM specifications and passing secret commercial agreements with PC makers jsut to force people to buy new costly hardware (with new licences of Windows as well).

Microsoft has also decided to silently drop support of its own standard in Windows 10, and changed its own documentations at the same time. The world was taken by surprise (and now has to listen the lies of Microsoft, and breach of contract, even for existing supported versions of Windows).

The compatiblity check is hiding the real reasons, they are not at all based on technical reasons, just commercial ones. And worse:

Windows 11 is MUCH LESS secure now than Windows 10, e.g. Windows Defender will not longer be enabled and will no longer run from boot (you'll haver to reenable it after EACH reboot).

Microsoft seems to argue that these changes are good for users security, but the reality is that Microsoft is not adding, but dropping security features and support: many more PCs will be left without any effective protection (and soon without any support, even if customers paid for this).

microsoft is also lying when it says that it will upward compatible. This is completely FAKE. windwos 11 is only comptible with a limited set of hardware built by companies that made secret deals with a small branch Microsoft.

Even the Microsoft support teams were surprized. Even the most expensive and latest Surface Pro built and sold by Microsoft, are not eligible.

May be Microsoft should have kept its initial promiss (affirmed years ago and never demented since then, just very announced and never expected a few days ago, even if this version had many of these features tested under the name "Windows 10" and without ever saying that there would be compatibility restriction changes, that were never tested even by Insiders) : that windows 10 was the LAST major version of Windows and that it was now developing around the Linux kernel (or BSD, including Android, iOS and MacOS). What is the purpose of the Windows Insider program when there are so disturbing changes and Microsoft actually did not listen its participants or did not ask anything before doing such strong formal announcement and making radical changes in the documentation of ALL existing supported version of Windows)?

The result in a few months will be clear: Google, Oracle and Apple will capture the market abandonned by Microsoft, no customer can trust now Microsoft.

I see only good alternative: go to Linux (which are now equally capable, and have greats desktop environements).

The alternative woukld be that Google or Oracle will start selling their own version of Windows, running in a VM hosted on a Linux-based hypervisor and kernel).

Same hear, I am trying to update to dev channel to check if the error still exists. I will update if it worked.