I appreciate that disabling Fast Start has helped some others, but as I have said previously, I tried it, and it didn't help me. In fact, since I was forced to reinstall Windows, Fast Start has been disabled.
I have just installed update KB5055523, with the hope Microsoft have finally fixed the issue ... they have not. It even appears that they have simply disabled facial biometrics on affected machines, as I tried the troubleshooter before going for the final desperate step of contacting MS Support. It deleted the biometric device, and after several reboots, it has not reappeared.
So ... I went through the painful process of asking MS support ...I gave them control of my machine for a couple of hours(!). They pretty much ignored all I told them, and went through everything I had already tried. I waited patiently, with the hope they would conclude it was an actual problem, and they would escalate to someone that would take it seriously, and had the power to escalate further ... the support guy got to the same point I did, and without warning, downloaded the Windows 11 ISO, and opened it ...I had to shout STOP (well, type), and explained that last time I tried this, I ended up with a BSoD and had to reinstall Windows, losing all my applications (but thankfully keeping all my data) .. he typed into Quick Assist that an in-place install would only repair and update ...I was just typing that I knew the theory, but it caused problems last time ...then Quick Assist promptly terminated, and I went back to the support portal (https://support.microsoft.com/home/contact), to find that he had closed my request!!!!! What a complete waste of time. showing the incredible lack of professionalism in Microsoft. I expect the closed case will show on his KPIs as a job well done!
Just updated to Win11 24H2 and it has killed Windows Hello!
I have an HP All-in-One 27-a275na.
All was working well under Win11 23H2 and just downloaded the ISO for Win11 24H2. Kept only my data to get the benefit of having the best possible install and then reinstalled only the latest versions of the apps I wanted.
Have checked for corrupted files (none found), deleted the Facial Recognition (Windows Hello) Software Device in Device Manager & Rebooted.
On restart the machine fails to start camera and asks for PIN and then when I try to setup Windows Hello Facial Recognition I get the Error Message " Sorry, something went wrong. Couldn't turn on Camera. Make sure it's working properly.
On checking the camera app it all appears to be working properly, and the windows settings allow apps to contact it!
Windows for home | Windows 11 | Accounts, profiles, and login
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
48 answers
Sort by: Most helpful
-
Anonymous
2025-04-11T10:53:50+00:00 -
Anonymous
2025-02-21T16:20:38+00:00 I found temporality disabling fast restart solved my issues with Windows Hello.
-
Anonymous
2025-02-21T09:38:58+00:00 Further update >>> I chose the Restore Point, and it corrupted my Windows to the point it would no longer boot. I had to go into Restore Options and choose to Reinstall Windows(!) At least I had the option to keep my files, but I have obviously lost all my installation (programs and settings), and I am permanently on the damned 24H2.
(yet another update to 24h2 today, which does nothing to resolve the problem) -
Anonymous
2025-02-16T12:28:25+00:00 Sorry, didn't spot you asked the question.
I am editing this, as I didn't recall Uninstall updates being difficult to spot 24H2, as I just replied (see below) ... despite 'Get Latest Updates' and 'Keep me up to date' being disabled, my laptop installed 24H2 yesterday. Choosing to uninstall KB5051987 did not remove 24H2, and I have no option to do so.
I thought about System > Recovery > Go Back, but that has no indication what you are going back to! Go. back to the previous version of Windows indicates that this will go back to Windows 10. I have no idea if that is right, as that should not be available after a couple of weeks, and I did it years ago, but I am not prepared to give it a go. My next option would be a Restore Point, but as I uninstalled KB5051987, I think it must have used up my allocated space, and the only restore point I have is from an hour ago .I now believe I am stuck with 24H2, and no way to go back :(
>>>> Re How to go back, but read the above >>>
Windows Update > Update history, and scroll down to the bottom to Uninstall Updates (which I am having to do yet again, as 24H2 has yet again disabled my Face Recognition).
My uninstall is only showing KB number (see Windows 11, version 24H2 update history, left side), but you can perhaps select by date. You will see below, I will be uninstalling February 11, 2025—KB5051987 (OS Build 26100.3194)
-
Anonymous
2025-01-18T11:18:52+00:00 Don't know about you, but my camera on HP Spectre x360 device from 2023 (Core i7 1355-U device) was installed with "Intel Image Process Unit Driver" and Camera is placed in Hardware Manager under Cameras under
but also under
.
What I also figured out, Intel Control Logic and Imaging Signal Processor are also somehow connected with the camera driver. Before update, camera was working, but could not be used in window hello, because IR-Camera was not working.
For me Update to Windows 11 24H2 caused BSOD-s in connection with Thunderbolt E-GPU.
Windows Update messed something with all those interconnected drivers - they all need to be in compatible versions, otherwise this could cause crashes of camera applications or in worst case BSOD-s.
I solved camera problem, but there are also somehow connected with the realtek sound adapter....something that I still seeking the solution. It's just a mess, what microsoft is doing with the updates. I'm not sure if that's the case for you, but manual delete of all those installed drivers and installing only the hp-ones solved the issues with camera - but you should perhaps disable windows update for drivers, because, if windows update updates one driver in the whole chain with the incompatible version - your back where you were. They just messed with the granularity and dependencies with the camera drivers....