Fingerprint reader not working in Windows 11 — Windows Hello asking for PIN instead of accepting a fingerprint, the fingerprint reader not being listed anywhere in device settings, or enrollment failing — is a common issue with a few distinct causes depending on whether the reader has ever worked or stopped working unexpectedly. We go deeper on the whole subject in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Which situation applies to you?
- Fingerprint reader never worked on this machine: driver installation, hardware support, or the feature is disabled in BIOS
- Was working, stopped after a Windows Update: typically a driver regression — the update installed a generic driver
- Fingerprint enrolled but not accepting: stored biometric data may have become corrupted; re-enrollment usually fixes this
- No fingerprint option in Windows Hello settings: the reader isn’t detected by Windows at all
Fix 1: Re-enroll the fingerprint
This is the quickest fix when the reader hardware is detected but doesn’t accept a registered fingerprint. Settings → Accounts → Sign-in options → Windows Hello Fingerprint → Remove → then set it up again from scratch. Windows stores biometric templates locally; re-enrolling creates a clean template that resolves false rejections and inconsistent reads.
Enroll multiple orientations of the same finger (straight, slight left, slight right, tip) during setup — this improves recognition accuracy and reduces false rejections in real use. The setup wizard suggests re-positioning; going through this carefully gives much better daily performance than rushing through with a single flat orientation.
Fix 2: Driver installation
Device Manager → Biometric Devices — the fingerprint reader should appear here. If absent: the driver isn’t installed. If present with a yellow triangle: the driver has an error.
For laptop built-in readers: the driver comes from the laptop manufacturer’s support page, not Windows Update. Search for your laptop model + “fingerprint driver Windows 11.” Common fingerprint reader manufacturers: Synaptics, Goodix, Elan, FPC — each requires the specific driver version for your laptop model. Windows Update’s generic fingerprint driver often doesn’t work correctly for specific hardware.
After installing the correct driver: restart → check Device Manager for successful installation (no yellow triangle, device name shows correctly) → then re-enroll fingerprints.
Fix 3: BIOS/UEFI fingerprint reader setting
Some laptop manufacturers allow the fingerprint reader to be disabled in BIOS for security. If the reader doesn’t appear in Device Manager at all (even after driver installation attempts): enter BIOS (F2 or Delete at startup) → look for “Fingerprint Reader,” “Biometric Device,” or “Security” section → confirm the fingerprint reader is enabled.
Fix 4: Windows Hello service repair
The Windows Biometric Service manages fingerprint authentication. If it crashes or stops: enrolled fingerprints can’t be used. Win+R → services.msc → “Windows Biometric Service” → right-click → Restart. If stopped: right-click → Start. After restarting: lock the screen (Win+L) and test fingerprint unlock.
net stop WbioSrvc
net start WbioSrvc
Administrator Command Prompt achieves the same with these two commands. After restarting the service: re-test fingerprint login immediately.
Fix 5: Clear the biometric database
Windows stores biometric templates in a local database. When this database becomes corrupted: fingerprint authentication fails consistently even after re-enrollment. The database is at:
C:WindowsSystem32WinBioDatabase
To reset: stop the Windows Biometric Service (services.msc → Windows Biometric Service → Stop) → navigate to the WinBioDatabase folder → delete all files inside (not the folder itself) → restart the service → re-enroll fingerprints. This forces Windows to create a fresh biometric database, resolving corruption that normal re-enrollment doesn’t fix.
Clean finger for better recognition
The fingerprint reader needs good contact to create an accurate template. Before troubleshooting software: clean the reader sensor with a dry cloth → ensure your fingertip is dry and clean when testing. Dry, calloused, or wet fingers reduce recognition accuracy. If recognition improved with a clean finger: the issue was physical, not software.
Our guide on Windows Hello PIN issues covers the PIN fallback that’s available when fingerprint authentication fails, and the Windows Hello configuration issues that affect both PIN and biometrics. For device driver issues that affect biometric devices alongside other hardware, our driver troubleshooting guide covers the Device Manager investigation approach. Microsoft’s Windows Hello documentation covers the biometric data security model, how templates are stored and protected, and the specific requirements for using fingerprint authentication in secure environments.
External USB fingerprint readers
USB fingerprint readers (for desktops that don’t have built-in readers) work through a standard HID driver in most cases. Plug in → Device Manager → Biometric Devices — it should appear. If it appears as “HID-compliant device” rather than by manufacturer name: Windows is using the generic HID driver, which works for basic fingerprint enrollment but may lack advanced features. The manufacturer’s driver (often included on a small disc or downloadable from their website) provides the proper device name and better performance.
For USB readers that don’t appear anywhere in Device Manager even when plugged in: try a different USB port, try the device on another computer to confirm it’s functional, and check whether the manufacturer provides Windows 11 compatible software (some older USB fingerprint readers stopped receiving Windows 11 drivers).
Fingerprint authentication after domain join
Joining a Windows machine to an Active Directory domain can reset Windows Hello fingerprint settings. Domain administrators can configure Windows Hello for Business policies that supersede local Windows Hello settings — requiring specific hardware security levels (TPM 2.0), mandatory multi-factor authentication, or limiting which biometric types are allowed.
If fingerprint authentication stopped working after domain join: check with IT. They may need to configure Windows Hello for Business policies to allow fingerprint authentication for your account, or the domain policy may require a supported TPM version that the hardware doesn’t have.
TPM requirement for Windows Hello
Windows Hello requires a TPM (Trusted Platform Module) to securely store biometric templates and PINs. Windows 11 requires TPM 2.0, and Windows Hello uses it for key storage. If the TPM is missing or has issues: Windows Hello fingerprint may not function or may fail enrollment.
Check TPM status: Win+R → tpm.msc. If it shows “TPM is ready for use” with version 2.0: TPM is not the issue. If it shows “Compatible TPM cannot be found” or an error: the TPM needs to be enabled in BIOS or the driver is missing. Security → TPM in BIOS settings — the TPM is sometimes disabled and needs to be enabled for Windows Hello to function.
Fingerprint reader accuracy over time
Fingerprint reader recognition can degrade in quality over time due to sensor surface wear (scratches reduce sensor accuracy), accumulated skin oil on the sensor (clean regularly with a microfibre cloth), and changes in skin texture (seasonal dryness, cuts, or calluses from physical work). If recognition accuracy has gradually worsened: delete the existing fingerprints and re-enroll multiple orientations fresh. The new templates captured in current conditions provide better match rates than old templates created when the skin was in a different state.
False rejections — when to accept vs troubleshoot
Windows Hello fingerprint recognition isn’t perfect — false rejections (the reader not recognizing a valid finger) happen occasionally. What’s normal: one rejection in 10-20 attempts. What indicates a problem: rejection more than 50% of the time, or complete failure to recognize the enrolled finger at all.
For high false rejection rates: re-enroll with more orientations (5-6 orientations of the same finger) → test accuracy. The enrollment process allows more orientations than most users use. For complete failure: proceed through the driver and database fixes above.
Fingerprint not working in specific apps
Windows Hello fingerprint authentication works at the system login level and in applications that specifically integrate Windows Hello for authentication (some password managers, banking apps, enterprise software). It doesn’t work as a general “authenticate for any app” input — applications need to specifically support the Windows Hello APIs to use fingerprint authentication.
If fingerprint works for Windows login but not for a specific app: the app may not support Windows Hello fingerprint, or it may require a specific configuration. Check the app’s security settings for any Windows Hello or biometric authentication option that needs to be enabled separately from the system-level setup.
Enterprise: Hello for Business vs consumer Hello
Windows Hello (consumer, on personal machines and non-domain workstations) and Windows Hello for Business (enterprise, requires Azure AD or Active Directory) are different implementations with different setup requirements and failure modes. On domain-joined machines: Hello for Business policies apply, and fingerprint setup follows a different configuration path than personal Hello. If fingerprint authentication worked before domain join: the Hello for Business configuration may need IT attention to re-enable it in the enterprise context.
Quick diagnostic flow
| Symptom | Cause | Fix |
| No fingerprint option in Settings | Hardware not detected or BIOS disabled | Check Device Manager; check BIOS settings |
| Option visible but enrollment fails | Driver issue or WinBioDatabase corrupt | Reinstall manufacturer driver; clear biometric database |
| Enrolled, now not accepting | Template corruption or skin change | Remove and re-enroll with multiple orientations |
| Intermittent failure | Dirty sensor or partial template | Clean sensor; re-enroll more orientations |
| Domain machine issues | Hello for Business policy | Contact IT; check TPM status |
Fingerprint authentication is reliable when the hardware is correctly detected, the driver is the manufacturer-specific version (not a generic one), and enrollment covers multiple orientations of the finger. Getting these three things right provides a consistently working experience without further troubleshooting. The fixes in this guide are ordered by frequency — re-enrollment and driver installation together cover the large majority of fingerprint reader problems in Windows 11.
One practical note on fingerprint security: Windows Hello fingerprint data never leaves the device. Biometric templates are stored in the TPM and local WinBioDatabase, encrypted and protected from access by other users or applications. Microsoft’s servers don’t receive fingerprint data. For users concerned about fingerprint data privacy: the on-device-only storage model provides strong privacy guarantees compared to cloud-based authentication systems. This is one reason Windows Hello is consistently recommended as a secure and private authentication method — the biometric data stays on the hardware that captured it.
SFC for biometric infrastructure
The biometric service and its associated files can become corrupted by failed updates or disk errors. If none of the above fixes resolve the issue:
sfc /scannowAdministrator Command Prompt. After repair and restart: test fingerprint authentication. Windows’ biometric service files are part of the system component store that SFC validates and repairs — corrupted service DLLs would explain persistent failures that survive driver reinstalls and database resets.
For new machines where fingerprint authentication has never been set up: the setup process in Settings → Accounts → Sign-in options → Windows Hello Fingerprint → Set up walks through enrollment. The reader’s quality (and the enrollment process thoroughness) largely determines the long-term authentication experience. Budget fingerprint readers on entry-level laptops have smaller sensor areas and lower-quality optical arrays — these are more prone to false rejections than premium readers regardless of software configuration. If authentication is unreliable despite correct setup: the hardware itself may be a limiting factor, and PIN + password fallback remains the reliable alternative.
Goodix and Synaptics reader specifics
Goodix and Synaptics supply the majority of built-in laptop fingerprint readers. Both require manufacturer-specific drivers for optimal performance. Windows Update often installs a “Microsoft fingerprint compatible device” driver that provides basic functionality but doesn’t include the tuning for specific sensor hardware. For Goodix: the driver comes from the laptop manufacturer (Lenovo, Dell, HP, ASUS all have Goodix driver packages specific to their models). For Synaptics: similarly from the laptop manufacturer, not from Synaptics’ own site (laptop-specific tuning isn’t available on the chip manufacturer’s generic driver page).
If you’re unsure whether the correct driver is installed: Device Manager → Biometric Devices → right-click the fingerprint reader → Properties → Driver tab → “Driver Provider” should show the laptop manufacturer (Lenovo, Dell, HP) or the reader manufacturer (Goodix, Synaptics, Elan) — not “Microsoft.” A “Microsoft” provider indicates the generic driver, which should be replaced with the manufacturer-specific one for the best authentication performance.
For users troubleshooting fingerprint authentication on a machine they’ve had for years: the combination of re-enrollment (clearing old templates), manufacturer driver update (replacing any generic driver that Windows updates may have installed), and WinBioDatabase reset provides the most thorough refresh of the entire fingerprint authentication stack. These three steps together create essentially a clean fingerprint authentication setup on existing hardware without reinstalling Windows — resolving accumulated issues from driver changes, template drift, and database state over months or years of use.
A brief note on using alternative fingers: most users enroll one or two fingers and rely on those exclusively. Enrolling a finger from each hand provides a useful backup — if the primary hand is occupied (carrying something, wet) the other is available. The Windows Hello setup allows enrolling multiple fingers simultaneously, each stored as a separate template. Up to 10 fingerprints can be enrolled across both hands, though 3-4 is practical for most users — providing redundancy without overcomplicating the setup. If this sounds familiar, Adobe Reader Not Opening is worth a look.
