TPM For Windows Hello After Restart
Comments
-
Upgrading to the newest nightly did not fix the TPM issue for my intel based machines.
0 -
Hi @gussic,
Can you do the following for me, it'll let us know if your Windows Hello key are in the software provider or the TPM provider:
- Click start and search for
Powershell
, open it - Enter the following command:
certutil -csp "Microsoft Passport Key Storage Provider" -key -v | Select-String -Pattern "NgcKeyImplType"
- Does it output
1 (0x1)
or2 (ox2)
?
It should show something like
NgcKeyImplType: 1 (0x1)
if it is in hardware TPM provider.0 - Click start and search for
-
Hi @gussic,
Interesting. Could you send us your 1Password diagnostics report, it might explain what's going on.
Here's how to generate the report on Windows
Please email the report to
support+forum@1password.com
and in your email, also include:- A link to this thread: https://1password.community/discussion/122057/tpm-for-windows-hello-after-restart/p2
- your forum username: @gussic
Let us know here when you sent it, so we can look for it.
0 -
Thank you, I'll reply there.
0 -
FYI: This has worked well in the last 1-2 months, so thank you for the fix. Something I've noticed, though, is that whenever Windows 11 build is updated (Windows Insiders build), 1Password forgets the Hello configuration, and you need to type in your password to unlock one time, followed by the Hello authentication. After that it works correctly until a new Windows build is installed. Not sure if this is something that could even be handled by 1Password - in any case it may not be a high prio issue, however, it might also affect users installing larger Windows updates that occur 1-2 times per year.
0 -
From what I observed in the last months, the TPM saved password was always forgotten after a system reboot that was required by Windows Update. It was not (as far as I remember never) forgotten after manual shutdown/reboot/restart initiated by myself.
0