Hp Validity Fingerprint Sensor Driver

[Kristin Dampeer]

reinstalledthese 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:

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).

The HP Client Security Mamager software on your notebook's support and driver page is a much more robust security suite than the security software I posted for HP consumer notebooks, which just works for getting the fingerprint sensor to work.

Hi, this did not work for me as expected. I use a HP ProBook 430 G2 with Windows 7 Pro 64 bit. I was able to install Dell's driver and see the "Biometric Devices" entry in the Control Panel, however when I went ahead and clicked "Use your Fingerprint with Windows" windows came back asking for the bundled software for the device. So I went to square one, uninstalled Dell's driver, installed HP's validity driver and on top of that HP Client Security software. This time it worked, after determining the security questions the software asks for three index and middle finger swipes for registration. I still cannot see the "Biometric Devices" in the Control Panel, but can logon using fingerprint recognition.

From this, I went to the HP site and found there was a driver for SUSE Linux Enterprise Desktop for the validity sensor. I downloaded and installed the rpm and everything went through successful, but I am still receiving the above error.

Sort of. I am unimpressed with the quality of the output. Fprint has a hard time correlating the output as there are usually too few features that are recognized. I think the windows drivers cheat by being a bit more tolerant.

Edit: I just looked over your previous posts and I see we talked about this before (I also never did manage to compile a CM 13 that would not hang at boot, but that is another issue)

Regardless, I see the link to an Ubuntu thread you provided in that older thread actually references this patch. Sadly, I had not known that the author passed away.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday

Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing

---

How to Ask Questions the Smart Way

Thanks bro for the help.

Yep, has been a long time since we talk about CM.. Actually, due to lack of time I'm quite absent from XDA and CM world I need to come back.

Please, add me to hangout so we can talk each other and I can assist you better on CM build matter.. eric...@gmail.com

There is a few tips that will make the trick to build successfully.

EDIT: I installed the packages libfprint-git (which is patched for VFS495 and other Validity sensors using a proprietary daemon) & vfs495-daemon from the AUR. But I'm getting the following errors from 'fprintd-enroll'

At this point it let me enroll my fingerprints, so go ahead and enable fingerprints as a login method and then I had the fingerprint sensor working and could use them for login to both Gnome and for sudo at the terminal

$ sudo authselect enable-feature with-fingerprint

Here is the Flake I build to get this working (before using this, you have to follow the first setup based on open-fprintd and python-validity up to step 3 and register a fingerprint to check if it worked. If successful):

The thing is that it has a fingerprint reader that worked fine under Windows 7. A couple of months ago I volunteered to upgrade it to Windows 10. That worked reasonably well but the fingerprint reader is missing in action.

Microsoft provides the basic OS infrastructure for Windows Hello. It is the hardware vendor responsibility to provide the drivers necessary to interface the hardware with Windows if the hardware will not work with whatever basic driver Windows provides. HP is notorious for not providing updated drivers when new versions of Windows are released.

1). Pursue the elderly HP software stack. Install the .NET 3.5 stuff and maybe the rest of the software components will agree to install and run. I could then manually uninstall all the .NET components less than .NET 3.5 and hope the fingerprint reader stack does not collapse;

Ah yes, I understand. Up until now I have been focusing on different issues and could not draw any direct connection between the mystery device not working and the known (other) issues on this laptop. And with that link posted previously, I have a means to identify this mystery device failure.

Um, seriously? I have been proceeding on the assumption that PIN was a separate but parallel authentication mechanism. Also because PINs have lower randomness than passwords, they have lower security than passwords.

I totally understand your reluctance about trying to talk someone who may not be particularly IT-savvy through carrying out often quite complex processes. (I have the same experience several times a month with some distant family members and friends so I know exactly how painful it can sometimes be. ? ) However, I have already suggested what I believe is a much, much easier alternative method of you getting this much-needed info yourself (post #27).

If we can determine that the Unknown Device is definitely not related to the issue with the fingerprint sensor then it will add credence to it being a driver issue with the fingerprint sensor.

Lesson learned. The generic Synaptics driver was the solution, it provided Windows Biometric Framework support, and we were able to tap into Windows Hello. Which is more modern and a preferred outcome for us anyway.

3a8082e126