TPM is Trusted Platform Module or, in other words, Trusted Platform Module technology.
TPM TRUSTED PLATFORM MODULE WINDOWS 10 HOW TO
How to know if our equipment is compatible.
![tpm trusted platform module windows 10 tpm trusted platform module windows 10](http://bestgamingpro.com/wp-content/uploads/2021/06/What-is-a-TPM-and-how-do-I-find-it.jpg)
This is a serious untold defect from both Gigabyte and Asus.
TPM TRUSTED PLATFORM MODULE WINDOWS 10 DRIVER
So the good question is: where can we find a UEFI-compatible driver that works for Windows 10 with Infineon chips ? We can't even find any firmware for the TPM module itself.ĭo we have other choice ? No (not even a TPM on USB key, which won't be recognized at boot time). which would invalidate our existing licences). It's really unfortunate because Both Gigabyte and Asus have made TPM 1.2 and TPM 2.0 modules (without saying in their documentation which one was working on their motherboard),Īnd they don't want to give any support for that (they want us to buy a new motherboard instead.
![tpm trusted platform module windows 10 tpm trusted platform module windows 10](https://1.bp.blogspot.com/-W-qNL-2lfd4/VHQBXNi7_OI/AAAAAAAAUy0/2ydh8YoGZiQldc4RjzGQvWY7rEiPOsXuACKgB/s200/OS%2BWindows%2B8.png)
This means that we need support from the motherboard firmware, but neither Asus, not Gigabyte provide a compatible BIOS version that supports TPM in UEFI boot mode !Īll we can do is to boot in "secure mode", but it's impossible to use the TPM. Module maker, but that device driver is NOT available from Infineon directly but only by its OEM: and neither ASUS, nor Gigabyte are listed. That device should then have a driver provided by the TPM Without the GPIO, it is impossible for the OS to enable and read the PCI configuratio, the device remains invisible, or should be activated only by the BIOS (which it does not in UEFI boot mode). Voltage and no connection at all on the TPM header (this means that the TPM module cannot support at all the GPIO protocol of TPM 1.2, and visibly this protocol is needed also by the BIOS. Indicate that there should be a jumper to configure the TPM 2.0 to 1.2 mode and enable the old legacy features allowed in TPM 1.2 but these chips have been soldered on the pluggable module without the jumper, and hardwired with a pullup resistor to a static Note that TPM 1.2 uses a special "GPIO" pin to enable some TPM functionn which is no longer needed in TPM 2.0 (the special vendor-specific functions are now standardized in the supported 2.0 standard, and TPM 2.0 modules (such as those by Infineon) Note that more recent versions of motherboards have a builtin TPM (and not a pluggable TPM header), and both Gigabyte and Asus have never specified in their dow the compatibility of their supported TPM modules (the motherboards were initially not designedįor Windows 10, which still did not exist officially even though it was in prerelease, the TPM was only tested for Windows 7, nothing spoke about the TPM 2.0 version at that time where only TPM 1.2 existed. Unfortunetely, I was completely unable to find any separate installable driver for Windows to properly detect the device and use it instead of the buitin Windows driver. It may also be an issue with the BIOS or UEFI driver in the motherboard, or the motherboard does not have a UEFI driver for the module, only a legacy BIOS driver, and the TPM does not work when booting in UEFI mode because it is not enumerated by the UEFI SLB9665TT2.0 chip) and which are those made for Gigabyte and Asus motherboard. This is most probably a bug in the builtin TPM driver coming with Windows itself, not compatible for example with a range of TPM modules made by Infineon (notably those using the Infineon You need to reset it a first time for less than 1/2 ms, then wait a bit, then reset it a second time and wait again: if you don't wait that time before you start sending other commands to it, the device will enter in self-protection mode and won't listen any Most probably Windows is not respecting the specs of the device and is trying to reset it too fast (TPM modules include a self-protection: It seems that we only see the TPM 2.0 transiently, then the device rapidely goes to some protection mode. If you have feedback for TechNet Subscriber Support, have the same issue. Please remember to mark the replies as answers if they help. We will try to analyze the log deeply for you. Once the log is collected, upload the log to OneDrive and paste the link here. HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Tpm /v Start /t REG_DWORD /d 0 /f To disable TPM logging, from an elevated command prompt, type: Log files start with 'tpm*' from '%SystemRoot%\System32\LogFiles\WMI'
![tpm trusted platform module windows 10 tpm trusted platform module windows 10](https://cdn.statically.io/img/cdn.wethegeek.com/wp-content/uploads/2021/10/trusted-platform-1024x576.jpg)
Temporarily stop the TPM driver logging and flush the buffer: 'logman stop tpm -ets'ĥ. Reg delete HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Tpm /v FileCounter /fĬhange to the directory '%SystemRoot%\System32\LogFiles\WMI’ Reg delete HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Tpm /v FileMax /f Reg add HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Tpm /v LogFileMode /t REG_DWORD /d 0x10000004 /f Reg add HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Tpm /v Start /t REG_DWORD /d 1 /f From an elevated command prompt, run the following commands: Please try to enable the TPM log to collect more information to troubleshoot this issue.ġ.