10-04-2024 09:32 PM - last edited 10-04-2024 09:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Hi all, hoping someone can help.
Ever since I got my Galaxy Book2 Pro laptop (i7, 16GB) I've used the fingerprint scanner to log in to Windows 11 (Windows Hello)
Now for some unknown reason, it is not working for login - the scanner still clearly works, but when I put my finger on it to login, it says "Your PIN is required to sign in".
I've tried adding more fingers in Windows settings, which works and reads the fingerprint OK, but I cannot log in using this method and have no idea how to fix it.
Any ideas?
Thanks
Solved! Go to Solution.
1 Solution
Accepted Solutions
08-05-2024 08:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I was trying to remove fingers previously from settings and then adding them back, which wasn't working. But then I thought about removing them, then restarting Windows and adding the fingerprints again in settings after the restart. This seems to have fixed it. Is this one of the types of fixed you've tried?
10-04-2024 10:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I put it down to Windows 11 and not so much Samsung. I couldn't be bothered trying to sort it out. It would be interesting to see if anyone has any idea on how to solve the problem though.
19-04-2024 01:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Thanks for the input.
I also put in my pin and it takes me straight in, but the fingerprint sensor is something I've become so used to, that putting in a pin feels archaic now, just as it does when using my Galaxy phone.
I can't think what has gone wrong but there must be a solution, as I say the fingerprint sensor still works, but not with the login process for some reason.
08-05-2024 06:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I am also having the same issue, it must be some sort of windows 11 update, that isn't compatible with the Samsung fingerprint driver. I have tried all types of fixes without success, haven't done the factory reset as I don't want to go that far. Maybe a Samsung driver update is required to fix this issue we are all experiencing.
08-05-2024 08:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I was trying to remove fingers previously from settings and then adding them back, which wasn't working. But then I thought about removing them, then restarting Windows and adding the fingerprints again in settings after the restart. This seems to have fixed it. Is this one of the types of fixed you've tried?
08-05-2024 08:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Brilliant Alex, that is the fix I was looking for. Did same as you and replicated fix. 😉
This should be the solution for everyone now and in the future.
Thanks
Brett
28-08-2024 11:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Hi there,
It sounds like your fingerprint settings might be tied to a specific security policy or recent update. Try these steps:
- Check Windows Hello settings: Go to Settings > Accounts > Sign-in options and ensure that "Fingerprint recognition" is turned on.
- Update drivers: Visit Samsung's support site to ensure your fingerprint scanner drivers are up-to-date.
- Re-register fingerprints: Remove all saved fingerprints and re-add them.
- Check for updates: Make sure both Windows and Samsung firmware are fully updated.
If the issue persists, consider resetting the fingerprint module in Device Manager.
Hope this helps!
28-08-2024 12:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Hi Hannan,
What ever caused this issue, whether an update or not, alex_ncfc was correct with his fix. It works brilliantly in solving this issue.
17-03-2025 05:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Mine stopped working after a Windows update, but the Alex suggestion worked like a charm.
