Fix Windows Hello Face Recognition Not Working
Most "Windows Hello face isn't working" threads jump straight to reinstalling drivers or nuking the biometric database. Half the time that's overkill for a problem that's really about lighting, a security change most people never heard about, or a camera that was never going to work with Hello in the first place. Before you touch a driver, figure out which of those three buckets you're actually in — it changes everything downstream.
Does your camera even support Windows Hello Face?
This is the check almost everyone skips, and it's the one that saves the most time. Windows Hello Face is not "any webcam plus software." Per Microsoft's own hardware guidance, it requires a camera specially configured for near-infrared (IR) imaging — a standard RGB webcam, even a good one, cannot do the 3D depth mapping Hello relies on. A $30 USB camera and a $300 one are equally useless here unless the listing specifically says it supports Windows Hello.
Confirm it in Device Manager: expand Cameras (or Biometric devices on some builds) and look for an entry that names an IR sensor, or a "Windows Hello Face" software device. If nothing like that shows up and you only see a generic "USB Video Device" or your laptop's normal webcam listed once, your hardware most likely doesn't support facial recognition at all, and no amount of driver reinstalling will fix that. Check your exact model's spec sheet from the manufacturer for "IR camera" or "Windows Hello face" support before spending another hour on this.
Why did face recognition suddenly stop working after an update?
If Hello worked fine for months and then broke after a Windows update, there's a specific, well-documented reason worth ruling out before anything else: starting with the update that shipped as part of Windows 11 build 26100.3775 in April 2025, Microsoft changed Windows Hello Face to require input from both the IR sensor and a color (RGB) camera, not IR alone. The change closed a spoofing vulnerability tracked as CVE-2025-26644, where adversarial input could fool the IR-only check. Microsoft has said this is intentional and won't be reverted.
The practical effect: facial recognition that used to work in a dark room, or with your webcam's visible-light lens covered or blocked, may now fail outright, even though your IR sensor is working perfectly. This is the single most common "it just stopped working" report for people on otherwise-healthy hardware, and it's the first thing to check before you assume something's broken.
If you cover your primary camera lens and leave only the IR window exposed — a common privacy habit — this is very likely your cause. Uncover the lens and get more ambient light before you try anything else.
There's a workaround some users apply: disabling the color camera entirely in Device Manager, which forces Hello back to IR-only mode. I wouldn't recommend it as your default move. You lose your regular webcam for every other app —Teams, Zoom, the Camera app —and you're deliberately opting back into the exact weakness Microsoft patched. It's a reasonable stopgap if you genuinely never use the webcam for anything else, not a fix to reach for first.
Rule out lighting and appearance changes before touching settings
Once hardware and the color-camera requirement are ruled out, work through the ordinary causes in order of how likely they are to be the actual problem, not how technical they sound:
- Harsh side lighting or strong backlight confuses the sensor. Face a light source rather than having it behind you.
- Certain makeup formulations behave differently under infrared than they look to your eyes, which can throw off recognition even though nothing "changed" from your perspective.
- Hats, high collars, or anything that shadows part of your face reduces the data Hello has to work with.
- A new haircut, new glasses, grown or shaved facial hair, or noticeable weight change are all legitimate reasons recognition gets flakier —not because something broke, but because your enrolled face template is now out of date.
For the appearance-drift case, Microsoft's own guidance is to use Improve recognition rather than re-enrolling from scratch: go to Settings > Accounts > Sign-in options > Facial recognition (Windows Hello) > Improve recognition. This adds an additional face template on top of your existing one instead of replacing it, which in practice recognizes you across a wider range of conditions —with and without glasses, for instance —rather than narrowing you to whatever you looked like at the last enrollment.
Symptom, confirming check, and fix
| What you're seeing | How to confirm it | What actually fixes it |
|---|---|---|
| "We couldn't find a camera compatible with Windows Hello Face" | Device Manager > Cameras shows no IR-capable device, or only a generic "USB Video Device" | Your hardware likely lacks a compatible IR camera; install the OEM camera driver (not the generic Windows one) if one exists, or use PIN/fingerprint instead |
| Worked fine before, now fails specifically in the dark or with the visible camera covered | Uncover the camera lens and try again in a lit room | This is the April 2025 color-camera requirement (CVE-2025-26644 fix), not a bug —improve lighting, or disable the color camera in Device Manager as a deliberate tradeoff |
| "Couldn't recognize you," inconsistent recognition | Try in different lighting and without accessories near your face | Settings > Accounts > Sign-in options > Facial recognition > Improve recognition |
| "Something went wrong with Windows Hello" at the lock screen, PIN still works | Device Manager shows the IR camera present with no warning icon | Restart the Windows Biometric Service: open an elevated Command Prompt and run net stop wbiosrvc then net start wbiosrvc |
| Setup won't complete, stuck on "make sure your face is centered" | Camera app can record video fine; only Hello enrollment fails | Remove the existing enrollment (Settings > Accounts > Sign-in options > Remove), restart, then set up again from a clean state |
| Facial recognition option is missing entirely from Sign-in options | Settings > Apps > Optional features > search "Windows Hello Face" | Install the Windows Hello Face optional feature if it's not present, then restart |
| Managed/work PC: Hello Face was working, now grayed out or absent | Run gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Biometrics | Confirm "Allow the use of biometrics" and "Allow users to log on using biometrics" are set to Enabled or Not Configured; an admin may have disabled this policy |
Do you actually need to reinstall the camera driver?
Only after the checks above come up empty. A generic "USB Video Device" driver where the OEM's actual Windows Hello-aware driver should be is a real and common cause, particularly on business laptops after a Windows Update replaces a vendor driver with a generic one. To check: Device Manager > right-click the camera > Properties > Driver tab, and look at the Driver Provider. If it says "Microsoft" where you'd expect the OEM name (Lenovo, Synaptics, Chicony, Sunplus, and similar names show up often for IR modules), go to the manufacturer's support site, get the specific driver for your exact model, and install it directly rather than trusting Windows Update to restore it.
If reinstalling the driver doesn't help and you suspect enrollment data itself is corrupted rather than the driver, Microsoft's guidance is to remove and re-enroll through Settings rather than manually deleting files under WinBioPlugIns —that folder holds files other system components expect to find, and hand-editing it can cause problems beyond just Hello. Use the Remove option in Sign-in options first; treat manual file deletion as a last resort you attempt only if Remove itself is failing.
When none of this applies to you
If your device never listed Windows Hello Face as an available sign-in option in the first place, this article isn't your problem —your hardware doesn't have compatible biometric hardware, full stop, and no driver or setting will add it. Similarly, if you're on a managed work device and IT has deliberately disabled biometric sign-in through policy, that's a decision above your access level, not a bug to troubleshoot; the Group Policy check above will confirm it, but changing it isn't something you can do from a standard user account.
One more distinction worth making: fingerprint readers use a separate part of the Windows Biometric Framework from facial recognition. If your fingerprint stopped working around the same time as your face recognition, don't assume it's the same root cause —they share a service (wbiosrvc) but fail independently for different hardware reasons.
For anything not covered above, run the built-in troubleshooter from Settings > System > Troubleshoot > Other troubleshooters, or work through Microsoft's own Windows Hello common issues and troubleshooting tips page, which stays current as Microsoft updates its guidance.