<https://discussion.enpass.io/index.php?/topic/27326-windows-hello-doesnt-work-on-system-boot-must-restart-enpass/page/2/#comment-77223>
<http://schema.org/text>
"As I already pointed out in the Beta forum, the issue might be related to the Infineon TPM. \n \n\n\n\thttps://discussion.enpass.io/index.php?/topic/21265-say-hello-to-full-time-windows-hello-with-enpass-beta-ver-650/&amp;do=findComment&amp;comment=38797\n \n\n\n\tI was not able to get it to work with Infineon. Only after I swapped it for a Nuvoton TPM, it started to work immediately. \n \n\n\n\tIn my case, Windows was throwing a certificate error for the Infineon TPM on each reboot. Look at your Windows event log if you see something like that once per reboot. That error was not related to Enpass at all, but to something which appears to be actually a problem of the TPM firmware itself. Even after clearing the TPM, the issue remained. The error said, that \"public and private key are not cryptographically bound\", which as far as I understood is one of the main things for which Enpass is looking. It was also showing an Infineon URI in the details tab and said that something is wrong with that. \n \n\n\n\tBecause this error was gone with Nuvoton TPM, and Enpass was also with that, I assume this is an issue of Infineons implementation. \n \n\n\n\t \n \n\n\n\tI also did a bit of research on this error and what it basically means is, that the TPM cannot provide attestation anymore that the private key was really generated by the TPM and never left it. Which appears to be crucial for Enpass Hello support. I saw that everyone posting screenshots is having Infineon TPM, which is why I think that might be the issue. \n "
<https://discussion.enpass.io/index.php?/topic/27326-windows-hello-doesnt-work-on-system-boot-must-restart-enpass/page/2/&tab=comments>