You lift the lid, look at the screen, and wait — but the little “looking for you” animation spins and gives up, or Windows Hello tells you it couldn’t recognize you at all. PIN still works, so you are not locked out, but the passwordless sign-in you bought the Copilot+ PC for is gone.

On AI PCs and Windows on ARM, Windows Hello face depends on a precise chain: the IR camera and emitter, the OEM camera driver with Hello extensions, camera privacy permissions, and the enrolled biometric template stored in the TPM. Break any link — a driver swap after an update, a privacy toggle, a corrupted template — and face unlock fails while everything else keeps working. The NPU that accelerates on-device AI does not do the face matching itself; the secure pipeline runs through the camera hardware and the TPM.

This guide gives you six fixes in technician order: hardware and privacy checks first, then driver repair, then re-enrollment, ending with the TPM and firmware layer. Work through them in sequence and test face sign-in after each step.

Why this happens

  • IR camera driver replaced or missing: Windows Update can swap your maker’s validated IR camera driver for a generic one without the Windows Hello extensions — face unlock silently dies while the camera still works in Teams.
  • Camera privacy settings blocking access: If camera access is off for the device or for system components, the Hello pipeline never receives frames, and the failure message blames recognition instead of permissions.
  • Corrupted biometric template after an update: Major Windows updates occasionally invalidate the stored face template in the TPM; the camera works fine, but there is nothing valid to match against.
  • Physical camera kill switch or shutter engaged: Many Copilot+ laptops have a function-key camera toggle or a physical shutter — the fastest cause to check and the most embarrassing to miss.
  • Lighting or positioning changed: Glare, strong backlight, or a new seating angle can push the IR capture outside its trained tolerance, especially right after a fresh enrollment in different conditions.
  • TPM or biometric service fault: The face template lives in the TPM and the matching runs through the Windows Biometric Service; a stalled service or TPM hiccup breaks enrollment and recognition together.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check the shutter, kill switch, and basic camera function

Before touching drivers, confirm the camera hardware is actually available. A surprising share of “Hello stopped working” cases are a physical shutter or an Fn-key toggle.

  1. Look for a physical camera shutter slider above the screen and make sure it is open.
  2. Press the camera function key (often Fn+F8 or a dedicated camera key — check your keyboard icons) to ensure the camera is not software-disabled at the firmware level.
  3. Open the Camera app: if it shows a black screen or “camera not found,” the problem is hardware/driver level, not Hello-specific — continue to Fix 3.
  4. If the Camera app works, open Settings > Bluetooth & devices > Cameras, select your camera, and confirm it is enabled.
  5. While in a lit room, also note whether the small IR emitter glows faintly red when Hello attempts — no glow suggests the IR unit specifically is down even if the visible camera works.

Fix 2: Verify camera privacy and sign-in options settings

Windows can block the Hello pipeline at the permission layer even when the Camera app works. Two settings pages matter, and both are quick to check.

  1. Open Settings > Privacy & security > Camera and confirm Camera access and Let apps access your camera are both On.
  2. Scroll that page and make sure nothing Hello-related is denied — system components need access, not just Store apps.
  3. Go to Settings > Accounts > Sign-in options > Facial recognition (Windows Hello) and confirm it shows as set up rather than erroring.
  4. If sign-in options show “Something went wrong,” do not re-enroll yet — the error usually means the driver or service underneath is broken; continue to Fix 3 first.
  5. Restart the laptop after changing privacy settings, then test face sign-in at the lock screen (Win+L) rather than only in Settings.

Fix 3: Reinstall the OEM IR camera driver

This is the fix that resolves most cases: the generic driver Windows Update installed handles video calls but lacks the infrared and anti-spoofing path Hello requires. Your maker’s driver restores it.

  1. Open Device Manager > Cameras (and Imaging devices on some models) and identify the IR camera entry — “Intel AVStream Camera” or similar on Intel AI PCs, vendor-specific names on Snapdragon machines.
  2. If you see a yellow warning icon or only a generic “USB Video Device,” the correct driver is missing.
  3. Download the camera/IR driver package for your exact model from Dell , HP , or Lenovo support — get the Windows 11 on ARM package for Snapdragon models.
  4. Install it as administrator, restart, and recheck Device Manager for a clean device with no warning icon.
  5. Test Hello at the lock screen. If it now attempts recognition (even if it fails to match), the pipeline is alive — proceed to Fix 4 to re-enroll.

Fix 4: Remove the old face data and re-enroll cleanly

A template enrolled under different lighting, or corrupted by an update, will never match no matter how good the driver is. Deleting and re-enrolling builds a fresh template against the current hardware state.

  1. Go to Settings > Accounts > Sign-in options > Facial recognition (Windows Hello) and click Remove to delete the stored face data.
  2. Restart the laptop — this clears any cached biometric state in the service.
  3. Click Set up, then Get started, and follow the enrollment in the lighting where you normally sign in (your desk, not a bright window behind you).
  4. Keep your face centered and still during the capture; move slightly when prompted so the IR sensor maps multiple angles.
  5. After enrollment, lock with Win+L and test three times. If recognition is flaky, click Improve recognition and add captures in a second lighting condition.

Fix 5: Restart the biometric service and check TPM health

When enrollment itself errors out or recognition fails with a healthy driver and fresh template, the Windows Biometric Service or the TPM may be at fault. Both are repairable without reinstalling Windows.

  1. Press Win+R, type services.msc, and find Windows Biometric Service — restart it, and set its startup type to Automatic if it was disabled.
  2. Open Windows Security > Device security > Security processor details and confirm the TPM reports ready with no errors.
  3. If the TPM shows an issue, run the troubleshooter there or clear it per the steps used for TPM firmware updates that fail mid-install — a stale fTPM state breaks the secure template store Hello depends on.
  4. After the service restart or TPM repair, re-enroll your face once more (Fix 4) so the template is written to a healthy store.
  5. Test at the lock screen. Persistent “couldn’t turn on the camera” errors at this point point to firmware — check your maker for a BIOS update.

Fix 6: Rule out system-level interference and reset Hello

If face unlock still fails with good drivers, a fresh template, and a healthy TPM, something at the system level is interfering — or the Hello configuration itself needs a full reset.

  1. Temporarily disconnect USB webcams, capture devices, and docks — an external camera can hijack the default device Hello binds to, the same class of device-confusion that makes audio interfaces misbehave on ARM laptops .
  2. Check Settings > Windows Update for pending updates, including optional driver updates — a newer IR driver may already be queued.
  3. In an elevated PowerShell, run Get-WindowsHello diagnostics if available, or simply remove all Hello methods (face, fingerprint, PIN), restart, and re-add them in order: PIN first, then face.
  4. If a specific AI workload recently started failing too — for example Hugging Face models erroring on the NPU — treat it as a platform-driver problem and reinstall the full OEM driver bundle, not just the camera piece.
  5. As a final step before hardware suspicion, use Settings > System > Recovery > Reset this PC (keep my files); if Hello fails on a clean system, the IR camera hardware needs a warranty repair.

Closing

Windows Hello face on an AI PC fails at one of four links: the shutter or kill switch, camera privacy, the IR camera driver, or the enrolled template. Check the physical switch first, reinstall the OEM camera driver second, and re-enroll in your real lighting. The chain is short, and a methodical pass through it restores face unlock in nearly every case.

Frequently asked questions

Why does Windows Hello say my face can't be recognized?
The usual causes are a disabled or outdated IR camera driver, camera privacy settings blocking the sensor, poor or backlit lighting, or a corrupted biometric template after a major update. Re-enrolling your face after fixing the driver resolves most cases.
Can I use Windows Hello face without an IR camera?
No — secure Windows Hello face sign-in requires an infrared camera plus the standard camera for anti-spoofing. If Device Manager shows no IR camera device, the hardware may be absent or its driver missing, and face unlock cannot work.
Does a Windows Update break Windows Hello face?
It can. Updates sometimes replace the OEM IR camera driver with a generic one that lacks the Hello extensions, or reset camera privacy permissions. Reinstalling the maker’s camera driver and re-checking privacy settings usually restores it.
Why does face unlock work in daylight but fail at night?
The IR camera handles darkness fine, so night failures usually mean the IR emitter or sensor driver is partially broken — Windows falls back to the visible-light camera, which needs light. Fix the IR camera driver rather than adding a lamp.