Windows 10: Reset TPM failed, resulting in slow login (have PTT not TPM)

I have a Lenovo Ideapad 710s. It has Intel PTT (Platform Trust Technology) rather than a dedicated TPM chip.

I got a Windows security center alert telling me that I needed to reset my security processor (clear TPM), so I did, clicking the "clear and restart" button. My computer rebooted, but I didn't get any prompt about clearing the TPM, and when I got to the Windows 10 cover screen and clicked to get to the login screen, it took about 2 minutes for the login boxes to appear. It now does this every time I reset the computer. Further, the TPM security alert is still there, so the reset failed.


I have checked my bios and it's the latest version. I went into the bios to double-check that I don't have TPM, and the only related security option is one to turn PTT on or off. And when I go to tpm.msc, it verifies that this computer doesn't have TPM.


I don't really care about whether my PTT/TPM gets cleared, I just want my login screen to stop taking so long to appear. Please help!


Thanks,

Sarah

:)

 

TPM update

Don't know if this is the right place for this thread but whatever, laptop informed me that " a firmware update is needed for you security processor (TPM)," now, i looked up what to do and from a microsoft support thing, the last step says to clear the tpm. it has a warning saying to back up my data, i would like to know what clearing the tpm does, and what measures i need to take to make sure nothing goes wrong.

 

Clear tpm

Hi I'm trying to reset my laptop to factory settings and its saying clear TPM. Or configuration change was requested for this computer's TPM.

 

TPM update

From m$

"The Clear-Tpm cmdlet resets the Trusted Platform Module (TPM) to its default state. A reset removes the owner authorization value and any keys stored in the TPM. To reset a TPM, you must provide a valid owner authorization value. You can enter an owner authorization value or specify a file that contains the value. If you do not provide a value, the cmdlet attempts to use a value stored in the registry."

Best measures would be a backup, or clone, similar type of save.

Look here