If you’re interested in testing Windows 11, you’ll be able to do so starting next week via the Dev channel in the Windows Insider Program. Here’s how to get started.
“We plan to release the first Insider Preview build for Windows 11 next week,” Microsoft’s Amanda Langowski writes. “However ahead of that release, we wanted to let Insiders know of a few changes we are making to how they will receive Windows 11 Insider Preview builds going forward.”
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
Those changes aren’t all that unexpected. The big one is that the Windows Insider Program will follow the same system requirements as will Windows 11 generally, you’ll need a PC with a dual-core 1 GHz or faster 64-bit processor, 4+ GB of RAM, 64+ GB of storage, and a TPM 2.0 module. That said, if your PC is already in the Windows Insider Program Dev channel and it doesn’t meet those requirements, Microsoft will allow you to install Windows 11 Insider Preview builds, at least until Windows 11 ships; at that time, those PCs will be opted out of testing and will have to be manually switched back to Windows 10.
To get started, you simply need to join the Dev channel of the Windows Insider Program. If you’ve already done so, you’re all set, assuming your PC is eligible. There’s nothing else to do.
If you’re not enrolled yet, open Settings and navigate to Update & Security > Windows Insider Program to opt-in and then reboot the PC. And then wait for next week. Windows 11 is on the way.
Note that the first builds will not have some features, including Android app support and Chat with Teams. And Windows 11 is expected to hit the Beta channel in July.
dftf
<p>I’ve been able to install the leaked (21996.1) build inside a VMWare Player machine… so unless the final version will be different, currently I’ve had no issue…</p>
dftf
<p>There is a PDF you can download from Microsoft (download.microsoft.com/download/7/8/8/788bf5ab-0751-4928-a22c-dffdc23c27f2/Minimum%20Hardware%20Requirements%20for%20Windows%2011.pdf) which breaks-down the requirements further. It says when Windows 11 detects it is running inside a VM, it will ignore certain requirements</p>
dftf
<p>Yes, Microsoft have officially said "bottom of the screen only" in the list of feature depreciations and removals</p>
dftf
<p>These should be available here in due-course: microsoft.com/en-us/software-download/windowsinsiderpreviewiso</p>
dftf
<p>This might help: pcworld.com/article/3622981/older-microsoft-surface-devices-cannot-upgrade-to-windows-11.html</p>
dftf
<p>The tool has now been updated to tell you exactly what issues there may be:</p><p><br></p><p>windowslatest.com/2021/06/26/microsoft-updates-windows-11-requirements-says-tpm-2-0-is-required/amp/</p><p><br></p><p>The Surface Book 1 has been confirmed as not eligible for an update to Windows 11. List of supported models here:</p><p><br></p><p>slashgear.com/some-older-microsoft-surface-devices-cant-upgrade-to-windows-11-25679919/</p>
dftf
<p>In the "Windows Security" app, click "Device Security" then "Security processor details" and check the version in there to be sure: look after "Specification version".</p><p><br></p><p>Beyond that (1) ensure within your UEFI settings it is fully-enabled and (2) see if there are any BIOS updates for your device, or any specific TPM firmware updates</p>
dftf
<p>Your CPU will likely work; it seems an 8th Gen Intel CPU is "preferred", but not "required", at-least according to docs.microsoft.com/en-us/windows/compatibility/windows-11</p>
dftf
<p>To confirm your TPM version, go into the "Windows Security" app, click "Device Security", then click "Security processor details". Then check next to "Specification version"</p>
dftf
<p>I’d imagine the requirements though are going to mean a LOT of devices won’t be able to run Windows 11 though, compared to Windows 10</p><p><br></p><p>Even on recent-model HP ProBook and EliteBook devices we use at work, if you want to install Windows onto a SATA drive you have to change from "UEFI" mode to "Legacy BIOS", as otherwise it will not boot (it doesn’t appear in the "boot order" list). As Windows 11 requires UEFI, that’s an issue.</p><p><br></p><p>Likewise, I think to use some third-party full-disk encryption software you may have to disable the "Secure Boot" feature. So for any business who uses something-other than BitLocker, again, this could be an issue.</p>
dftf
<p>Oddly according to docs.microsoft.com/en-us/windows/compatibility/windows-11/ it seems the TPM must be version 1.2 minium; 2.0 is simply recommended.</p>
dftf
<p>I think having it required on <em>new PCs</em> would be fine, it just sucks for existing ones. You’d think at a time there is a global silicon shortage it makes little-sense, too…</p><p><br></p><p><em>"… since I haven’t read anywhere that full-disk encryption will be on by default in all Windows 11 installs. (Which would be a recipe for disaster, since nobody would bother to back up their BitLocker key …)"</em></p><p><br></p><p>It’s possible that FDE <em>could </em>become a default thing on Windows 11 Home installs: it will be mandatory to sign-in with a <em>Microsoft Account</em>, and the backup-key could get linked to that. And as all devices have to ship with a 64-bit CPU, Secure Boot enabled and a v2.0 TPM, that means the "Device Encryption" option, currently in Windows 10, would be supported. (Which is essentially BitLocker behind-the-scenes, but the only config is simply ON or OFF).</p><p><br></p><p>Don’t forget that on all iOS, iPadOS and Android devices sold in recent-years, the internal-storage is encrypted by-default, so it’s nothing new in some cases. Linux doesn’t (but most distros give you the option during the initial install). And on macOS I’ve no-idea if "FileVault" is enabled by-default or not…</p>
dftf
<p>It will be required — listed here under "System Requirements":</p><p>microsoft.com/en-gb/windows/windows-11-specifications</p>
dftf
<p><strong>UPDATE</strong>: according to docs.microsoft.com/en-us/windows/compatibility/windows-11 , it’ll only be required to have a v1.2 TPM chip; a v2.0 is "recommended", but not required</p>
dftf
<p>Anyone currently running an Insider version of Windows 10 right now is going to get upgraded to Windows 11 within the next few weeks. However, as you’re running the leaked build (which Microsoft has been issuing legal takedown-orders to sites to remove their downloads) I think you’ll find you won’t be supported.</p><p><br></p><p>Wait until an official Windows 11 Insider Preview ISO is made available here (microsoft.com/en-us/software-download/windowsinsiderpreviewiso) and do a clean-install at that time</p>
dftf
<p>Yeah, I’d imagine many cheap-end laptops and desktops aimed at the home-user market right-now probably lack a TPM… so bit mad that a new device you could buy today won’t run Windows 11 when it’s released later this year! It’s like the "Vista Capable" thing all-over-again!</p>
dftf
<p>In the "Windows Security" app, click "Device Security" then click "Security processor details"</p>
dftf
<p>Or go into Device Manager and expand the "Security devices" item; if you don’t have that, your device either has no TPM, or you need to go into the BIOS / UEFI settings and enable it</p>
dftf
<p>"<span style="color: rgb(0, 0, 0);">Ninja’d"? What do you think this site is, </span><em style="color: rgb(0, 0, 0);">Ars Technica</em><span style="color: rgb(0, 0, 0);">? ;)</span></p>
dftf
<p>You can run 11 on them providing they have at-least a 1.2 TPM chip, UEFI (not BIOS only) and offer Secure Boot.</p><p><br></p><p>Otherwise you have until October 2025 to still run Windows 10 on them (or Jan 2023 for Windows 8.1)</p>
dftf
<p>Well, unless Microsoft drops any of the requirements before launch then those machines have until October 2025 to run Windows 10 securely (assuming they are on either Home or Pro). And after that point, you might be able to find someone running an activation-server online and offering LTSC licences; the 2019 LTSC is supported until Jan 2029…</p>
dftf
<p>When Windows 11 detects it is running inside a VM, it ignores certain hardware requirements.</p><p><br></p><p>Refer to this PDF: download.microsoft.com/download/7/8/8/788bf5ab-0751-4928-a22c-dffdc23c27f2/Minimum%20Hardware%20Requirements%20for%20Windows%2011.pdf</p>
dftf
<p>It’s unlikely you’ll get a Media Creation Tool until Windows 11 goes RTM, but an ISO image should be made available at microsoft.com/en-us/software-download/windowsinsiderpreviewiso once it officially starts rolling-out to Insiders</p>
dftf
<p>Apparently an 8th Gen CPU is only preferred, but should not prevent a Windows 11 install, at-least according to docs.microsoft.com/en-us/windows/compatibility/windows-11</p>
dftf
<p>The Health Check tool has just been updated within the last few hours and now will tell you what the issue is</p>
dftf
<p>Given the Dev build was leaked, not made officially available, I’d highly-doubt they’d allow an in-place upgrade, no…</p>
dftf
<p>The value you would be looking at in Windows Security > Device Security > "Security processor details" is the <strong>Specification version </strong>field.</p><p><br></p><p>Another easy way is to go into Device Manager and then expand the "Security devices" item: on my device, it clearly says "Trusted Platform Module 1.2".</p><p><br></p><p>According to docs.microsoft.com/en-us/windows/compatibility/windows-11 , your device must have a v1.2 TPM minimum (v2.0 is recommended) and also the "8th Gen Intel CPU or equivalent AMD or ARM" is also a "recommended", but not "required"</p>
dftf
<p>It’s reported Microsoft have now released an updated version of the Health Check tool, and it will now tell you specifically what the issues are</p>
dftf
<p>Yeah, even-though on the main page it says 2.0 is required, it clearly says on docs.microsoft.com/en-us/windows/compatibility/windows-11 that only 1.2 is required; 2.0 is just preferred.</p><p><br></p><p>I’m still puzzled though why they didn’t make things like a TPM, UEFI and Secure Boot mandatory for new devices, but not require them on existing ones. Would have made more-sense: newer devices are more-secure by default, but you can still get Win11 on as-many devices as-possible…</p>
dftf
<p>Update: Microsoft have updated that page to confirm a v2.0 TPM will be the minimum (bit.ly/3jfZ5fe)</p>
dftf
<p>You can continue to run Windows 10 securely until October 2025. If you install a virtualisation solution (such as the built-in <em>Hyper-V </em>if you’re using Pro or higher; or <em>VMWare Player </em>or <em>Oracle VM VirtualBox </em>on Home) you can install Windows 11 inside it, and run it inside Windows 10.</p>
dftf
<p>You can find the source of what is referenced above here: docs.microsoft.com/en-us/windows/compatibility/windows-11/</p>
dftf
<p>They have recently updated that page (bit.ly/3jfZ5fe). TPM 1.2 won’t be supported</p>
dftf
<p>Source: docs.microsoft.com/en-us/windows/compatibility/windows-11</p>
dftf
<p>They have now revised that page and clarified it must be a v2.0 TPM. (source: bit.ly/3jfZ5fe )</p>
dftf
<p>That’s what I’m wondering too… is it "security and bug-fix only" from now for Windows 10?</p>
dftf
<p>Nope, I don’t see your model on the list of confirmed Surface devices which will get Windows 11:</p><p><br></p><p>slashgear.com/some-older-microsoft-surface-devices-cant-upgrade-to-windows-11-25679919/</p><p><br></p><p>The Register say it’s because the CPU isn’t supported:</p><p><br></p><p>theregister.com/2021/06/25/windows_11_processor/</p>