"Alert! TMP device is not detected" on 7720 Laptop
The 7720 laptop shows "Alert! TMP device is not detected" on turn on or restart. Options I get: " Press F1 key to retry. Press F2 key for setup utility Press F5 key to run onboard diagnostics"
With F1, It will just boot up normally. Butt it's really annoying to do every time.
This started all of a sudden with no clue to what caused it. I remember the day before this happened, that was my first time I used the "PC Health Check" to verify for Windows 11 compatibility. Could that be the cause, or there was a bios update, or maybe HW failure!
I tried updating to the latest BIOS version, still no luck. So not sure how to troubleshoot it.
@jhaaa When you ran PC Health Check, it might have triggered BIOS check at boot. Go into BIOS and under Security, check if the option TPM On is not check, you tick the box to check it, save and see if the error go away at reboot.
The reflashing did not work. I used the latest BIOS Firmware version application (Precision_7x20_1.22.0.exe), and even earlier versions. After the Windows reboots to do , I just get the usual TPM error. And when I select F1 to retry, it just boots back into Windows!
Now, with not being able to change the BIOS, this became more difficult.
I found that the laptop BIOS was last updated on November 2nd which is when I started to get the TPM error. So it seems the issue is caused by this update.
After research I found a way to rollback that update using Ctrl+ESC on startup. I tried it, and the rollback worked. But I'm still getting the TPM error, and the BIOS upgrade won't work.
I have the same problem with the same device number. i tried reflashing the bios, installing security apps of dell, runing tpd drivers, however nothing worked out!
Chino de Oro
11 Legend
•
8554 Posts
•
47161 Points
1348
0
Posted November 10th, 2021 19:00
@jhaaa When you ran PC Health Check, it might have triggered BIOS check at boot. Go into BIOS and under Security, check if the option TPM On is not check, you tick the box to check it, save and see if the error go away at reboot.