HP SIMPLEPASS 2012

[BenMcDui]

Hello Dragon-Fur,

I repeated the steps for removing the driver over and over. The computer installs the driver again every time I boot after a hard shutdown. The driver installed is 4.3.118.0.

I found drivers in places like:

C:\SWSetup\Drivers\Fingerprint\Drivers\WBF_0011_DRV\

Would there be a way to remove all possible instances of the driver?

Thanks,

Ben

[Dragon-Fur]

Hi Ben,

Validity Driver v4.3.118.0 is compatible with HP SimplePass V5.0.1.455 -- the driver and that version of SimplePass are both quite old; none of the current versions of SimplePass can make use of this Driver.

The SWSETUP folder contains copies of your installed software.  It does not clean itself out as might be expected.  This means that there may be copies of old and new patches and software in the folder.

You can make a backup of the SWSetup folder contents.   The folder does not have any particular structure other than a standard folder; making a copy of the folder onto a USB stick or to another external location will suffice.  Having a copy of this folder is good practice.

After you have the backup done,

• Create a Restore Point  (although it is not directly related to removing a folder, this is good practice when you are making changes of any kind).

• I am curious about the folder contents, can you show a listing before you delete

                                        Drivers\Fingerprint\Drivers\WBF_0011_DRV

• After you get the listing, picture, infomation:  Delete C:\SWSetup\Drivers\Fingerprint\Drivers\WBF_0011_DRV
• Go in and dig out the Validity Driver V4.3.118.0 from your Device Manager > Biometrics ... that is, uninstall AND delete the 4.3.118.0 Driver
  
• Restart / Reboot the system OR if you are particularly freaked by this time, perform the Hard Reset.
• Log into the system and Check -- is the old driver finally gone?

• If you have managed to get rid of the old driver, install your newer "205" driver.
• Restart / Reboot the system
• Is the newer driver installed?

• If yes the driver is installed, then install the latest 6.x HP SimplePass software.

That may do it.

Click the Kudos Star!

It is a great “Thank You” for the HP Experts who are here to help!

[BenMcDui]

Dear Dragon-Fur,

The contents you rerquested:
C:\SWSetup\Drivers\Fingerprint\Drivers\WBF_0011_DRV\X64\wbf_vfs_0011.dll and
C:\SWSetup\Drivers\Fingerprint\Drivers\WBF_0011_DRV\X84\wbf_vfs_0011.dll
similar listings exist for
WBF_003c_DRV,
WBF_010_DRV,
WBF_018_DRV,
WBF_201_DRV,
WBF_300_DRV,
WBF_301_DRV,
WBF_451_DRV.

This is what I did

Backup and delete C:\SWSetup\Drivers\Fingerprint\Drivers\*
Remove the driver 4.3.118.0. The Biometrics Devices disappear from Device manager.
Reboot
Booting takes a long time; Precious is really upset now.
Machine automatically gets driver from Internet and installs 4.5.235.0. I know this version is higher than you recommend, but let's give it a try...
Fingerprint reader remains dead even after reboot.

Remove 4.5.235.0.
Reboot
Interrupt automatic download of driver.
But 4.5.235.0 is still active!

Found C:\SWSetup\Drivers\Fingerprint\WBFDDKSetup.exe and more; backup and remove.
Remove 4.5.235.0.
Reboot.
INTERRUPT the automatic download
Machine now says "driver not found"
Device Manager lists "unknown device" which after inspection turns out to be the reader (Harware-id)

Install sp56403.exe
"A newer version of Validity WBF DDK was already installed. OK?"
Search entire C: for WBF and DKK, delete everything ruthlessly.
Repeat the search, more found, delete.

Install sp56403.exe
"A newer version of Validity WBF DDK was already installed. OK?"
Automatic update of the "Unknown Device" in Device Manager -> 4.5.235.0
Reboot
Fingerprint sensor is dead.

Remove 4.5.235
Use CCleaner to remove any WBF DKK related (orphan) entries
Remove any WBF DKK related item on C:
Reboot

run sp56403.exe.
"A newer version of Validity WBF DDK was already installed. OK?"

Summarizing:

• Automatic install of version 4.5.235 does not revive the sensor
• Manual install of sp56403.exe bumps into the "A newer version... " message, although I removed all WBF and DKK related items, as well as registry entries. It seems as if sp56403.exe installs files that lead to the message "A newer version "
• The sensor remains dead, where previously it at least responde by rejecting my fingerprint.
• Login results in a black screen that lasts for 30 s.

Note: the sernsor does no longer work during boot, and DigitalPersona says the sensor is not connected. I have not even tried to go beyond this by installing Simplepass.

Beats me..

Thanks for your on-going support!

Ben

[Dragon-Fur]

Ben,

I cannot imagine the frustration you must be feeling!

I am distressed that things are worse for you.  Price of working blind.  My apologies. 

• Have you ever used the Digital Persona software on this system?    DP is old code written for older computers.  If you have never used it, and / or you don't have a good reason for having on the system, you might disable it or delete it.   If you have used DP, I suppose you can Export the DP database and then just leave it for now.  DP is not compatible with SimplePass.
  

----------------------------------------------------------------------------------------------------------------------------

• When you say you are removing the Validity driver, what precisely to you mean?

I am expecting you to say: "Uninstall AND Delete" and will assume same.

----------------------------------------------------------------------------------------------------------------------------

I am surprised by this forced driver update that is hammering at Precious.

See this guide to prevent Windows 7 from installing drivers out from under you:

How to stop Windows 7 automatically installing drivers

I do not suppose you want to leave the setting this way -- it may help with the forced update you are seeing on the BIOMETRIC device for time it takes to straighten out this mess.

----------------------------------------------------------------------------------------------------------------------------

• Do you know the name of the setup or sp* file that installed that 4.5.235 version?

There is something odd about this -- I found one reference to this version but I have yet to find matching installation file.  I do not have a complete list -- I might be missing something.

search in C:\SWSetup first -- install could be hiding anywhere, I suppose.  There is nothing "usual" about what is happening to Precious.

This is more of a curiosity than anything else.

If we can get any driver to install and to work, we can consider an update.

-----------------------------------------------------------------------------------------------------------------------------

Question:

• Do you have a Restore Point that you could use to backtrack to a time / date before all this fell apart?
• Or, at least do you have a Restore Point to put Precious back before the last couple of changes?

Reference:

Restoring Windows to a Previous Point (Windows 7)

System Restore can be tricky, too.  When you go to create a restore point -- just because Precious is so sensitive right now, be sure you first click on the C drive in the list and then create the restore point.  You might also unplug (temporarily) an USB drives you have connected to the computer.

This Experts Opinion:

I ask because as much as CCleaner is one of the more benign of the registry cleaners, things might only get worse if you keep hammering on the registry with any cleaner.  The tools can be dangerous to use.

-------------------------------------------------------------------------------------------------------------------------------

Next

• Try stopping the auto-update / auto-install of the devices.
• Create a Restore Point
• Delete and remove the BIOMETRIC driver
• No CCleaner this time
• Perform the Hard Reset .  Boot the computer and log in
• Assuming that Precious boots, check the device list
• Assuming evil version 4.5.235is finally gone, Install your Validity Driver
• Restart the computer (not shutdown and boot)

Out of other ideas for the moment... 

Click the Kudos Star!

It is a great “Thank You” to the HP Experts who are here to help!

[BenMcDui]

Dear Dragon-Fur,

Answering to your various remarks/questions:

Have you ever used the Digital Persona software on this system?
I have removed it, but assume I need it to use my fingerprint to log in to my computer?

I am expecting you to say: "Uninstall AND Delete" and will assume same.
Yes, this is what I do; uninstall and then tick the box for delete.

See this guide to prevent Windows 7 from installing drivers out from under you:
I already found this option and set it to manual update. Would indeed better be reverted after we're done.

Do you know the name of the setup or sp* file that installed that 4.5.235 version?
No, it installs fully autonumously and I have no idea where it may get stored temporarily if at all.
It is not in C:\ProgramData\Downloaded Installations, nor in C:\SWSetup\Drivers\Fingerprint.

So I followed you to do list:

    Try stopping the auto-update / auto-install of the devices. DONE

    Create a Restore Point. DONE
   

    Delete and remove the BIOMETRIC driver. There is no Biometric Device any more, just an Unknown Device with the hardware-id that refers to the fingerprint sensor

    No CCleaner this time. AYE

    Perform the Hard Reset . DONE: removed battery and power cord, pressed the I/O for 1 minute.

    Boot the computer and log in. DONE

    Assuming that Precious boots, check the device list. No biometric, only Unknown device.

    Assuming evil version 4.5.235is finally gone, Install your Validity Driver. Install sp56403.exe, the install information says VERSION:  4.3.301.0 REV:  A and then:  "A newer version of .... WBF .... etc."

Try to load a driver in Device Manager for Unknown Device (search the Internet as well)  "Your Unknown device can not be installed; no driver can be found".

Switched on "automatic update of drivers".

Reboot. (I notice that when I leave the login screen alone for a while, login is not followed by the blackout.)

Without any warning, "behind the screens", Validity Sensor version 4.5.235.0 has installed.

Restart.

The sensor is still dead. Normally, the white LED blinks when the login screen is up, inviting me to swipe my finger. Even when it had lost the fingerprint data, it would respond to a swipe with an orange LED. Now there is nothing. I had assumed that DigitalPersona was the application taking care of the fingerprint login, but now DigitalPersona says the sensor is not connected. In Device Manager, the sensor reports "Working correctly". The sensor also reports as details of the driver: C:\Program Files\Validity Sensors\FMA\nl-NL\FPManager.resources.dll (my system language is NL). There is also to befound C:\Program Files\Validity Sensors\FMA\ValidityFMA.exe and C:\Program Files\Validity Sensors\FMA\ValidityFMA.exe.config.

Well, where does dat lead us?

Thanks,

Ben

[Dragon-Fur]

OK,  Well you have a driver.

You do need the software to go with it.  I hold to the belief that you should be running HP SimplePass.

Your computer's webpage:

HP Pavilion dv7-6b70ed Entertainment Notebook PC Drivers

==========================================================================================

My apologies for being so stuck on this:

I have been going on the assumption, based on your computer's webpage and on your original comments, that you are running HP SimplePass.  I am confused by the references to Digital Persona.  One simply does not run these two programs on the same computer at the same time.  They do essentially the same job -- Digital Persona is older code, HP SimplePass is the successor to DP.

I am still trying to understand if you ever used Digital Persona on this computer.  I do not see it listed in your computer's website - your original question was regarding HP SimplePass.  I am frankly not seeing the connection between HP SimplePass and you running Digital Persona.  These two programs are not the same software.

• Is Digital Persona the original fingerprint program listed in your Recovery Manager?

If you have removed Digital Persona, how is it still reporting

Now there is nothing. I had assumed that DigitalPersona was the application taking care of the fingerprint login, but now DigitalPersona says the sensor is not connected.

???

===========================================================================================

Many things about this issue confuse me, frankly.  Smiling.

Like how you installed the later version of HP SimplePass and ended up with HP SimplePass 5.3 - that makes little sense to me since the later HP SimplePass version is 6.0.100.276 .

I still think that you should be able to install and run

sp63224 HP SimplePass V6.0.100.276 Win7-8

Unfortunately, I also believe that should you try to reinstall V6.0.100.276, that something else may get in the way.

For example:

• TrueAPI error(s) - the result of configuration confusion?  There is a possible fix for this (already posted) - would it work?  Wow, I do not know.  Frown.
• Odd version results - like installing sp63224 and ending up with HP SimplePass 5.3 .  Ugh.  That is just wrong.
• Digital Persona still reporting errors even after DP has been reportedly removed from the computer.  Also wrong - once removed / deleted / uninstalled, a program is not supposed to hang around and give you warning messages.

Frankly, I do not know how you can move forward without repairing your system configuration.  I fear that the registry is messed up -- the errors and the weird messages you are seeing could indicate that the registry is either missing something important, or that the registry is struggling with errant entries that it cannot clear.  This is admittedly a guess.  I might spend time tearing my own system's registry apart looking for a problem - it is not something I would do to anyone else.  The results can worse than that what the effort is worth.

I have dealt with Digital Persona and HP SimplePass on the computer at the same time; I never tried to run one along side the other.  It now sounds like it would have been a really bad idea.  As soon as I was ready to install HP SimplePass, I disabled DP.  Very soon thereafter, I uninstalled DP and never put it on the system again.

I do apologise to making this worse -- I cannot fathom how to dig out when neither program will let loose of your system's setup.

If I were you, I would back up my data -- all of it and to a couple of external locations.  I would make sure I had a current System Image in case things just get worse and you want to come back to where you are now.  I could make every effort to make sure I was ready, then I would Repair the system.

Starting with

Windows 7: SFC /SCANNOW Command - System File Checker

Remember:  You can run sfc more than one time - and in some cases, it is actually necessary to do so.

If you still cannot get rid of DP and install HP SimplePass,

then move on the the Startup Repair...

How to Run a Startup Repair in Windows 7

then, if all else, fails -- reinstall the Operating System.

For now, I would stay away from using the Registry Cleaner.  I do not think this is helping you.  Personal Opinion, that.

If I have any other flashes of insight, I will post back.

[BenMcDui]

Hello Dragon-Fur,

I checked the page you recommended:
HP Pavilion dv7-6b70ed Entertainment Notebook PC Drivers
The recommendation for the Validity Fingerprint Sensor Driver seems to be
2011-11-18 , Version 4.3.205.0
whereas the automatic install gives me 4.5.235.0, dated 2009-07-22.
How in the world can a higer version number have an earlier date? This is suspicious.

To be honest, I took DigitalPersona as needed for fingerprint windows login, but I have no proof it originally existed on my machine. So I Removed DigitalPersona and rebooted.

Recovery Manager tells me the following programs are likely to be restored:

• HP Simple Pass 2011 5.3.0.273
• Validity Sensors, Inc. (Biometrics) 02/01/2011 4.3.118.00.

There is no reference to anything like DigitalPersona or Verisoft. Does your computer provide Windows Login with a fingerprinter swipe?

So I tried installing Simplepass: sp63224.exe. TrueAPI(x64) is missing.

I made a fresh download from SkyDrive of ATTrueApiMin64_V6.0.100.276.msi and ran it first to remove the old install, second to do a fresh install.

Next I tried again installing sp63224.exe. TrueAPI(x64) is missing.
How difficult can it be?

Searching for solutions for TrueAPI I found http://h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/couldn-t-find-trueapi-x64/m-p/2175243/highl...
where Mirielle (Honor Student) recommends: "Fix your true API by downloading boost from this link http://www.boostbyreason.com/resource-file-10245-trueapi-dll.aspx and run a free scan. It would fix your true API." To nice to be true; Is this an attempt to lure us into a commercial product?

Apart from Mirielle's suspect solution, I have found nothing that helps me resolving the missing TruAPI. I tried removing/installing/repairing TruAPI but nothing helps me any further.

There are various TrueAPI entities in my system in various places, why can't the SimplePass installer find them?
Interesting: Authentec TrueAPI  64 bit appears in the list when I do Configuration Screen->Remove software.
The challenge here is, I suppose, to find out where the Simplepass Installer searches for TrueAPI, or why it sees the "wrong" version

I did sfc /scannow; no problems found.

This is as far as I got now, grateful for any further thoughts and suggestions. But we *are*  etting close to a Restore, aren't we?

Best regards,

Ben

[Dragon-Fur]

Ben,

I am at least beginning to understand why your configuration is so confused.

I might have discovered a couple of things that may help stave off the dreaded "recovery", that is, you having to reinstall your Operating System to straighten out the mess.

One of the items I discovered is the location and number of installer msi files depends on the number of versions installed on a system over a given time.  Depending on which version one is trying to repair, one or more of the installer files (filename.msi) are not useful for correct recovery.

I have updated the TrueAPI repair procedure. 

Find, open, and reference the procedure named:  HP SimplePass Installation – TrueAPI Missing

I cannot test this for you -- my configuration has never broken in the manner you are facing so I am still working blind.   The updated steps in my procedure have been extrapolated by what I can see and the results you have reported to me.

To be noted:  I have not solved the issue with your Validity Driver version -- I do think this is related to the interdependency I mentioned earlier.  I think you can leave the "205" driver in place -- it may work assuming the rest of the HP SimplePass repair / install is not skee-hawed (meaning messed up, forlorn tiny bits of broken code accumulating in the bit bucket).

OK... maybe closer?

Click the Kudos Star!

It is a great “Thank You” to the HP Experts who are here to help!

[BenMcDui]

Thanks Dragon-Fur,

I have some good news: after an automatic Windows update my fingerprint sensor started flashing and after I (re-)registered my fingerprints (Start - Configuration screen - User accounts/parental - User accounts - Manage fingerprints) Windows login works!

Now we only  have to get Simplepass installed 😉

I followed your link to the update procedure. I ran C:\ProgramData\Downloaded Installations\ATTrueApiMin64.msi and did repair. The files in C:\Program Files\Common Files\AuthenTec and C:\Program Files (x86)\Common Files\AuthenTec are all there, PLUS: TrueWinBioServer.exe.

Running sp63224.exe however still complains about the missing TrueAPI. What is going on here, why does the installer not see or accept the TrueAPI files that seem to be in the right place?

Best regards,

Ben

[Dragon-Fur]

Ben,

It does make sense that the Windows Updates fixed the Windows logon -- the mechanics for the native Windows 8.1 fingerprint logon are enabled with the addition of the Windows patches that provide the access to the hardware.  In other words, "Yes, the system has to have all the windows 8.1 updates to use the fingerprinter".

OK.  For the TrueAPI:  I do not know the answer.  I suspect the registry is hosed or that a library (.dll) link is missing somewhere.

There is so much going on "under the hood", that it could be several things.

I will think on it.

Now that the native logon is working, you might throw a Hard Reset at it and see if that clears the cobwebs.

I honestly do not know what to expect at this point.  Grim Smile here.

• Sidebar:  Is your Windows 8 Refresh still available?  If it is, don't do it yet, just asking for the moment.

Click the Kudos Star!

It is a great “Thank You” for the Experts who offer aid.