08-29-2017 07:09 AM
I recently update my ThinkPad W550s from Win10 Version 1607 to Win10 Version 1703 build 15063.540 (Windows 10 Creators Update).
Fingerprint is not working after upgraded.
I just get "Your credentials could not be verified". I've tried uninstalling and reinstalling the driver (and I'm on the latest version), removing and re-registering my fingerprint...
Has anyone had this problem and managed to fix it?
Can you help me?
Solved! Go to Solution.
08-29-2017 11:35 AM
Does login by your PIN still work?
As a troubleshooting step - can you try creating a new user and see if you can get fingerprint working for that new user?
08-29-2017 11:18 PM
PIN login does not work ...
... I tried to create a new user and it works!
For now it seems to work, so I hope it's a definitive solution.
Thank you so much for now, I will keep you up to date.
08-30-2017 04:46 AM
So I think the issue must be about the PIN. Fingerprint works on top of PIN, so if PIN not working, then fingerprint can't possibly work either. On the broken user account, please try to delete both fingerprint and PIN, then create a new PIN, and finally create new fingerprints.
08-31-2017 10:51 PM
On the broken user account, please try to delete both fingerprint and PIN, then create a new PIN, and finally create new fingerprints.
Thank you so much.
That was driving me insane.
09-10-2017 02:14 AM
I have had the same problem on my Thinkpad P70 with the same version of Windows 10. I have updated the drivers, disabled and re-enabled the fingerprint reader device, removed my set of fingerprint scans, and tried setting up the new ones, either by creating a new account and/or PIN before starting the scan (Windows Hello then doesn't continue with the setup sequence), and by doing the scans and then creating the PIN (Window Hello exits without saving the scans or PIN). As you suggested, it does seem to be a problem with how the fingerprint works with the PIN, but in my case does not seem to be solvable. Is there anything else I can try other than just hoping future updates will sort the problem? John