Why Windows 11 is forcing everyone to use TPM chips

 

 

Microsoft announced yesterday that Windows 11 will require TPM (Trusted Platform Module) chips on existing and new devices. It’s a significant hardware change that has been years in the making, but Microsoft’s messy way of communicating this has left many confused about whether their hardware is compatible. What is a TPM, and why do you need one for Windows 11 anyway?

 

“The Trusted Platform Modules (TPM) is a chip that is either integrated into your PC’s motherboard or added separately into the CPU,” explains David Weston, director of enterprise and OS security at Microsoft. “Its purpose is to protect encryption keys, user credentials, and other sensitive data behind a hardware barrier so that malware and attackers can’t access or tamper with that data.”

So it’s all about security. TPMs work by offering hardware-level protection instead of software only. It can be used to encrypt disks using Windows features like BitLocker, or to prevent dictionary attacks against passwords. TPM 1.2 chips have existed since 2011, but they’ve typically only been used widely in IT-managed business laptops and desktops. Microsoft wants to bring that same level of protection to everyone using Windows, even if it’s not always perfect.

Microsoft has been warning for months that firmware attacks are on the rise. “Our own Security Signals report found that 83 percent of businesses experienced a firmware attack, and only 29 percent are allocating resources to protect this critical layer,” says Weston.

 

That 83 percent figure seems huge, but when you consider the various phishing, ransomware, supply chain, and IoT vulnerabilities that exist, the broad range of attacks becomes a lot clearer. Ransomware attacks hit the headlines weekly, and ransomware funds more ransomware so it’s a difficult problem to solve. TPMs will certainly help with certain attacks, but Microsoft is banking on a combination of modern CPUs, Secure Boot, and its set of virtualization protections to really make a dent in ransomware.

 

Microsoft is trying to play its part, particularly as Windows is the platform that’s often most affected by these attacks. It’s widely used by businesses worldwide, and there are more than 1.3 billion Windows 10 machines in use today. Microsoft software has been at the core of devastating attacks that made global headlines, like the Russia-linked SolarWinds hack and the Hafnium hacks on Microsoft Exchange Server. And while the company isn’t responsible for forcing its clients to keep its software patched, it’s trying to be more proactive about protection.

Microsoft has a habit of struggling to move Windows into the future in both hardware and software, and this particular change hasn’t been explained well. While Microsoft has required OEMs to ship devices with support for TPM chips since Windows 10, the company hasn’t forced users or its many device partners to turn these on for Windows to work. That’s what’s really changing with Windows 11, and combined with Microsoft’s Windows 11 upgrade checker, it has resulted in a lot of understandable confusion.

 

Microsoft’s Windows 11 website lists the minimum system requirements, with a link to compatible CPUs and a clear mention that a TPM 2.0 is required at a minimum. (That may not actually be the case.) The PC Health Check app that Microsoft asks people to download and check to see if Windows 11 runs will flag systems that do not have Secure Boot or TPM support enabled or devices that have CPUs that aren’t officially supported (anything older than 8th Gen Intel chips).

 

That’s left many trying to figure out if their device supports TPM or not, confusion with BIOS settings, and even people rushing to buy separate TPM modules they don’t need. Some are even scalping TPM 2.0 modules on eBay!

 

Hidden away on Microsoft’s site is what’s really happening here — or so we thought, until Microsoft changed its page a couple hours after we published this story. According to the original version of the page, the true minimum requirements are TPM 1.2 and a 64-bit dual-core CPU that’s 1GHz or greater. Since TPM support can be enabled through practically any modern CPU in the BIOS settings of a machine, you shouldn’t need a separate module unless your CPU is very old.

 

But the new page says it requires TPM 2.0 and an processor that Microsoft has explicitly certified as compatible — which might mean everything before an 8th Gen Intel Core and AMD Ryzen 2000 won’t work. We’re following up with Microsoft now.

 

Screenshot by Sean Hollister / The Verge

Microsoft is promoting TPM 2.0 and performing checks for 8th Gen or newer Intel chips because these are the requirements for certified OEM hardware — the machines you’ll find in stores with an inevitable Windows 11 sticker. But Windows 11 will likely install on devices with TPM 1.2 enabled, and practically any CPU that meets the 64-bit dual-core 1GHz or above standard — you’ll just have to navigate a notification telling you the “upgrade is not advised.”

 

Microsoft doesn’t even mention the TPM 1.2 minimum in its blog post outlining this new security effort today, nor does the company offer any details on the CPU support that many seem to be stumbling into. If you’re having issues with the PC Health App checker for Windows 11, make sure you have “PTT” on Intel systems enabled in the BIOS, or “PSP fTPM” on AMD devices. The company’s system checker should be less confusing soon, though: shortly after we published this story, Weston tweeted that it will now be more specific about why your PC isn’t passing muster.

 

What Microsoft is trying to achieve here will benefit the Windows ecosystem in years to come, alongside its new efforts for Xbox-like security on Windows. Microsoft just totally dropped the ball on explaining that to everyone on day one.

 

Update, 2:26PM ET: Added that Microsoft updated its PC Health Check app, shortly after we published this story, to be more specific about why your computer isn’t meeting Windows 11 system requirements.

 

Update, 3:53PM ET: Added that Microsoft has changed its compatibility page to mention TPM 2.0 as a requirement instead of TPM 1.2, and that specific CPUs may be a requirement. We’re getting to the bottom of this now.