Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / How Windows 11 Is Quietly Mandating Enterprise Hardware Root of Trust
Transcript
- Lucas: If you are an enterprise IT admin and you think deploying Windows 11 with TPM 2.0 is enough to check the security box, Microsoft has a quiet surprise for you — hardware root of trust is now effectively mandatory for new certified devices. Luna: Wait — I thought TPM 2.0 was the hardware root of trust. What more could they want? Lucas: That's the common assumption, and it's half right. TPM 2.0 provides the cryptographic engine, but the root of trust is about the chain that leads up to it. Specifically, Windows 11's Windows Hardware Compatibility Program — the WHCP — now requires that certified devices measure platform firmware measurements into the TPM during boot. Those measurements get stored in PCR registers, especially PCR7. Luna: PCR7 is the one that binds BitLocker to the exact firmware state, right? Lucas: Exactly. PCR7 covers the secure boot policy and the UEFI firmware. If the measurements recorded at boot don't match the expected values, BitLocker won't release the encryption key without a recovery password. That's the security win — a compromised bootloader or malicious firmware change gets caught immediately. But here's the quiet part: as of January 2026, any new device submitted for WHCP certification must pass a test that verifies PCR7 is populated correctly with the right measurements. Luna: So this isn't a Windows update that changes behaviour on existing hardware — it's a supply-side mandate. New PCs must have this, or they don't get the Windows 11 seal of approval. Lucas: Correct. Microsoft hasn't made a big announcement about it. It's in the WHCP documentation — section 2.4.1, firmware measurement requirements. But if you're an IT buyer spec'ing out next quarter's laptop refresh, the OEMs are already complying. Dell, Lenovo, HP — they've all updated their firmware to include the measurements. The issue is older hardware that was shipped before this requirement. Luna: How do you check if a machine is compliant? I assume there's a PowerShell command. Lucas: There is. You run 'Get-Tpm' in PowerShell and look at the 'IsReady' property and the 'ManufacturerId' — but the real test is checking 'Get-TpmEndorsementKeyInfo' to see if the endorsement key certificate is present. More practically, for BitLocker enforcement, you want to run 'manage-bde -protectors -get C:' and see if the key protectors include a PCR validation profile that includes PCR7. If it's missing, your BitLocker won't bind to firmware integrity. Luna: What percentage of enterprise fleets would fail that check today? Lucas: I've seen estimates that roughly 30 to 40 percent of enterprise PCs shipped between 2021 and early 2024 don't have the proper PCR7 measurements. They have TPM 2.0, they have secure boot enabled, but the firmware measurement logic wasn't implemented by the OEM. Those machines will still run Windows 11, but they won't pass the new hardware certification, and more importantly, they won't get the full security guarantees around BitLocker. Microsoft is nudging the ecosystem toward a hardware root of trust that starts in the firmware, not just the TPM chip. Luna: So for an IT admin, the actionable step is auditing the fleet now — not waiting for a compliance deadline. Lucas: Absolutely. And there's another layer: Microsoft is also starting to require device attestation for certain cloud services. If you use Azure AD joined devices and conditional access policies, the attestation check verifies the hardware root of trust. Machines without proper PCR measurements can fail that attestation and get blocked from accessing corporate resources. It's a domino effect. Luna: Is there a way for an OEM to add these measurements via a firmware update, or is it a hardware limitation? Lucas: In some cases, a firmware update can add the measurement logic. Many UEFI firmware implementations on Intel 12th-gen and later, or AMD Zen 4 and later, have the capability but shipped with it disabled. The OEM can release a BIOS update to enable the PCR7 measurements. But on older platforms — say, Intel 11th-gen or AMD Zen 3 — the firmware may not support it at all. Those machines are effectively at end of life for this security feature. Luna: That sounds like a planned hardware refresh cycle. Microsoft wants everyone on newer silicon to get the root of trust. Lucas: It's a pattern we've seen before — TPM 2.0, then VBS and Credential Guard, now hardware root of trust. Each step raises the security baseline but also raises the hardware floor. The interesting angle is that this time, it's not a Windows 11 system requirement — it's a certification requirement. So enterprises can technically buy non-certified hardware, but they lose the ability to use certain security features and cloud integrations. Most organizations won't accept that trade-off. Luna: What about devices that are already in use? Can an IT admin force enable PCR7 measurement via Group Policy? Lucas: No — PCR7 measurement is a firmware behaviour. Group Policy can enforce BitLocker policies, like requiring a TPM and PIN, but it cannot make the firmware report measurements it doesn't generate. The only option is a firmware update or hardware replacement. That's why auditing now is critical: know which machines can be updated and which cannot. Luna: Is there any downside to enabling PCR7 binding? Like more BitLocker recovery prompts if firmware gets updated? Lucas: Yes, that's the operational headache. If you bind BitLocker to PCR7 and then apply a BIOS update that changes the firmware measurements, BitLocker will demand a recovery key at next boot. IT needs to have a process to suspend BitLocker before firmware updates — or manage the recovery keys centrally. It's a trade-off between security and manageability. Luna: Sounds like a classic security vs. convenience problem, but with a clear winner if you care about protecting against firmware attacks. Lucas: Exactly. And given the rise of firmware-level threats like LoJax and Bootkitty, this is a reasonable escalation. Let's talk a bit about the actual technical details of how PCR7 binding works, because I think it clarifies why this mandate matters. Luna: Please — I think listeners want to know the nuts and bolts. Lucas: So the TPM has several Platform Configuration Registers — PCRs. PCR0 measures the BIOS, PCR2 measures option ROMs, PCR4 measures the boot loader. PCR7 specifically measures the secure boot policy and the UEFI firmware. When BitLocker creates a protector that includes PCR7, it seals the encryption key to the current values of PCR7. If an attacker modifies the secure boot policy or replaces the firmware, the PCR7 values change, and the key can't be unsealed. The system boots, but BitLocker goes into recovery mode — unless the attacker also has the 48-digit recovery key. Luna: So the recovery key becomes the last line of defence. That's why Microsoft pushes for storing recovery keys in Azure AD or Active Directory. Lucas: Right. And the new WHCP requirement ensures that PCR7 is actually populated with meaningful measurements. Some early UEFI implementations left PCR7 empty or wrote a constant value — essentially making the binding useless. The certification test checks for proper measurement of the secure boot variables. Luna: I have to ask: is Microsoft doing this to improve security, or to drive hardware sales? Both? Lucas: I think it's both, but I lean toward security as the primary motive. The era of firmware attacks is real. We've seen sophisticated threat actors persist in firmware for years. A hardware root of trust is the best defence. That said, Microsoft's hardware partners certainly benefit from the upgrade cycle. But the timing — quietly embedding this in the WHCP rather than announcing a new security initiative — suggests they want to avoid the backlash that came with the TPM 2.0 requirement. Luna: It's a classic Microsoft move: define the standard through certification, not through system requirements. Lucas: Exactly. And honestly, a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making shows like this — so we can dig into these quiet changes without chasing ad revenue. It's a small group, but it keeps us independent. Luna: Yeah, it really does. And knowing that people find value in these deep dives makes it worth the effort. Lucas: So back to the technical side — if you are an IT admin, the first step is to inventory your fleet. Use a script to check 'Get-Tpm' and 'Get-WmiObject -Namespace Root\CIMv2\Security\MicrosoftTpm -Class Win32_Tpm'. Look for the 'IsEnabled' and 'IsActivated' properties, but more importantly, check 'SpecVersion' — it should be 2.0. Then check the PCR7 binding with 'manage-bde'. If you find machines with TPM 2.0 but no PCR7 protector, those are candidates for firmware updates or replacement. Luna: And for those with older TPM 1.2? They're out of luck entirely. Lucas: Windows 11 already requires TPM 2.0, so those shouldn't be in the fleet for Windows 11. But if you have Windows 10 machines with TPM 1.2, they are not affected by this mandate — but they also don't get the hardware root of trust benefit. The bottom line: the industry is converging on a firmware-rooted trust model, and Windows 11 is the vehicle. Luna: What about virtual machines? Do they need hardware root of trust? Lucas: Virtual machines rely on the host's hardware root of trust. If the host has proper PCR7 measurements and the VM uses a virtual TPM, the vTPM inherits the host's trust chain. But the VM itself doesn't need its own firmware measurements — it's abstracted. That said, if you're using Hyper-V with shielded virtual machines, the fabric attestation does require hardware root of trust on the host. Luna: Good clarification. So the mandate primarily affects physical endpoints. Lucas: Primarily, yes. Also servers, but the WHCP is mostly about client devices. Servers have their own certification programs. But the trend is clear: Microsoft wants every Windows device to have a measured boot chain. Luna: One last question: how does this interact with Linux dual-boot? If you have a Windows 11 machine that also boots Linux, does the Linux boot process affect PCR7 measurements? Lucas: It can. If Linux boots with Secure Boot disabled or uses a different bootloader, the PCR7 measurements will change. That means if BitLocker is bound to PCR7, switching to Linux and back might trigger recovery. It's a known pain point for dual-boot setups. Some organizations mitigate by using a separate protector or by not binding to PCR7 on dual-boot machines. But Microsoft's direction is to make that binding the default. Luna: So the takeaway: audit your fleet, plan firmware updates, and prepare for a hardware refresh cycle on older machines. Lucas: Exactly. And start now — because as Windows 11 updates continue, more features will depend on this hardware root of trust. It's not going away.