Z170 K4/D3 with a TPM

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello all, I just wanted to post this here for anyone searching for the issue. The K4/D3 Fatal1ty mainboard with the P710 UEFI version with the compatible 2.0 TPM module has some issues when being used with OPAL tools or Bitlocker. 

If for some reason it stops appearing on the UEFI menu or the operating system, remove, reset to UEFI defaults, reboot, reinsert the TPM module, then repeat and it should appear again. This was a weird issue.

Then if it errors out inside the operating system, especially in windows 10, make sure to first set the group policy for encryption in windows to either 128 bit if you selected SHA-1 on the UEFI or 256 if you selected SHA-2. The OS has very little control over the settings so they must match or some odd, undocumented errors will happen when trying to use encryption.
As a side note, SHA-2 and 256 bit encryption are probably not supported by the TPM 1.2 version, but I can't confirm this since I haven't tried that version.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MX16 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 24 May 2017 Status: Offline Points: 5	Post Options Post Reply Quote MX16 Report Post Thanks(0) Quote Reply Topic: Z170 K4/D3 with a TPM Posted: 24 May 2017 at 2:25pm
	Hello all, I just wanted to post this here for anyone searching for the issue. The K4/D3 Fatal1ty mainboard with the P710 UEFI version with the compatible 2.0 TPM module has some issues when being used with OPAL tools or Bitlocker. If for some reason it stops appearing on the UEFI menu or the operating system, remove, reset to UEFI defaults, reboot, reinsert the TPM module, then repeat and it should appear again. This was a weird issue. Then if it errors out inside the operating system, especially in windows 10, make sure to first set the group policy for encryption in windows to either 128 bit if you selected SHA-1 on the UEFI or 256 if you selected SHA-2. The OS has very little control over the settings so they must match or some odd, undocumented errors will happen when trying to use encryption. As a side note, SHA-2 and 256 bit encryption are probably not supported by the TPM 1.2 version, but I can't confirm this since I haven't tried that version.