Windows 10 Pro; TPM v1.2 working, TPM v2.0 doesn't

Question

Our IT Techs are sending assets (laptops) back to HP for repair. The assets came with TPM v1.2 installed and when they come back, they are loaded with TPM v2.0 and we have not been able to encrypt the disk after the change of TPM. Is there a fix or workaround anyone knows of to resolve this issue other than to request HP place TPM v1.2 on the build they send back. 
 
 Thank You

MichaelMcLannahan · Accepted Answer

Hello Joseph! 
 
 TPM is actually hardware - It's a module/chip within the computer that helps aid the security functions of the device. TPM 2.0 is the "current" standard and has replaced 1.2. 
 Often (although not always) TPM 1.2 can be flashed/upgrade to 2.0. 2.0 is enhanced in features and more secure than 1.2 and ideally you should want your estate to be 2.0 based for this reason. 
 
 SafeGuard (and BitLocker that SafeGuard manages) is FULLY TPM 2.0 compliant and this configuration/hardware should NOT present an issue at all. 
 
 Are you saying that you're sending the devices back to HP encrypted- They then repair and when the laptop returns they've flashed the TPM to 2.0 (or they've changed the motherboard)? 
 
 What doesn't work exactly? Are you trying to re-encrypt the devices and they don't - or TPM 2.0 devices don't encrypt at all - but 1.2 do? 
 
 We can work through this but rest assured you do NOT need to downgrade to 1.2 for SafeGuard or Bitlocker to work.

MichaelMcLannahan · Answer

Are the devices attempting to encrypt, and failing/erroring or not even doing that? 
 If you enable BL manually on the device - what happens? 
 At an elevated command prompt "manage-bde c: -on"