Can t Turn My Computer on Sorry Something Went Wrong Please Try Again
Sorry, something went wrong on Windows Hello for Business Fingerprint
I take random issues on older laptops, where Fingerprint commuter is recognized, but when trying to enroll the finger, it displays me "Sorry, something went wrong...". I have 2 like laptops with exact same fingerprint driver, one accepts fingerprint, some other ane does not. I call up I had no bug with information technology in 1909 and 20H2 builds, but I at present run into this with 21H1.
Finally got it on all laptops!
-
Check and remove if whatsoever fingerprints are left in Sign in pick.
-
Go to Device manager and uninstall device. Click the suboption to uninstall device from this system.
-
Reboot the auto
-
Get back to sign in options and re-enroll the finger. If it fails, repeat the entire procedure again with rebooting.
I think this commuter is partly faulty I have here, but I take no chance to apply another i. I tried to crook newer commuter to accept this device past adding my hardware id into .inf file, simply information technology didn't workout.
@yannara Thanks for posting in our Q&A. From your description, I know that windows Hello for Business organisation Fingerprint doesn't piece of work in windows 10 21H1, just it works in other versions such every bit 1909 and 20H2 builds. If there is anything misunderstanding, please right me.
To clarify this issue, we appreciate your help to try to manually ready the fingerprint in a windows 10 21H1 device that not enrolled in intune and check if it works.
If in that location is anything update, feel complimentary to let u.s.a. know.
If the response is helpful, please click "Accept Answer" and upvote information technology.
Note: Please follow the steps in our documentation to enable email notifications if you want to receive the related email notification for this thread.
Ahh okay, and then this is a known problem in 21H1? Will there be a fix for that and in what time schedule? Thanks!
0 Votes 0 ·
@LuDaiMSFT-0289 since this behavior is random, it would be very time consuming to test this manually, because it might work. Any other ideas?
0 Votes 0 ·
@yannara With the limitation resource, it is hard to make certain if it is a known event, because this consequence is non only related to intune, simply also related to windows itself.
Given this state of affairs, it is suggested to open an online ticket to double ostend and feedback this issue more quickly. Information technology is free. Here is the online support link and promise it helpful.
https://docs.microsoft.com/en-us/mem/intune/fundamentals/get-back up
At the aforementioned time, I will besides feedback this issue.
Thank you for understanding.
0 Votes 0 ·
@LuDaiMSFT-0289 certain, I will try to discover 20H2 media and install the problematic unit with this and enroll it into Intune. I am pretty sure information technology is about the build itself.
0 Votes 0 ·
Prove more than comments
@LuDaiMSFT-0289 I just want to confirm that I did a test on 20H2 and the problem is the aforementioned, so it is not about the build itself. The device and driver nosotros are talking about hither is this:
USB\VID_138A&PID_003D
@yannara Thanks for the update.
Based on your test effect, the different version devices that have the same driver occurs the same trouble. Did the devices that can use Windows Hello for Business organization Fingerprint successfully have the aforementioned commuter or another one?
0 Votes 0 ·
This problem occurs simply on spesific HP Elitebook family with exactly same driver. Some of computers are okay, some are not.
0 Votes 0 ·
This is weird, but because these devices are quite erstwhile, I approximate I can treat this as a solution. Not every finger tin can be enrolled, so basically when I get "something gets wrong", I try some other finger, I might laissez passer or not, if not so some other finger and finally some finger gets accepted. It might be hardware problem with reader or something. Eventually, I managed to enroll all devices with "SOME" finger, but my indexing finger is non good :D
@yannara Hahaha, I never thought it would be such an interesting phenomenon. I retrieve your method is worth trying for someone with the same problem.
Cheers for your fourth dimension to test and feedback. :D
i Vote one ·
I un-accepted my previous answer, because I came up again with the aforementioned problem, where machines were re-installed and users changed, and I noticed, that fifty-fifty the 2nd or third finger is applied, it will fail to accept it during logon. So, this happends on Windows 10 21H1 Intune deject-simply managed.
I took this HP Elitebook 2107p and installed it with my SCCM, using on-prem setup and Windows 10 1909 build. Fingerprint works like a charm, with a beginning finger! In my onprem lab, the commuter for Fingerprint is Synaptics FP Sensors 4.5.307.0. In a cloud setup, it is newer. In a cloud, drivers comes from MS Catalog.
I can side by side practise the exam past servicing 1909 to 21H1 via SCCM and meet what happends.
Source: https://docs.microsoft.com/en-us/answers/questions/505608/sorry-something-went-wrong-on-windows-hello-for-bu.html
This worked for me! Thanks!
1 Vote 1 ·
Worked for my Dell G5 Goodix fingerprint problem. Cheers a million!
1 Vote 1 ·
*uninstall biometric driver from device manager
*open grouping policy editor >> computer configuration>>Administrative Templates>> Windows Components>>Biometrics>> Allow the use of biometrics( set up enabled)>> Allow users to log on using biometrics ( ready enabled)
*restart your laptop and go to BIOS
*In BIOS go to boot option>> articulate secure kick keys (gear up enabled)>> relieve and exit
*Go to device manager, scan for hardware changes, at present install your biometrics, it should work fine
0 Votes 0 ·