This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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!
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.
This should be fixed in the July 2025 patch (update build > 26100.4351, along with any associated Microsoft Store UWP app updates).
If the issue still occurs (e.g., a crash in BioEnrollmentHost.exe), the problem may be with a video codec that was included in previous versions of Windows but now needs to be installed or provided.
How new do the cameras need to be to support this enhanced sign-in security you are speaking about here?
Im assuming a laptop that i bought this year in January would be considered fairly new since it supports the latest Windows Hello parameters.
And if the upgrade route youre mentioning would work, then mine would be working as this is what i did, without changing anything about the facial data and hence it should have been preserved. Yet it just didnt function properly.
A lot of work to be done by microsoft to fix this.
I didnt see that error anywhere btw.
New devices (Secured Core / CoPilot+ PCs) use "Enhanced Sign-in Security", which requires drivers and hardware that enable encryption/authentication at a low hardware level.
The error I mentioned is from the crash in the MFPLAT.DLL (Media Foundation Platform DLL).
The problem can be "fixed" from either Microsoft's side (add or handle codecs/encoding/resolutions as they did in Windows 10-11 23H2), or from the camera manufacturer's driver side (use or transcode to a 24H2 supported codec/resolution).
We opened a support case with Microsoft and paid the $500 fee, and still haven't heard anything in months. MS is unable or unwilling to fix this issue it appears. This issue affects our hybrid joined machines, they can't use Windows Hello Biometric options like face or fingerprint to login. We can't use our Yubico FIDO2 security keys to sign-in on Windows hybrid joined machines either after this update. We've basically been forced to eliminate the hybrid joined machines and convert them to Microsoft Entra joined instead, which doesn't have this issue. This has been a major hassle for us. We've essentially given up on Microsoft fixing this and have moved on.
