Check whether Windows Biometric Framework enumerates the reader and whether Enhanced Sign-in Security (ESS) is excluding it before replacing the working Device Manager driver.
Device Manager’s “working properly” status confirms that the device driver loaded, but Windows Hello also requires the reader to be enumerated by the Windows Biometric Framework (WBF). ESS can prevent a non-ESS sensor from being enumerated even though Device Manager lists it normally.^1^
1. Check WBF enumeration
- Press Win+R, enter
eventvwr.msc, and press Enter.
- Open:
Applications and Services Logs → Microsoft → Windows → Biometrics → Operational.
- Restart the computer, reopen that log, and look for Event ID 1108 relating to:
USB\VID_3274&PID_8012
- Interpret the result:
- Event 1108 exists: WBF loaded the sensor. Check whether the event describes it as isolated in a System or Virtual Secure Mode process.
- No Event 1108: Windows Hello is not enumerating the sensor. Continue with the ESS test and then the Catalog driver.
Microsoft documents Event 1108 as confirmation that WBF loaded a biometric sensor.^1^
2. Test whether ESS is blocking the reader
First open Settings → Accounts → Sign-in options → Additional settings.
- Windows 11 24H2 or newer: If Enhanced sign-in security is present and On, temporarily turn it Off.
- Windows 11 23H2: If Sign in with an external camera or fingerprint reader is present, turn it On; this disables ESS for that test.
- Restart Windows and check Fingerprint recognition (Windows Hello) again.
Disabling ESS reduces biometric sign-in protections. Use this initially only as a diagnostic test; re-enable it afterward unless the reader works only without ESS and that security trade-off is acceptable. The fact that this internally installed reader uses a USB hardware ID does not by itself establish whether it is ESS-capable.
If no relevant toggle appears, do not modify the registry to force it. Instead, check:
- Run
msinfo32.
- Under System Summary, check whether Virtualization-based Security says Running.
- Under Software Environment → Running Tasks, check for
bioiso.exe and ngciso.exe.
ESS-capable fingerprint sensors require match-on-chip hardware, a manufacturing certificate, and compatible driver/firmware. When ESS is enabled, non-ESS sensors are not enumerated by WBF.^1^
3. Try the matching Microsoft Update Catalog package
Since the Acer driver has already been removed and reinstalled, repeating that package is unlikely to add information. The Microsoft Update Catalog lists MicroArray biometric packages matching USB\VID_3274&PID_8012, including version [IP Address] for Windows 11 24H2/25H2.^2^
This confirms that a Microsoft-distributed driver exists; it does not confirm validation for every SFN14-55 SKU. Prefer Acer’s package unless the following details match.
- Run
winver and confirm the installed Windows release.
- Create a restore point.
- In the Catalog result’s Update Details, confirm:
- The supported Windows release matches.
- The package includes the exact hardware ID.
- Download the applicable CAB and extract it from Command Prompt:
mkdir C:\MicroArrayDriver
expand -F:* "%USERPROFILE%\Downloads\downloaded-driver.cab" C:\MicroArrayDriver
- Open Device Manager → Biometric devices → Microarray Fingerprint Reader → Update driver.
- Select Browse my computer for drivers, choose
C:\MicroArrayDriver, enable Include subfolders, and install.
- Restart, then check for Event 1108 and return to Settings → Accounts → Sign-in options.
If it remains unavailable
Microsoft’s ESS troubleshooting sequence next calls for removing the Windows Hello PIN, restarting the biometric service, recreating the PIN, and retesting.^1^
Removing the PIN temporarily removes that sign-in method, so confirm that the account password works first.
- Settings → Accounts → Sign-in options → PIN (Windows Hello) → Remove.
- Open Command Prompt as administrator and run:
net stop wbiosrvc
net start wbiosrvc
- Recreate the PIN, restart, and test fingerprint setup.
If there is still no Event 1108, submit a Feedback Hub report and attach the Biometrics Operational log, current driver version, Windows build, and hardware ID. Also return the case to Acer because ESS compatibility depends on the combined sensor, firmware, driver, and OEM system configuration. There is no confirmed publicly documented known issue specific to the SFN14-55 with this hardware ID.
References
- Windows Hello Enhanced Sign-in Security
- Microsoft Update Catalog