How do I enable the fingerprint reader?

Topic

New Reply

I have an HP laptop, an HP Pavilion dv7. Not really mine, it belongs to a family member. It’s a very nice laptop that’s about 4 years old.

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.

We performed a bare-metal upgrade. It turns out that HP only supports laptops 2 years old or less so I prepared our upgrade with the idea we won’t get support. In fact we prepared rather carefully.

As part of that I researched Windows Hello. It turns out that Windows Hello isn’t limited to facial recognition, which has gotten most of the press. It covers fingerprint readers too! So we are covered, right?

Not right. The Windows Hello screen that is supposed to support fingerprint readers, lacks the fingerprint reader option on this system. I’ve even seen screen shots of what this fingerprint reader option is supposed to look like, exactly where it is, everything. It’s not there. And yes, the relevant Biometric option in the system settings is present, it shows the reader hardware and driver, everything is A-OK. No warnings or errors.

I’m not done at this point you understand. “Not supported” does not mean “our systems no longer work”. I went to the HP web site and got all the software for this system. It turns out that you need to install 3 pieces of HP software to support the fingerprint reader. There’s a driver, a platform component (they might have called it foundation), and the fingerprint application. It’s all Windows 7 era stuff you understand.

The driver installed just fine. The platform component install failed with a “you cannot install this with .NET less than 3.5”. Naturally I check and no, there’s no .NET less than version 3.5. As a bare metal install we have .NET v4.6 and only that version. We didn’t have all the .NET v4.6 components though, so I tried adding all those and re-running the platform install. Nope, that didn’t change the error message at all.

Of course we have no HP support. I know their platform component install logic is broken but I can’t get that fixed. And Windows Hello isn’t giving me the options I know it ought to.

Fingerprint readers are supposed to be first-class authentication options now. As in, fully supported by the operating system. I’d prefer a Windows Hello solution because that gets me support. So why isn’t Windows Hello giving me a fingerprint reader option?

For the record it’s an HP Pavilion dv7 model 4260-ca (entertainment).

Reply | Quote

Replies

:confused: Microsoft is not obligated to make their Windows software work with any and all hardware that has ever been, or will be created. It’s HP that would need to create the software that would enable their hardware to work correctly with Windows.

Reply | Quote

The platform component install failed with a “you cannot install this with .NET less than 3.5”.

It should probably say, “or more than” too. So it could be worth enabling 3.5.

Reply | Quote

It should probably say, “or more than” too. So it could be worth enabling 3.5.

You may be on to something. However I hate to install .NET 3.5, as it automatically installs all the .NET baggage all the way back to .NET 2.0! I might as well not have gone to the work of a bare-metal install at that rate, grumble, grumble…

Reply | Quote

Microsoft is not obligated to make their Windows software work with any and all hardware that has ever been, or will be created.

True, but this laptop isn’t exactly ancient either. And I’m not aware of any technology requirements that Windows has, that invalidates fingerprint readers of a certain class or age. Unlike the facial recognition which requires infrared cameras that almost no-one has right now.

In fact that’s the entire point of device drivers. They handle the hardware and then Windows can work with a device independent interface.

Reply | Quote

Go into device manager and check that fingerprint reader for red exes or yellow exclamation points.
delete the device and reboot.

However I hate to install .NET 3.5, as it automatically installs all the .NET baggage all the way back to .NET 2.0!

If that is what is required do it, or revert back to W7.

Reply | Quote

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.

I agree with Clint about .NET. If it says you need 3.5 then you better install it since the HP software does not appear to work with newer versions.

Joe

--Joe

Reply | Quote

Note that you can enable .NET 3.5 as a Windows feature by going to Control Panel | Programs | Programs and Features | Turn Windows features on or off.

Joe

--Joe

Reply | Quote

I’m wrestling with my next move. The way I see it I could do any (or all) of the following;

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;

2). Go to Microsoft. Theoretically I’m supported by them for Windows Hello… though I’m certain they will want a credit card number and will charge for support. And I suspect the end result will be “we don’t support systems that old” or “we have no idea what is wrong, why don’t you talk to HP?”

3). Try to get a newer driver. We have the last BIOS update for the laptop installed but maybe there’s a newer Windows driver available from Synaptics (formerly Validity).

HP Notebook PCs – Troubleshooting a Fingerprint Reader

Fingerprint reader support in Windows 10

Reply | Quote

In order for your HP hardware to work with Windows, you need Windows-compatible drivers that have been created by HP for their HP hardware to work with Windows.

Reply | Quote

Got a chance to work on the laptop this weekend.

I tried installing the .NET v3.5, which allowed the platform module to install (hey, that’s progress!). Then I installed SimplePass which is the HP fingerprint reader application, also without incident. After a reboot and manually starting SimplePass, we hit another problem. Although fingerprint readers are mentioned on the first screen, on the second we only got options to use a PIN or standard Windows account password. No fingerprint reader option.

I also went back and checked the Windows Hello setup screen. It too still refuses to offer a fingerprint option.

One more thing I did. I hunted down a generic but modern Synaptics driver, which they offer in 64-bit, Windows 10 rated and everything. That’s great but… Synaptics recommends running the HP OEM driver due to possible enhancement/modification by the OEM. Also, and this is a bit concerning, the Synaptics driver doesn’t specifically mention fingerprint readers (Synaptics makes touchpad hardware too. In fact they brand themselves as a biometrics company so for all I know they make iris readers and more). On the plus side the Synaptics driver has a much higher version number than the current driver we have, version 19.0.19.1 versus 2.0.1.2. At least I hope that’s a plus!

Finally, the Synaptics drivers come in flavors for SMBus and I2C hardware. I have no idea how to choose between these. Drat.

Reply | Quote

Also, and this is a bit concerning, the Synaptics driver doesn’t specifically mention fingerprint readers (Synaptics makes touchpad hardware too.

Instead of the generic Synaptics biometric driver, try the latest Synaptics Fingerprint Reader driver, available from here. Don’t download DriverMax, just the Windows 10 driver further down the page. From posts on other forums it’s likely the installer may suddenly quit the first time and you’ll need to run it again. You’ll need to re-boot after installing the driver.

PS – Again, from another forum, you shouldn’t need SimplePass. Windows 10 should handle that for you.

Hope this helps…

Reply | Quote

Instead of the generic Synaptics biometric driver, try the latest Synaptics Fingerprint Reader driver, ….

Wow cool! May I ask how were you able to determine it was the PID=0011 driver for the chip and not one of the others? I poured through what I could find on the DV7 and could not find the ID of the chip? Or do you figure–as I do–that all Synaptics driver packs will contain the correct driver and the installation app to detect the correct chip and install the correct driver from the pack?
http://www.drivermax.com/driver-download/0/Biometric/Synaptics+FP+Sensors

Reply | Quote

May I ask how were you able to determine it was the PID=0011 driver for the chip and not one of the others? I poured through what I could find on the DV7 and could not find the ID of the chip? Or do you figure–as I do–that all Synaptics driver packs will contain the correct driver and the installation app to detect the correct chip and install the correct driver from the pack?
http://www.drivermax.com/driver-download/0/Biometric/Synaptics+FP+Sensors

Sorry but it’s just a guess at the moment. I’ve just got the fingerprint reader working on my HP ProBook 6475b (PID=0003d) in Win 10 after having the same problems as the OP. I ended up reading through a lot of the posts on the HP Support forums. Several people had success with that PID=0011 driver on different models of HP laptops so I thought I would advise that one first before moving on to one of the other 6.

I didn’t need .NET 3.5 or any HP software either, just had to set a PIN first on my account (I use a local one) after the fingerprint reader driver was installed.

Reply | Quote

…. Synaptics recommends running the HP OEM driver due to possible enhancement/modification by the OEM. …

Finally, the Synaptics drivers come in flavors for SMBus and I2C hardware. I have no idea how to choose between these. Drat.

They all say that. I have never run across a driver yet that was improved by the OEM. That said you find latest drivers by searching PCI Database. I am a little wary of a 17 version jump in two years. Ideally, once found a Win10 driver can be located via Google on HP.com’s site with fingerprint reader app. Normally you wouldn’t care for most devices, but for this you likely will need HP’s if it exists for any newer model where that fingerprint reader chip was used. Whatever Win10 compatible software HP developed should then work. Alternatively someone else’s package but that can cause interesting messages if it works (“scan Lenovo FingerSafe”) .

I’d go with the SMBus.

http://forum.scottmueller.com/viewtopic.php?t=1308

http://www.pcworld.com/article/2089404/how-to-easily-find-drivers-for-unknown-devices-in-windows.html

https://msdn.microsoft.com/en-us/library/hh506443%28v=vs.110%29.aspx

http://support.hp.com/us-en/product/HP-Pavilion-dv7-Entertainment-Notebook-PC-series/4346314/model/5052139/

This looks like the last version of the software written by HP:
http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_126956_1

Reply | Quote

The Windows Hello screen that is supposed to support fingerprint readers, lacks the fingerprint reader option on this system. I’ve even seen screen shots of what this fingerprint reader option is supposed to look like, exactly where it is, everything. It’s not there. And yes, the relevant Biometric option in the system settings is present, it shows the reader hardware and driver, everything is A-OK. No warnings or errors.

I’m not done at this point you understand. “Not supported” does not mean “our systems no longer work”. I went to the HP web site and got all the software for this system. It turns out that you need to install 3 pieces of HP software to support the fingerprint reader. There’s a driver, a platform component (they might have called it foundation), and the fingerprint application. It’s all Windows 7 era stuff you understand.

I’ve just got the fingerprint reader working in my own HP laptop. My Device Manager now shows the fingerprint reader and a TPM chip.

43811-fingerprint
Click to enlarge

In your first post you wrote “the relevant Biometric option in the system settings is present, it shows the reader hardware and driver, everything is A-OK. No warnings or errors.”

By “system settings”, do you mean Device Manager, i.e. does it look similar? Could you post a screenshot?

(As yours is a consumer laptop – as opposed to a business model – it’s more than possible that yours won’t have a TPM chip. I was unable to find any info about whether the HP Pavilion dv7-4260ca has one.)

If your Device Manager does show the fingerprint reader under Biometric devices (with no warning) then – going by my own experience earlier today – I’m a bit confused why you should need any further software. Does it unlock OK using your PIN?

Reply | Quote

My Device Manager now shows the fingerprint reader and a TPM chip.

(etc.)

Yes, I meant Device Manager, and the Biometric devices node shows much the same as yours.

As for the TPM I must confess I never thought to check for that. The TPM would increase the overall security of the system but I don’t think it’s required for the fingerprint reader. In fact I answered my own question as I was writing that–the fingerprint reader worked before. Whether this system has a TPM or not the fingerprint reader is functional in both principle and in fact.

Unfortunately I cannot post a screen shot easily, as I’m currently located in a different city. The system owner has basic skills and could be talked through the process of getting a snap. I’ll do it if you think it worthwhile.

I also recall one “unknown device” in Device Manager but I doubt that is relevant. It was in it’s own device group (not Biometrics).

Reply | Quote

Yes, I meant Device Manager, and the Biometric devices node shows much the same as yours.

If the Fingerprint sensor is showing under the Biometric devices node then you don’t need any additional Synaptics driver for it (and no screenshot is needed).

I also recall one “unknown device” in Device Manager but I doubt that is relevant. It was in it’s own device group (not Biometrics).

Personally I would still find out what the unknown device was, just for peace of mind. It could be a base device like an accelerometer, which IMO is important to protect a ‘spinning platter’ hard disk in case of a fall. Windows 10 didn’t pick up the accelerometer in my HP laptop so I had to manually install the latest HP 3D DriveGuard (v5.2.2.1).

43821-HP-3D
Click to enlarge

Alternatively, it could be something like the HP Hotkeys device (which supports the special Function keys for media, volume, etc.) which, again, Windows 10 didn’t pick up so I had to install the ‘HP Hotkey Support’ software to get the Function key actions displaying on-screen.

Reply | Quote

Personally I would still find out what the unknown device was, just for peace of mind.

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.

Still, this is going to take some time. I may not have access for a couple of months.

Reply | Quote

Windows 10 didn’t pick up the accelerometer in my HP laptop so I had to manually install the latest HP 3D DriveGuard (v5.2.2.1).

43821-HP-3D
Click to enlarge

Alternatively, it could be something like the HP Hotkeys device (which supports the special Function keys for media, volume, etc.) which, again, Windows 10 didn’t pick up so I had to install the ‘HP Hotkey Support’ software to get the Function key actions displaying on-screen.

On researching for whether to install Driveguard, I found the latest version to be 6.0.28.1.

Reply | Quote

OK, we have successfully set up a PIN. Now the Account Sign-in Settings screen looks like this:

43855-Sign-In-Options-After-PIN-Set

As you can see there is still no Windows Hello option, no message prompting us to set a PIN under Windows Hello (of course that wouldn’t make sense from a sequencing perspective now), and no option to set up a fingerprint reader.

The mystery remains!

Reply | Quote

…just had to set a PIN first on my account…

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.

Thus I’ve been avoiding them like the plague.

Reply | Quote

Um, seriously? I have been proceeding on the assumption that PIN was a separate but parallel authentication mechanism.

I had to set a PIN first in order that Windows Hello enabled the ‘Finger’ Setup button.

Didn’t you get this?

43820-set-PIN
Click to enlarge

Once I set the PIN up, the ‘Finger’ Setup button became enabled. I clicked on the ‘Finger’ Setup button and it asked me to enter my PIN before allowing me to enrol using a fingertip.

Reply | Quote

Didn’t you get this?

Nope. I mean that message is clear and unambiguous, connecting the PIN requirement to the fingerprint reader. Even if I was tired I wouldn’t have missed the connection; particularly since getting the fingerprint reader running has become a bit of a mission of mine. It’s the principle of the thing now, you know? It ought to work and I don’t understand why it’s not working.

Reply | Quote

I would fix the ‘unknown device’ first, just in case it has a bearing, then return to the Fingerprint issue. Post back if you need any help identifyng it.

I freaked out yesterday when I updated the BIOS on my HP laptop to the latest version and the flaming fingerprint sensor immediately stopped working (so I used the PIN to log in). I ended up having to load the BIOS defaults, re-configure them all then disable/re-enable the ‘Fingerprint Device’ in the BIOS before it began working again. Phew!

Reply | Quote

Well that was unbelievably painful, but I got the screen shots requested!

43826-Device-Manager-Screen-Shot

43827-Account-Screen-Shot

As you can see there appears to be no TPM hardware at all and the prompt message for the PIN in Windows Hello, in fact the entire Windows Hello group is missing.

Reply | Quote

Good screenshots… it looks like you’re almost there.

I think the reason that Windows Hello and Fingerprint options aren’t yet visible is because a PIN doesn’t appear to have been set. What happens when you click on the Add button under PIN? Does it let you set a PIN? If so then do it… and Windows Helllo should appear, together with the Fingerprint option.

As for the ‘unknown device’, try this:

1. Double-click on the ‘unknown device’ to bring up its Properties.
2. Select the Details tab.
3. Change the Property dropdown from the default Device description to Hardware IDs instead.
4. Post a new screenshot or list the VEN and DEV info… or use the PCI Vendor and Device Lists database to identify it.

Hope this helps…

Reply | Quote

I’ve asked the family member to perform the PIN steps. We’ll see how far they get.

IMO asking this person to troubleshoot an Unknown Device exceeds their skill level.

Reply | Quote

Just a thought but you could probably supervise both yourself using something like TeamViewer.

(I put TeamViewer Quick Support on all my family’s and friends’ Windows devices, with a shortcut to the app on their desktop, just in case.)

Reply | Quote

Another step forward, so let’s have a quick recap…

1. Is the Fingerprint device enabled in BIOS/UEFI? Yes, you had it working in Windows 7 (post #1).
2. Does Windows 10 recognise the Fingerprint device and install an appropriate driver? Yes, Windows 10’s Device Manager shows the device as a Validity sensor under Biometric devices (post #24).
3. Is a PIN enabled (a pre-requisite). Yes, a PIN has been enabled (post #29).
4. So what’s left to do? I can’t help but think that the last remaining ‘unknown device’ may be involved…

Short explanation? … in Windows 7 there was no built-in support for this particular fingerprint reader except for a hardware device driver. Instead, you had to install a .Net app – HP SimplePass – which was dependent on .Net 3.5.

Using Windows 10, my own experience and that of others shows that support for biometric devices like the fingerprint readers used in some HP laptops, is now built-in… so neither HP SimplePass nor .Net 3.5 is required.

The possible fly in the ointment? It wasn’t possible to determine whether your HP Pavilion dv7-4260ca laptop has a TPM chip (which is a base device) or not.

As for the TPM I must confess I never thought to check for that. The TPM would increase the overall security of the system but I don’t think it’s required for the fingerprint reader. In fact I answered my own question as I was writing that–the fingerprint reader worked before. Whether this system has a TPM or not the fingerprint reader is functional in both principle and in fact.

Sorry but… I personally wouldn’t make the same assumption. Ignoring that your W10 Device Manager screenshot in post #24 shows 2 entirely different graphics adapters, you don’t know for sure whether your working W7 configuration included a TPM driver nor whether, in W10, the last remaining ‘unknown device’ is related in any way to the problem enabling the fingerprint reader in Windows Hello.

As per post #22, I suggest this is the next thing to sort out.

Hope this helps…

Reply | Quote

Careful now. The graphics adapter is a known issue and has nothing to do with the fingerprint reader. That’s another matter for another time.

Reply | Quote

I was reading an article about Windows 10 Phone and suddenly a phrase jumped out like a bolt of lightning.

“Windows Hello requires a specialized infrared camera or fingerprint reader that supports the Window Biometric framework.”

This is the first time I’ve heard of a specific fingerprint reader requirement, beyond basic hardware and drivers. And it makes sense that there would be a standard interface need, like an API. It could explain the lack of Windows Hello functionality I’m experiencing. This would also likely hold true for both Windows 10 for PC’s and phone devices. Although there are some differences they are far more alike than in the Windows CE days.

Windows 10 Mobile Upgrades Arrive For Older Smartphones

Reply | Quote

The installation of the hardware driver for the Validity sensor should have triggered the automatic installation of the Windows Biometric Framework (WBF).

In Device Manager, expand Biometric devices, double-click on the Validity sensor, open the Details tab and check the list of associated events.

Is there an event that shows the Windows Biometric Framework was installed?

Is the Windows Biometric Service installed (probably with a Startup Type of Automatic (Trigger Start)?

PS – As per posts #20, #23, #25 and #30, I still suggest you identify the ‘unknown device’, if only to discount it as being part of the problem.

Hope this helps…

Reply | Quote

Wouldn’t the Windows Biometric Framework show up in Add/Remove Programs?

I really don’t want to send this client through Event Manager. Even the Services Manager might be too much, though I suppose we could give it a go.

Reply | Quote

Wouldn’t the Windows Biometric Framework show up in Add/Remove Programs?

No. It’s a built-in background support service that is installed/enabled automatically by the OS (if a WBF-compatible biometric hardware device driver is installed) rather than manually added by a user (e.g. HP’s SimplePass, which itself needs .NET 3.5 in earlier versions of Windows).

I really don’t want to send this client through Event Manager. Even the Services Manager might be too much, though I suppose we could give it a go.

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

TeamViewer, amongst other functionality, has built-in tools for screen capture (both stills and video).

43953-teamviewer_screen_recording
Click to enlarge

NOTE: TeamViewer is only free to use for personal use. In your original post and post #26 you described the laptop’s owner as a family member. However, your latest post (#34) describes the person as a client so that would be a major issue. (TeamViewer is very expensive for business use.)

Reply | Quote

OK, we managed to get all the information requested. First up is the detailed laptop config, both before and after the upgrade.

Next we got the services screen shot. Rather confusingly, this shows the Biometric service with an Automatic trigger and it’s running! I was sorta hoping it showed Biometrics absent or off. That would have made the absence of Windows Hello easier to explain. And the presence of Biometrics, running, what’s that about? With no camera or fingerprint reader support why is Biometrics running at all?

The reference to a “client” is habitual, they are in fact a family member.

Reply | Quote

OK, we managed to get all the information requested. First up is the detailed laptop config, both before and after the upgrade.

Next we got the services screen shot. Rather confusingly, this shows the Biometric service with an Automatic trigger and it’s running! I was sorta hoping it showed Biometrics absent or off. That would have made the absence of Windows Hello easier to explain. And the presence of Biometrics, running, what’s that about? With no camera or fingerprint reader support why is Biometrics running at all?

In Windows 7 the fingerprint sensor needed HP SimplePass as the conduit to pass information to the OS. (HP SimplePass itself needed .NET 3.5 in order to function.)

In Windows 10, neither HP SimplePass nor .NET 3.5 is needed because Windows 10 has its own built-in conduit – the Windows Biometric Framework (WBF) which runs as a service.

One of your previous screenshots (post #24) shows the fingerprint sensor is recognised and functioning OK in Device Manager.

Your latest screenshot confirms that the WBF service itself is up and running.

Your HP_Pavilion_dv7_Dec_31_2015, After Windows 10 Upgrade.txt attachment shows, at the very end in the Diagnostics section, that there have been a number of issues flagged up by Windows Error Reporting (WER). However, I’ve checked all the Vendor/Device identifiers shown (as item P2 in WER reports #3-9) and all relate to known hardware that is not related to the fingerprint sensor.

As a result, I think the problem may be that the fingerprint sensor driver that is currently in use is not a WBF-certified driver, i.e. whilst it obviously recognises the hardware correctly (‘cos it shows in Device Manager with no errors), it doesn’t appear to pass the info on to the WBF service and hence to the OS.

There’s still the issue of the Unknown Device but I’m beginning to think that this may be because there’s no driver installed for the laptop’s accelerometer (see post #20). Unfortunately this is impossible to rule out because your screenshot only shows a truncated view of the icons in the Notification Area.

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.

Can you please do the following:

1. In the Cortana search box to the right of the Start button, type msinfo.
2. When System Information appears as a search result, right-click on it and choose Run as administrator.

43998-msinfo

3. When System Information appears, expand Components in the left-hand pane then select Problem Devices.

43999-problem-devices

4. In the File menu, select Export… and save as problem.txt. (I’m hoping that this will show the Vendor/Device info of the Unknown Device. If it shows as ACPIVEN_HPQ&DEV_0004 then we’ll know that it’s the accelerometer, which needs HP DriveGuard installed to resolve.)

5. Expand Software Environment in the left-hand pane then select Services.

44000-services

4. In the File menu, select Export… and save as services.txt. (I’m hoping that this will identify whatever service the fingerprint sensor is using and its current status. The sensor not only needs a hardware device driver for the OS to recognise it in Device Manager but it also needs a running service in order that the hardware can pass information to the WBF service and hence the OS.)

5. Close MSINFO and attach problem.txt and services.txt to your next post.

Hope this helps…

Reply | Quote

I certainly appreciate your help on this Rick. It helps a lot to talk through the issues involved. And I like your explanation that while we have a running fingerprint driver, it lacks WBF support. The HP driver wouldn’t have needed that due to a custom software stack.

This implies that installing the generic manufacturer driver might be a good answer.

I’ll follow up with the Unknown Device information.

Reply | Quote

Right now. I’ve obtained those “Problem” files. The hardware file is short, just 2 entries while the software file has quite a few items.

Reply | Quote

Attached file: HP Pavilion dv7 Hardware Problems.txt

[indent]System Information report written at: 03/28/16 13:56:52
System Name: DESKTOP-TFGUEBQ
[Problem Devices]

Device PNP Device ID Error Code
Not Available ACPIHPQ00043&2411E6FE&0 The drivers for this device are not installed.
…[/indent][/quote]

Does this driver solve that problem?

Device ACPIHPQ00043&2411e6fe&0 requires further installation.

John_Hannigan
Student
Posts: 1
Member Since: 09-08-2015

09-08-2015 04:14 PM

Product Name: HP Envy M6 1350sf
Operating System: Microsoft Windows 10 (64-bit)

After upgrading to Windows 10, the only device that indicates a problem is an Unknown Device according to Device Manager (Device ACPIHPQ00043&2411e6fe&0).

I did a Google search but did not find anything for Windows 10. …

~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~-._.-~

Paul_Tikkanen
Provost
Posts: 72,158
Member Since: 07-13-2010

09-08-2015 05:23 PM

Hi:

Below is the link to the driver you need for the 0004…

ftp://ftp.hp.com/pub/softpaq/sp64001-64500/sp64144.exe

…

Reply | Quote

I’ve obtained those “Problem” files. The hardware file is short, just 2 entries while the software file has quite a few items.

As I suspected, the Unknown device (shown in the HP Pavilion dv7 Hardware Problems.txt file) is the accelerometer, which needs HP DriveGuard installed to resolve. At least that’s now been cleared up so you can concentrate on the fingerprint reader.

The HP Pavilion dv7 Software Problems.txt file shows a Validity VCS Fingerprint Service running. This doesn’t look like a WBF-supported service, i.e. not one that can pass info from the fingerprint sensor on to the built-in Windows Biometric Framework service. However, there IS a WBF-supported driver for the Validity fingerprint sensor. You can download it from Validity Fingerprint Common Driver for Windows 10 (32-bit, 64-bit) – Desktops, Laptops and Workstations.

Hope this helps…

Edit: I took another look at the list of services and spotted a Validity WBF Policy Service running. However, the fingerprint reader isn’t recognised by Windows Hello so I still think it’s worth downloading and installing the Validity Fingerprint Common Driver for Windows 10 (32-bit, 64-bit) from the URL above.

Reply | Quote

…I still think it’s worth downloading and installing the Validity Fingerprint Common Driver for Windows 10…

Agreed. It will take me 2-3 weeks to get access to this system to perform this work.

Reply | Quote

So we finally had a chance to work on this laptop and problem and there’s very good news. We finally got the fingerprint reader working!

We manually uninstalled the HP fingerprint stack. It was a bear to uninstall and took several tries. Mainly the problem was that the HP Software Framework refused to uninstall. It gave us some bizarre error messages saying that “The Administrator has locked you out”, yet we were running with Admin privileges! It took quite a bit of fooling around to figure out that we could elevate our authority by running the MSI installer and that installer would allow us to uninstall.

So then we installed the Synaptics SMBus driver and it didn’t work. There were no errors or warnings but it clearly didn’t work either. Uninstalled that.

Tried the I2C driver, and suddenly there was a Windows Hello option in Accounts under Settings! We ran that and suddenly there was an option to register the fingerprints and everything.

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.

Reply | Quote

HP machines
Rule 1: Remove all HP bloatware.
Rule 2: See rule 1.

cheers, Paul

Reply | Quote

Thanks to all who contributed.

Reply | Quote