Windows Hello Fingerprint Not Working: Complete Fix List

Layer-by-layer fix list for Windows Hello fingerprint failures: re-enroll, drivers, TPM, NGC vault, hardware.

Published 2026-06-29 by LaptopTestOnline Editorial Team

Windows Hello Fingerprint Not Working: Complete Fix List

Windows Hello fingerprint authentication is brilliant when it works and uniquely frustrating when it doesn't. The Hello stack involves a sensor, a driver, the Windows biometric framework, and a credential vault — and a problem at any layer breaks the whole flow. Here is the order in which to attack each layer.

Step 1: Verify the sensor is alive

Open our Fingerprint Test. It uses the WebAuthn API and Windows Hello as the verifier. If our test successfully prompts you and accepts your finger, the hardware and OS pipeline work. If our test reports "No platform authenticator available," the OS doesn't see the sensor — start at step 2.

Step 2: Re-enroll the fingerprint

Most "Windows Hello can't recognize you" cases are solved by deleting all enrolled fingers and re-enrolling. Skin condition, finger position, and sensor calibration drift over months.

Settings → Accounts → Sign-in options → Fingerprint recognition → Remove. Then enroll again, taking care to:

• Cover the entire sensor area with the pad of your finger, not the tip.
• Vary the angle slightly across the enrollment samples.
• Enroll the same finger twice as "left thumb" and "left thumb 2" for redundancy.

Skin oil and minor cuts change the print enough to confuse a single enrollment. Two enrollments per finger boosts the match rate dramatically.

Step 3: Update the fingerprint driver

Device Manager → Biometric devices → right-click the sensor → Update driver → "Search automatically." If Windows finds nothing newer, visit your laptop manufacturer's support page and install the latest fingerprint driver for your exact model. Use the OEM driver, not the generic one Windows installs.

On ThinkPads this is usually "Synaptics WBF Fingerprint Reader." On Dell, "Goodix" or "Validity." On HP, often "Synaptics SGX."

Step 4: Reset the Windows Hello credential vault

Sometimes the Hello container itself becomes corrupt. The fix is destructive (it removes all stored biometrics for all users on the machine) but reliable.

1. Run PowerShell as administrator.
2. cd C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC
3. Delete the contents of the NGC folder.
4. Restart and re-enroll.

If you get "access denied," take ownership of the folder first using takeown /f NGC /r then icacls NGC /grant administrators:F /t.

Step 5: Check the Windows Biometric Service

Press Win + R → services.msc → find "Windows Biometric Service." Confirm:

• Startup type: Automatic.
• Status: Running.

If it won't start, the next step (driver reinstall) usually fixes it.

Step 6: Clean reinstall the driver

Device Manager → Biometric devices → right-click → Uninstall device → check "Delete the driver software." Restart. Install the OEM driver fresh.

If the sensor disappears entirely from Device Manager after uninstall and doesn't return after restart, it's almost certainly a hardware or cable issue (step 10).

Step 7: TPM and Hello configuration

Windows Hello uses the TPM to store credentials. If the TPM is misconfigured, Hello refuses to enroll at all.

Run PowerShell as administrator and check:

Get-Tpm

Confirm TpmReady: True, TpmPresent: True, Enabled_InitialValue: True.

If the TPM is disabled, reboot into BIOS and enable it (often called "Intel PTT," "AMD fTPM," or "Security Chip"). As a last resort you can run tpm.msc and "Clear TPM" — but treat this as destructive: clearing the TPM erases all TPM-protected keys, including BitLocker. Before clearing, back up your BitLocker recovery key (or suspend BitLocker), make sure you can sign in another way, and expect to re-enroll Windows Hello and other credentials afterwards.

Step 8: Account type compatibility

Windows Hello biometric sign-in requires either a Microsoft account, an Entra (Azure AD) account, or a local account with a PIN already configured. If you're on a pure local account with no PIN, set up a PIN first (Settings → Sign-in options → PIN) — Hello will then unlock.

Step 9: Group Policy lockout (work or school PCs)

If you're on a managed device, your IT department may have disabled biometric sign-in via Group Policy. Quick check: gpresult /h gp.html → search for "Allow domain users to log on using biometrics" or "Use Windows Hello for Business."

If you find a policy disabling Hello, the only path is asking IT to enable it.

Step 10: Hardware diagnostics

If software steps don't restore the sensor:

• Boot a Windows installation USB into recovery and try fingerprint enrollment from a clean environment.
• On laptops with a fingerprint sensor integrated into the power button, the sensor may have failed even though the button still works.
• Open Device Manager → View → Show hidden devices. If the sensor appears as "unknown device" with code 43, it's likely a hardware failure.

Replacement involves swapping the fingerprint module (which on integrated power-button designs means the entire palm-rest assembly — expensive, typically $80–$200 in parts).

Step 11: macOS Touch ID parallels

The same logic applies on Macs:

• Touch ID failures after macOS updates → re-enroll all fingers.
• Persistent failures → reset Secure Enclave-stored data with sudo bioutil -p.
• Touch ID sensor on the keyboard is integrated; failure usually means keyboard replacement.

Why fingerprint sensors fail more on dry skin

Capacitive fingerprint sensors read the tiny variations in skin moisture between ridges and valleys. Very dry skin (winter, frequent sanitizer use), recent injuries, or persistent calluses produce inconsistent readings. Solutions:

• Use a tiny dab of moisturizer on the finger pad 5 minutes before scanning.
• Enroll the same finger 2–3 times across different conditions (dry, after washing).
• Avoid scanning immediately after eating or hand washing — water on the sensor confuses the reading.

Quick triage

Run our Fingerprint Test after each step to confirm progress. The browser test isolates whether the hardware and Windows pipeline are working, separately from any specific app or account problem.

Try related tests

• fingerprint test

Back to all guides