TPM 2.0, short for Trusted Platform Module, is a security chip or firmware feature that Windows 11 requires before it will install. It stores encryption keys, protects login credentials, and enables features like BitLocker and Windows Hello, which is why Microsoft made it mandatory. Many otherwise compatible PCs already have TPM hardware built in, but the setting is switched off in the BIOS or UEFI firmware by default, especially on custom-built desktops. Checking whether your machine has TPM 2.0 takes less than a minute in Windows itself. Press the Windows key and R together, type tpm.msc, and press Enter to open the TPM management console. If the status shows that the TPM is ready for use and the specification version reads 2.0, you can stop here because your system already meets the requirement.

If the console reports that a compatible TPM cannot be found, do not panic, because in most cases the chip is present but disabled in firmware. The fix is to restart your computer and enter the BIOS or UEFI settings, typically by pressing Delete, F2, or F12 repeatedly during boot. The exact key varies by manufacturer, so watch the splash screen for a hint or check your motherboard manual. Once inside the firmware interface, look for a Security, Advanced, or Trusted Computing section. This is where motherboard vendors hide TPM controls, often under names like TPM Device Selection, Security Device Support, or Trusted Platform Module. On Intel systems the feature may be labeled Intel PTT or Platform Trust Technology, while AMD boards call it fTPM or firmware TPM.

Before changing anything, take a quick photo of your current BIOS settings with your phone so you can revert if something goes wrong. Then set the TPM option to Enabled rather than Disabled, and if a firmware-versus-discrete choice appears, firmware TPM is the usual correct pick for a system without a physical TPM module. Some boards also offer a TPM 2.0 versus TPM 1.2 selector, and you should choose 2.0 since Windows 11 will not accept the older standard. If you are unsure whether your machine is genuinely compatible, background reading on cloud hardware strategy can help you understand how the industry weighs hardware security features. Save your changes with the firmware's Save and Exit option, usually F10, and let the PC reboot into Windows.

After the reboot, run tpm.msc again to confirm that the module now shows up as ready and version 2.0. If it still does not appear, your motherboard may need a BIOS update that adds or unlocks TPM support, which you can download from the manufacturer's support page. Updating BIOS firmware carries a small risk, so only do it while connected to reliable power and never interrupt the process. Laptop users rarely need this step since most laptops shipped in recent years already have TPM 2.0 active. It is also worth checking Secure Boot, a separate firmware setting that Windows 11 requires alongside TPM. Enabling it follows the same pattern: find the Secure Boot option under the Boot or Security tab, set it to Enabled, and save your changes.

One common stumbling block is that enabling TPM can trigger a one-time Windows notice asking you to clear or confirm the TPM, especially after firmware updates. Do not clear the TPM unless you have backed up any BitLocker recovery keys, because clearing wipes stored encryption keys and can make encrypted drives unreadable. If your system is brand new and BitLocker is not yet set up, accepting the prompt is generally safe. Desktop owners with very old motherboards should also verify that a TPM header or module option exists at all, since some legacy boards lack the feature entirely and cannot run Windows 11 without hardware upgrades. When the board truly lacks TPM 2.0, no software trick changes that reality.

Once TPM 2.0 is confirmed active and Secure Boot is on, you can proceed with the Windows 11 installation or upgrade with confidence. Run the PC Health Check tool or simply retry the setup media, and the TPM error that blocked you before should be gone. Keep your BIOS firmware reasonably up to date going forward, because manufacturers periodically improve TPM and security behavior through updates. For readers who enjoy hands-on infrastructure work, pairing this hardware knowledge with container deployment skills is a natural next step, and those curious about the broader ecosystem can explore how automation platforms are changing everyday IT tasks.