Fingerprint Sensor Driver For Windows 7
Janet Denzel
I upgraded from a Windows 7 install (not factory image) to Windows 10 and decided to try out the new build-in OS sensor support. On Win7 I didn't use it because it needed the HP tools installed and that was more bloat then i am comfortable with.. of course the problem is getting the drivers.. Windows seems to have installed a driver which is over 2 years old and doesn't even seem compatible with the OS fingerprint API. I'm not entirely sure whether Win10 is using the same one as Win7, but in any case, driver update didn't find a newer one which was compatible with the OS fingerprint features.
I downloaded and installed the version Lucadebe posted ( Removed link for error in link ). (Note that the installer does seem to dissapear all of a sudden, this is normal i think, it just adds the driver to windows, it won't actually update the device.)
2. use an older (but still relatively recent; a few months old) driver (from lenovo) which does support my sensor, but isn't certified as Win10 compatible. There are several versions to chose from here, although NONE from HP..
The first driver does list the newer VFS495 sensor (mine is VFS491), so i figured i'd force it and see if it works, rather than use a slightly older driver (also from Lenovo) not listed as Win10 compatible.
I went into device manager and opened the properties for the biometric sensor. On the driver tab i selected 'Update driver' -> 'Browse local dirvers' -> 'Let me pick from a list of device drivers on my computer'.
If you are using the HP provided driver it will by default have a driver selected from manufacturere 'Validity Sensors, Inc.'. They were acquired by Synaptics, so the new driver will be available under 'Synaptics FP Sensors'. I actually installed a number of newer drivers, but the one posted above should be listed as 'Synaptics FP Sensors (WBF) (PID=003d)'. Select it and click next to install..
@PeerOne: I would get the driver from the HP site with the right driver match... IF HP actually bothered providing driver updates. As it is, the only recent drivers for the VFS491 are available through lenovo. I have the HP Softpaq manager installed.. while the application itself got an update for Win10, the only 'driver' still being updated through it is the BIOS. Everything else is ancient...
It saddens my that we have to rely on another manufacturer to provide us with drivers for HP products... Lenovo is still providing drivers for laptops that are older than mine, even drivers for newer operating systems..
Dude, there's NOT an "actual hardware site to ge the right driver match", did you ever tried to find it? That's why so much people is asking about that, because HP's site do not have the driver, neither the manufacturer.
Exactly, who hasn't this fingerprint reader can't even imagine how many driver issues we had after any windows major updates.
I just wanted to share a solution (after a single day since the release of W10).
For me, now it works even better than before (with W8.1).
reinstalled these drivers, tried to set up fingerprint in HP Protecttools, the programm crashes and can't find the sensor afterwards, even after restarting that programm, only a reboot fixes it but the programm keeps crashing after all, is there any way i can get the fingerprint to work with windows for logging in etc.
Kind regards,
Sebastiaan
HP Client Security Manager provides enhanced Windows login and website single-sign-on capabilities. Security Manager is also the host for HP Client Security plugins, and therefore should be installed before other Client Security modules. This package is provided for supported models running a supported operating system.
I am running Windows 10 64-bit on the HP ProBook 6460b. I followed instructions to install a different driver for the VFS471 fingerprint scanner. As soon as I did, windows hello immediately started working. Note, I did not have to uninstall the old driver or remove the device from Device Manager. Simply performed "update new driver" and directed Windows to the "wbf_vfs_003c.inf" file. Worked like a charm.
See the last post on the link below:
Same issue here with the fingerprint sensor on my HP dv6-6b51ea. Tried installing the Windows 8 x64 driver found on the laptop's support page, however it doesn't work. The installation gets so far and then cuts out. How hard is it for HP to have working models of all their laptops, testing and developing new drivers in anticipation of new Windows OS updates?
It's worth mentioning that if anybody else here has got a similar HP model with 'switchable graphics', Windows 8.1 completely messed it up (like I haven't had enough problems trying to troubleshoot Switchable Graphics in the past), so I had to uninstall all AMD products, restart a few times and install the AMD stuff from the laptop's support page again.
Managed to get it to work! I had everything uninstalled to start with. I forgot to mention previously that in Device Manager, there were no Biometric Devices, however there was one extra USB port with a yellow icon (which I assumed to be the sensor). I disabled and enabled it a few times, but nothing. Then decided to try installing HP Simplepass 2011 which goes by SP61399.exe. That installed fine. I next tried the driver installation which is SP58834.exe. That, as before, cut out half way through. I tried running it under different compatibility settings, namely Windows 7 and 8. Each time it cut out. I decided to restart anyway and alas, it was working! Sorry about waffling on but I'm not entirely sure which of the above worked - all I know is that one of them did!
After upgrading to Windows 8.1 I had to reinstall the Validity Sensor software which was working under Windows 8.1 Preview. Now I am unable to get it working. Here are the details with respect to the Validity Sensor Hardware installed on my HP HDX 16:
There is no software for your particular computer for Windows 8. For the Fingerprint sensor to work it needs the Validity Sensor software and the HP SimplePass. I have included a link to a download for the SimplePass software for Windows 8.
Last week, I updated my PC to windows 8.1 and the fingerprint reader stopped working. The reader does not flash anymore. When I checked the device manager, there is no error displayed. And yet, I did try the steps showed herewithin this solution. But my fingerprint reader is not working.
Microsoft has introduced new requirements on biometric sensors to comply with Windows Hello quality guidelines. A new manual review process will be necessary to gain approval to interoperate with Windows Hello. The process will be enforced with an OS check for a specific signature obtained through the Windows DevCenter (here: ) that can only be obtained by undergoing the process in this document. Drivers that have been created and signed by WHQL before 6/1/17 are grandfathered. New and updated drivers that do not obtain this signature after this date will not work with Windows Hello in Window 10, version 1703 or later after the enforcement date.
A driver will always undergo manual approval to obtain the Windows Hello signature. Updates to approved drivers can refer to previous submissions for faster approval. Drivers must undergo a new review if it applies to a new sensor, or if changes to the matching engine have occurred that impact FAR, FRR, or presentation attack detection.
bugId: ID number for the previous HLK submission that contains the previously approved security review information or 0 if the submission is undergoing an entirely new security review.
Biometric driver packages will need to be submitted to the new DevCenter portal to obtain the required Windows Hello signature and be uploaded to WU. Packages will need to include specific properties in the driver INF file to properly specify the adaptor dll's obtaining the digital signature. The following example demonstrates the formatting to obtain the bio signature on adaptor binaries and their related libraries.
For example, if the driver package contained a sensor, engine, and storage adaptor named sensor.dll, engine.dll, and storage.dll respectively, and one loaded stringparser.dll, then to obtain the bio signature on each one, the INF file would have to include the following components:
This step is the most important to making sure your driver receives the proper certification. All third party biometric adaptor files and any third party dlls loaded by these adaptors will need to be labeled and included in this manner if they are to obtain the biometric signature when submitted to DevCenter.
The HLK tests will make sure the above modifications have been made in steps 3 and 4 and will fail if the configurations information is not there.When packaging the final HLK in HLK studio include the security review template submitted in the bug as a supplemental file.
Microsoft will approve the submission provided it meets all Biometric requirementsObtaining the biometric signature is not certification that the driver will work with Windows Hello. For example, a file could be excluded in the inf configuration file that is checked for the signature. If this file is loaded at the time the OS enforces the signature, the load will fail and the driver will not operate with Windows Hello. The signed driver should be tested by the IHV and OEM to ensure it works in the collective system.
If an update to a previously signed driver needs to be made, follow the instructions under step 3 for filling in the bugId and updateExistingSubmission fields in the driver configuration xml for the updated driver.If an update is being made to a grandfathered driver, the same steps should be used. The bugId field should be set to the submission ID of the grandfathered driver and the updateExistingSubmission field should be set to true.The driver configuration xml should be included in the driver package that is submitted.
If you install legacy drivers on Windows 7 or later with Windows Biometric Framework, there is a chance that a future Windows Update could automatically replace the legacy driver with the WBF driver, which could cause your application to not work well. To avoid this possible problem, please be sure to update the SecuGen SDK dll, for example, sgfplib.dll (from FDx SDK Pro).
9d9a05e021