Re:Potential impact of the Intel ME vulnerability
by wildmusings on Tuesday November 28, 2017 @09:30AM
(#15797556)
Have you tried running tpm.msc and resetting it? Maybe also try resetting it in the bios/firmware? Those seem to usually do the trick for solving TPM issues.
Re:Potential impact of the Intel ME vulnerability
by zaarn on Tuesday November 28, 2017 @09:59AM
(#15797774)
The issue was actually caused by changing the CPU, the TPM was then reset by the BIOS after the first powerup. I could try it again though.
From my previous experience, Windows will happily insert the decryption key into the TPM once you enter the recovery code.
Re:Potential impact of the Intel ME vulnerability
by wildmusings on Tuesday November 28, 2017 @12:09PM
(#15799071)
It usually will but I think there’s something about TPM ownership that sometimes requires manual reset through tpm.msc and/or firmware options.
For the few times in the month where I need Windows, it's not worth the effort.