1 2 Previous Next 22 Replies Latest reply on May 30, 2016 6:08 AM by renaultr17

    Why won't Bitlocker work on NUC D34010WYK when it has TPM v2.0?


      When attempting to enable Bitlocker on a NUC D34010WYK, I receive the following error message:


      "The Trusted Platform Module (TPM) on this computer doesn't work with the current BIOS.  Contact the computer manufacturer for BIOS upgrade instructions."


      I have updated the system to the latest v25 BIOS for this board.  I have also contacted Intel about a dozen times regarding this issue, because the first 11 times, the Intel Technical Support representatives told me that the unit doesn't have a TPM or rather a "real" TPM.  What that means, I have no idea.  Not sure why "real" was denoted as the concept of a "fake" TPM is rather, difficult to understand.


      If the device did not have a TPM, then when I enter "TPM Administration" from Control Panel>Bitlocker, it would say, "No TPM device found", and that would be that, however, when I do access TPM Administration, it shows me that the system does indeed have a working TPM.  I enable it in BIOS and in Windows 8.1 (what I'm running), it states under the "Status" that "The TPM is ready for use, with reduced functionality".  I am able to 'Change the TPM owner password' or 'Clear the TPM to remove ownership and reset the TPM to factory defaults.'


      Under TPM Management on Local Computer, I have the following options: -Prepare the TPM

      -Change Owner Password

      -Clear TPM

      -Reset TPM Lockout


      Under TPM Manufacturer Information it states: 
      -Manufacturer Name:  INTC

      -Manufacturer Version: 9.5

      -Specification Version: 2.0


      Now, I understand that I can still manage to encrypt the drive using Bitlocker, so long as I create a group policy that bypasses the TPM, but we really would like to be able to use TPM.


      Now, the 12th Technical Support person was different and finally told me something different.  Instead of telling me that it didn't have a TPM, he said that the "Engineers are aware of this issue and are working on a fix.  I cannot tell you how long it will be before it's fixed, but I can tell you that they are working on it and it is a high priorty."

      Well, apparently, they have been working on it for over 2 months now.  I was hoping that one of these most recent BIOS update was going to fix this problem, but no luck. 

      Could someone at Intel please look into this if it isn't being looked into already and if it is, could you please get some kind of information regarding ETA on when this might be fixed?





        1 2 Previous Next