The next decisive step is to determine whether Windows fails to enumerate the fingerprint sensor during startup, because restarting the biometric service can re-enumerate it without identifying the underlying driver, security-component, or startup-software failure.
1. Capture the failure before restarting the service
Immediately after a reboot when the reader and Sign-in options are unresponsive:
- Right-click Start → Event Viewer.
- Open Applications and Services Logs → Microsoft → Windows → Biometrics → Operational.
- Look for errors at boot and for event 1108, which indicates that Windows successfully loaded a biometric sensor.
- Note whether event 1108 identifies the fingerprint sensor as isolated in:
- Virtual Secure Mode when Enhanced Sign-in Security (ESS) is active, or
- System when ESS is not active.
- Restart Windows Biometric Service, then refresh the log and compare the new events.
Microsoft documents event 1108 as the sensor-enumeration event and provides the device-instance-path correlation under Device Manager → Biometric devices → fingerprint reader → Properties → Details. ^1^
Interpret the result:
- Event 1108 appears only after restarting the service: the sensor or its driver stack is failing to initialize during boot.
- Event 1108 exists before the restart, followed by errors: record the error codes and the sensor name; the device is enumerated, but a later Windows Hello component is failing.
- No new biometric events until the service restart: investigate startup software or the device’s power/driver initialization.
2. Reinstall—not merely update—the biometric driver
Since updating and checking Device Manager did not help, remove the existing driver instance so Windows rebuilds the device stack:
- Download the fingerprint driver for the exact laptop model from its manufacturer, but do not install it yet.
- Open Device Manager → Biometric devices.
- Right-click the fingerprint reader → Uninstall device.
- If offered, select Attempt to remove the driver for this device only when the downloaded OEM package is ready.
- Restart the laptop.
- Install the OEM package, restart again, and check whether event 1108 now appears during startup.
Microsoft’s Windows Hello troubleshooting specifically directs users to uninstall the biometric device and restart so Windows attempts to reinstall its driver. ^1^
3. Check ESS only if the setting is enabled
Open Settings → Accounts → Sign-in options after temporarily restarting the service. If Enhanced sign-in security says On:
- Run
msinfo32.
- Under System Summary, verify Virtualization-based security is Running.
- Open Software Environment → Running Tasks.
- Check for
bioiso.exe and ngciso.exe.
Missing secure components indicate an ESS initialization problem rather than a fingerprint-enrollment problem. ESS requires compatible sensor hardware, firmware, and drivers; non-ESS-capable sensors are not enumerated while ESS is enabled. ^1^
Do not disable security features as a first repair. Supply the event details and ESS status to the laptop manufacturer so it can provide a compatible biometric driver or firmware package.
4. Test for a non-Microsoft startup conflict
If the clean driver installation does not fix it, perform one clean-boot test:
- Search for
msconfig and open System Configuration.
- On Services, select Hide all Microsoft services, then Disable all.
- On Startup, select Open Task Manager and disable enabled startup applications.
- Restart and test the fingerprint reader before manually restarting its service.
If the reader works, re-enable half the disabled items at a time and reboot until the conflicting service or application is isolated. Return to normal startup afterward. Microsoft documents this binary-isolation procedure for identifying background software conflicts. ^2^
Conditional checks
- USB-connected fingerprint reader: In Device Manager, select View → Devices by connection. If the reader is below a USB hub, open each parent hub’s Properties → Power Management and clear Allow the computer to turn off this device to save power. This workaround applies specifically when a USB reader or its upstream hub is being suspended. ^3^
- Affected ELAN driver: If Device Manager reports ELAN version
3.10.11001.10606, 3.10.11001.10502, or 3.10.11001.10801, run sfc /scannow; Microsoft identifies those versions and onnxruntime.dll as a specific affected configuration. ^4^
- Settings continues freezing: Repair Windows components from Terminal (Admin), then restart:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
DISM should run before SFC. ^5^
If the failure remains after driver reinstallation and also occurs in a clean boot, submit a Feedback Hub report containing the failed-boot biometric events, event 1108 status, device instance path, driver version, and ESS/VBS status. Microsoft’s Windows Hello guidance directs unresolved biometric failures to Feedback Hub. ^1^
References
- Windows Hello Enhanced Sign-in Security
- [Windows 11](https://support.microsoft.com/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows)
- The Dissapearance of Fingerprint (sign-in option) from My Windows 11 Laptop - Microsoft Q&A
- About the ELAN fingerprint driver troubleshooter for devices upgrading from Windows 10 to Windows 11 | Microsoft Support
- Use the System File Checker tool to repair missing or corrupted system files | Microsoft Support