Re:Potential impact of the Intel ME vulnerability
by wildmusings on Tuesday November 28, 2017 @07:06AM
(#15796451)
You should use the manage-bde cli tool, or the bitlocker GUI, to remove the TPM protector and replace it with a passphrase. You’ll need to set one of the group policy options to enable using a passphrase.
Re:Potential impact of the Intel ME vulnerability
by zaarn on Tuesday November 28, 2017 @07:36AM
(#15796632)
Yeah but I don't want that. I want to use the TPM, Windows just broke it.
For the few times in the month where I need Windows, it's not worth the effort.
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.
But you still have to type it in.
I do this regularly as a recent W10 upgrade broke the SoftTPM in my Ryzen CPU (no longer recognised at boot), so I type it in everytime I boot windows (so once or three times a month).
It's very resilient since it has a built-in Error Detection Code for each 6 digit pair entered, if you make a typo, it likely will immediately complain and prevents entering any more of the code.