Alert TPM Device Is Not Detected

The Alert TPM Device Is Not Detected error means your PC cannot see the Trusted Platform Module chip, usually because of BIOS settings or firmware.

What The Alert TPM Device Is Not Detected Error Means

The message alert tpm device is not detected usually appears during startup on a Windows laptop or desktop, sometimes just before the system loads and sometimes right after a BIOS screen.

A Trusted Platform Module is a small chip on the motherboard or built into the processor that stores encryption keys, BitLocker information, and sign-in secrets for Windows Hello and similar features.

When firmware or Windows cannot talk to this chip, the system shows a tpm device not detected warning and may ask for a BitLocker recovery key, disable some security options, or even stop an upgrade to Windows 11.

On many Dell, HP, Lenovo, and other systems the wording matches this TPM alert, but the root problem is the same: firmware, configuration, or hardware is blocking access to the security chip.

Main Causes Of A TPM Device Not Detected Alert

This alert has a short line of text, yet several different conditions can trigger it.

Most causes fall into a few groups that help you decide which fix to try first.

Likely Cause	Typical Symptom	First Action
TPM disabled or hidden in BIOS	This TPM alert appears at every boot	Enter firmware setup and enable TPM, PTT, or fTPM
Outdated or buggy BIOS	Alert started right after a firmware update or reset	Install the latest stable BIOS from the vendor
TPM driver issue in Windows	tpm.msc says no compatible TPM, but BIOS shows one	Reinstall or update the security device driver
Cleared or replaced motherboard	BitLocker asks for recovery each boot	Enter recovery key and rebind BitLocker to the TPM
Physical TPM fault	TPM missing in both BIOS and Windows tools	Check warranty and contact the system maker

Some business laptops can switch between a discrete hardware TPM chip and a firmware based one inside the CPU, and the alert often shows up if this toggle changes or the inactive option is selected.

Company managed devices can also show the alert tpm device is not detected when network policies expect one TPM configuration, while the local firmware is set up in a different way.

Simple Checks Inside Windows Before You Change BIOS

Before changing low level firmware screens, it helps to confirm what Windows knows about the Trusted Platform Module.

This gives you a safer picture of whether you are dealing with a simple driver glitch, a firmware switch, or a lost chip.

Check TPM Status Inside Windows

Open Run dialog — Press Windows+R, type tpm.msc, and press Enter to open the TPM management window.
Read the status line — Look for a message that confirms a TPM is present or says that no compatible TPM can be found.
Note the version — If a chip is listed, check whether it reports TPM 1.2 or TPM 2.0, since newer Windows features expect version 2.0.

Use Device Manager To Refresh The Driver

In many cases Windows can see the chip but fails to load a clean driver instance.

You can let the operating system rebuild that connection in a few steps.

Open Device Manager — Right click the Start button and pick Device Manager from the menu.
Locate Security devices — Expand Security devices and look for an entry named Trusted Platform Module or TPM.
Reinstall the device — Right click the TPM entry, choose Uninstall device, restart the computer, and let Windows detect the chip again.

Scan For Updates And Firmware Fixes

Vendors often ship BIOS and firmware updates through Windows Update or their own utility, and some releases mention Trusted Platform Module fixes in the change log.

Run Windows Update — Open Settings > Windows Update and install pending quality and firmware updates.
Use the vendor tool — Many brands ship a support app that lists BIOS updates, chipset drivers, and security patches in one place.
Reboot after updates — Restart and see whether the alert tpm device is not detected warning still appears during boot.

If Windows tools show a healthy TPM 2.0 entry yet the startup alert persists, firmware settings are the next area to inspect.

Fixing The TPM Device Is Not Detected Message In BIOS

Most causes of this TPM warning relate to how firmware exposes the chip to the operating system.

The wording and exact keys differ by vendor, yet the path to turn the Trusted Platform Module back on follows the same pattern on most modern systems.

Enter Firmware Setup Safely

Shut down fully — Power off the PC instead of using sleep or hibernate, then wait a few seconds.
Use the setup key — Turn the computer on and tap the usual setup key such as F2, F10, Del, Esc, or F12 until a firmware menu appears.
Stay in read only mode first — Move through menus with arrow keys and do not clear or reset anything yet.

Enable The Security Device

Inside the firmware menu you need to locate the section that controls the Trusted Platform Module or its firmware based twin.

Find the TPM setting — Look under headings such as Security, Trusted Computing, Advanced, or similar.
Check for alternate names — On some Intel systems the option is called PTT, and on many AMD systems it is called fTPM.
Set it to enabled — Change the setting from Off, Hidden, or Disabled to On, Enabled, Available, or a similar active state.
Confirm TPM version — If a version drop down appears, pick TPM 2.0 instead of 1.2 when your hardware supports it.
Save and exit — Use the firmware on screen hint to save changes and restart back into Windows.

After this change the alert tpm device is not detected message should disappear, and Windows Security should show a ready security processor again.

Think Carefully Before You Clear The TPM

Firmware menus often include a control that clears the chip.

That action wipes encryption keys inside the Trusted Platform Module and can cut access to drives that rely on those keys.

Check for BitLocker — In Windows, open Control Panel > BitLocker Drive Encryption and see whether drive protection is turned on.
Locate recovery keys — Before clearing any chip, sign in to your Microsoft account or company portal and confirm that recovery keys are stored there.
Only clear when ready — Use the clear option in firmware only when you have backups, recovery keys, and a clear reason to reset the Trusted Platform Module.

What To Do When The Alert Appears After Updates Or Hardware Changes

Sometimes the alert TPM Device Is Not Detected text shows up right after a BIOS update, motherboard replacement, or storage upgrade.

In those moments it helps to retrace what changed on the machine and adjust firmware choices that may have reverted to factory defaults.

After A BIOS Or Firmware Update

Review release notes — On the vendor site, look for lines about security, TPM, or Intel PTT and note any new options.
Load defaults once — Inside BIOS, apply the Load Setup Defaults option, save, then re enter and enable TPM again.
Match boot mode — Confirm that UEFI, Secure Boot, and disk mode match the layout of your Windows installation so BitLocker does not trigger extra prompts.

After Motherboard Or CPU Changes

A new board or processor often brings a different Trusted Platform Module implementation, and existing BitLocker bindings may no longer match the chip.

Expect recovery prompts — Enter BitLocker recovery keys when Windows requests them after the first boot with new hardware.
Re enable encryption — Once the system is stable and the tpm device not detected alert is gone, turn BitLocker back on or run a system check so it trusts the new chip.
Update drivers — Install chipset and management engine drivers for the new platform to support firmware communication.

On Company Managed Devices

Business laptops often have extra rules that depend on TPM health.

If you see the alert on such a system, local fixes may be limited.

Contact support early — Let your help desk or admin know about the alert so they can check policy logs.
Avoid manual clearing — Wait for written approval before clearing any Trusted Platform Module keys on a managed device.
Stay on the network — Keep the laptop connected to the corporate network while they run remote checks or reissue keys.

How To Prevent Future TPM Device Not Detected Alerts

Once the system boots cleanly again, a few habits reduce the chance of the same alert returning at the worst moment.

These steps also protect data that depends on the Trusted Platform Module for safe storage.

Apply firmware updates calmly — Install BIOS updates only when the laptop is on reliable power and avoid hard shutdowns during flashing.
Keep security tools current — Let Windows Update and vendor apps deliver security and chipset drivers that relate to the TPM.
Store recovery keys safely — Save BitLocker and device recovery keys to a Microsoft account, Azure Active Directory, or a locked vault.
Note current firmware settings — Before large changes, take photos of Security and Boot screens so you can restore TPM options later.
Plan hardware swaps — When replacing a motherboard, plan for BitLocker recovery and a full backup, since the new TPM may not match the old one.

When To Suspect Hardware Damage

Most Alert TPM Device Is Not Detected cases come from settings and firmware, yet a small share point to a failing security chip or board.

Run vendor diagnostics — Use the built in hardware tests in your support app or firmware menu to scan for board faults.
Watch for other glitches — Note random shutdowns, USB ports that stop working, or fan control problems that appear together with TPM errors.
Plan repair steps — If tests report a board issue and the PC is still under warranty, open a ticket with the maker before trying independent repair shops.

With those checks and habits in place, the next time you see any tpm device not detected alert you can walk through checks calmly and fix it. A clear plan for firmware settings, drivers, backups, and support contacts turns a scary startup message into a short maintenance task that keeps your Windows device ready for daily work and protects sign in methods, encrypted drives, and sensitive files from lockouts. That small routine saves time on days and keeps logins smooth.