A
Arthur Pewty(2)
The above error has started appearing over the past 2 days. However, the system seems to be working just fine, should I be concerned or do anything?
I have several drives, all of which are Bitlocker encrypted and I have a motherboard with TPM enabled and apparently working just fine. No errors reported in the TPM troubleshooter, nor in the BIOS and everything looks fine. All the drives auto-unlock on boot, with me simply entering my pin at logon. So I assume the system is clearly reading the keys from the TPM chip without issue, or else the drives could not unlock, right?
I have checked the recovery keys manually, and they all work fine as well.
So I am a bit stumped as to what the Windows error is about? Should I just ignore it? The "fix" it would seem would be to disable Bitlocker and re-enable it. But that would take days since disabling it on C: will also require disabling it on the other drives, so we are talking tens of Terabytes. Understandably I am very, very reluctant to do that simply to sort out an event log error!
Any thoughts/suggestions?
Continue reading...
I have several drives, all of which are Bitlocker encrypted and I have a motherboard with TPM enabled and apparently working just fine. No errors reported in the TPM troubleshooter, nor in the BIOS and everything looks fine. All the drives auto-unlock on boot, with me simply entering my pin at logon. So I assume the system is clearly reading the keys from the TPM chip without issue, or else the drives could not unlock, right?
I have checked the recovery keys manually, and they all work fine as well.
So I am a bit stumped as to what the Windows error is about? Should I just ignore it? The "fix" it would seem would be to disable Bitlocker and re-enable it. But that would take days since disabling it on C: will also require disabling it on the other drives, so we are talking tens of Terabytes. Understandably I am very, very reluctant to do that simply to sort out an event log error!
Any thoughts/suggestions?
Continue reading...