When running DCP controlvalut installation package, either from the security driver pack or standalone, it rolls back at the end of the installation. There is a installation log with 30000+ lines but I don't know how to read it.
We had a similar problem at one point; I cannot remeber which OS, but the issue was actually a bad version of the WDF Coinstaller. Somehow we got a pre-release version on the system that should NEVER have been deplyed; some application put it on the system -- we don't know where it came from.
You might try deleting/renaming WdfCoInstaller01005.dll and try re-running the install.
Renamed WDFCoinstaller01005.dll (however it is only in system32\drvstore\ so I am not sure if it really functions) and uninstall/reinstall DCP security driver pack and security manager. Still no success.
Same here. Windows7 64bit. I managed to see fingerprint reader at one point but when i start enrollment wizard it keeps telling me: An error occured during fingerprint enrollment. Please try to re-enroll this fingerprint.
Reader is freshly added , no previous enrollments (to be in conflict somewhere).
Tried the dll renaming, wave fingerprint folder deleting, disabled tpm before install, enabled it after install - still no luck to enroll.
I enabled bitlocker so when disabling tpm i have to type the recovery pwd.
I wonder if this bitlocker needs to be suspended before DCP SM and SD install? I'll try to suspend bitlocker, disable tpm and try all over again.
I'll let you know. Never had any issues with lenovo, strange that upek cannot be used with broadcom reader. Should be standard...
Renamed WDFCoinstaller01005.dll (however it is only in system32\drvstore\ so I am not sure if it really functions) and uninstall/reinstall DCP security driver pack and security manager. Still no success.
olivexer -
Are you sure you found all of the instances of WDFCoinstaller? Was there not one in c:\Windows\System32 ?
Is there anything interesting in %temp%\DSDPI.txt ? Are there any other installer log files in %temp% after the failed install?
Same here. Windows7 64bit. I managed to see fingerprint reader at one point but when i start enrollment wizard it keeps telling me: An error occured during fingerprint enrollment. Please try to re-enroll this fingerprint.
ahto - It sounds like you are having a different issue. olivexer's initial post indicates he is having an install-time issue; he likely does not even see the enroll fingerprint option in the Wave software as a result. He is also using XP-32.
...Tried the dll renaming, wave fingerprint folder deleting, disabled tpm before install, enabled it after install - still no luck to enroll.
The .dll I mentioned is specifically related to an installer issue caused by someone releasing software with a Beta of a Microsoft .dll that they should not have (they violated a MS licensing agreement when they did). I am not sure where that .dll came from. If your fingerprint sensor is showing up in device manager, it is not likely related to olivexer's issue.
I wonder if this bitlocker needs to be suspended before DCP SM and SD install? I'll try to suspend bitlocker, disable tpm and try all over again.
I'll let you know. Never had any issues with lenovo, strange that upek cannot be used with broadcom reader. Should be standard...
Bitlocker should not need to be disabled. The TPM should not have to be off or on; the fingerprint sensor should work either way. (If you have turned the TPM ON with credentials enrolled, then you will need to leave it on as the credentials are protected by the TPM -- turning it off will make them inaccessible.)
UPEK is a brand of sensor. Their implmentation is different than Broadcom's, or Authentec's ,or anyone elses. Unfortunately, there is no real "standard" for the fingerprint sensors.
Most of the sensor and solution manufacturers were using something similar, but not "standard." Microsoft came up with this "WBF" thing in Win 7, but they did not provide all of the components. WBF is also completely different than the pseudo-standard the manufacturers were already using in XP and Vista; so switching to WBF for Win 7 is not a simple task for the manufacturers.
I am using A11 of DCP security driver pack and A13 of DCP security manager application, under XP32 SP3. I have also updated BIOS and controlvault firmware to latest version. Until A11 of security driver my E6500 works find and recongnizes all devices and I can do fingerprint enrollment, preboot authentication etc. I only installed fingerprint secuirty and didn't install other security options like wallet, secured drive etc.
Now the issue is, when I want to install A12 or A13 of driver pack, I get problems. No matter I uninstall previous version or not, After installation of new driver pack and reboot, I cannot get the swipe sensor and another piece of hardware (I am not sure, maybe the smart card reader) recongnized and working. I've tried all above suggestions and none works for me. I have a drive backup image so each time I tried and it is unsuccessful, I restore the image to get back to normal, so I am still using A11 driver.
I only have it in C:\WINDOWS\system32\DRVSTORE\apfiltr_87CBD9E9705812FBC12CF164569112CB8994C422 so I guess it doesn't really function. The version is 1.5.6000.0 (vista_rtm.061101-2205) as I check in file property. But I am not running Vista.
[quote user="olivexer"]
Renamed WDFCoinstaller01005.dll (however it is only in system32\drvstore\ so I am not sure if it really functions) and uninstall/reinstall DCP security driver pack and security manager. Still no success.
olivexer -
Are you sure you found all of the instances of WDFCoinstaller? Was there not one in c:\Windows\System32 ?
Is there anything interesting in %temp%\DSDPI.txt ? Are there any other installer log files in %temp% after the failed install?
Sry if this is not the right thread, but in one point i was'nt able to see the reader too. I'll make a new thread if i have an answer from our local support team.
Same here. Windows7 64bit. I managed to see fingerprint reader at one point but when i start enrollment wizard it keeps telling me: An error occured during fingerprint enrollment. Please try to re-enroll this fingerprint.
Reader is freshly added , no previous enrollments (to be in conflict somewhere).
Tried the dll renaming, wave fingerprint folder deleting, disabled tpm before install, enabled it after install - still no luck to enroll.
I enabled bitlocker so when disabling tpm i have to type the recovery pwd.
I wonder if this bitlocker needs to be suspended before DCP SM and SD install? I'll try to suspend bitlocker, disable tpm and try all over again.
I'll let you know. Never had any issues with lenovo, strange that upek cannot be used with broadcom reader. Should be standard...
olivexer
1 Rookie
•
66 Posts
0
January 11th, 2010 23:00
I tried all that you suggested. Still no success.
When running DCP controlvalut installation package, either from the security driver pack or standalone, it rolls back at the end of the installation. There is a installation log with 30000+ lines but I don't know how to read it.
syragk
1 Rookie
•
23 Posts
0
January 15th, 2010 07:00
We had a similar problem at one point; I cannot remeber which OS, but the issue was actually a bad version of the WDF Coinstaller. Somehow we got a pre-release version on the system that should NEVER have been deplyed; some application put it on the system -- we don't know where it came from.
You might try deleting/renaming WdfCoInstaller01005.dll and try re-running the install.
Maybe that will help.
olivexer
1 Rookie
•
66 Posts
0
January 16th, 2010 02:00
Renamed WDFCoinstaller01005.dll (however it is only in system32\drvstore\ so I am not sure if it really functions) and uninstall/reinstall DCP security driver pack and security manager. Still no success.
ahto
3 Posts
0
January 18th, 2010 01:00
Hi
Same here. Windows7 64bit. I managed to see fingerprint reader at one point but when i start enrollment wizard it keeps telling me: An error occured during fingerprint enrollment. Please try to re-enroll this fingerprint.
Reader is freshly added , no previous enrollments (to be in conflict somewhere).
Tried the dll renaming, wave fingerprint folder deleting, disabled tpm before install, enabled it after install - still no luck to enroll.
I enabled bitlocker so when disabling tpm i have to type the recovery pwd.
I wonder if this bitlocker needs to be suspended before DCP SM and SD install? I'll try to suspend bitlocker, disable tpm and try all over again.
I'll let you know. Never had any issues with lenovo, strange that upek cannot be used with broadcom reader. Should be standard...
ahto
3 Posts
0
January 18th, 2010 06:00
ok, now i tried to disable tpm from bios. Before that i uninstalled security driver and manager. Rebooted, fw off, antivirus off.
installed driver reboot, installed manager reboot. endabled tpm. refreshed ownership. enabled, owned TPM ok.
everything ok exept i cant enroll my fingerprints. pc is in domain, i am a domain admin. Did everything as administrator just in case.
somebody has w7 64bit e6500 and broadcom fingerprint device working there?
olivexer
1 Rookie
•
66 Posts
0
January 18th, 2010 06:00
Mine is just XP SP3. How come Dell has no any response on this?
syragk
1 Rookie
•
23 Posts
0
January 20th, 2010 15:00
olivexer -
Are you sure you found all of the instances of WDFCoinstaller? Was there not one in c:\Windows\System32 ?
Is there anything interesting in %temp%\DSDPI.txt ? Are there any other installer log files in %temp% after the failed install?
syragk
1 Rookie
•
23 Posts
0
January 20th, 2010 16:00
ahto - It sounds like you are having a different issue. olivexer's initial post indicates he is having an install-time issue; he likely does not even see the enroll fingerprint option in the Wave software as a result. He is also using XP-32.
The .dll I mentioned is specifically related to an installer issue caused by someone releasing software with a Beta of a Microsoft .dll that they should not have (they violated a MS licensing agreement when they did). I am not sure where that .dll came from. If your fingerprint sensor is showing up in device manager, it is not likely related to olivexer's issue.
Bitlocker should not need to be disabled. The TPM should not have to be off or on; the fingerprint sensor should work either way. (If you have turned the TPM ON with credentials enrolled, then you will need to leave it on as the credentials are protected by the TPM -- turning it off will make them inaccessible.)
UPEK is a brand of sensor. Their implmentation is different than Broadcom's, or Authentec's ,or anyone elses. Unfortunately, there is no real "standard" for the fingerprint sensors.
Most of the sensor and solution manufacturers were using something similar, but not "standard." Microsoft came up with this "WBF" thing in Win 7, but they did not provide all of the components. WBF is also completely different than the pseudo-standard the manufacturers were already using in XP and Vista; so switching to WBF for Win 7 is not a simple task for the manufacturers.
olivexer
1 Rookie
•
66 Posts
0
January 20th, 2010 23:00
Let me clarify:
I am using A11 of DCP security driver pack and A13 of DCP security manager application, under XP32 SP3. I have also updated BIOS and controlvault firmware to latest version. Until A11 of security driver my E6500 works find and recongnizes all devices and I can do fingerprint enrollment, preboot authentication etc. I only installed fingerprint secuirty and didn't install other security options like wallet, secured drive etc.
Now the issue is, when I want to install A12 or A13 of driver pack, I get problems. No matter I uninstall previous version or not, After installation of new driver pack and reboot, I cannot get the swipe sensor and another piece of hardware (I am not sure, maybe the smart card reader) recongnized and working. I've tried all above suggestions and none works for me. I have a drive backup image so each time I tried and it is unsuccessful, I restore the image to get back to normal, so I am still using A11 driver.
olivexer
1 Rookie
•
66 Posts
0
January 20th, 2010 23:00
I only have it in C:\WINDOWS\system32\DRVSTORE\apfiltr_87CBD9E9705812FBC12CF164569112CB8994C422 so I guess it doesn't really function. The version is 1.5.6000.0 (vista_rtm.061101-2205) as I check in file property. But I am not running Vista.
olivexer -
Are you sure you found all of the instances of WDFCoinstaller? Was there not one in c:\Windows\System32 ?
Is there anything interesting in %temp%\DSDPI.txt ? Are there any other installer log files in %temp% after the failed install?
[/quote]ahto
3 Posts
0
January 20th, 2010 23:00
Hi
Sry if this is not the right thread, but in one point i was'nt able to see the reader too. I'll make a new thread if i have an answer from our local support team.
All the best,
Ahto
syragk
1 Rookie
•
23 Posts
0
January 21st, 2010 14:00
olivexer
If that is the only copy of the WDF Coinstaller dll; then that isn't likely the same issue.
Is there anything interesting in %temp%\DSDPI.txt ? Are there any other installer log files in %temp% after the failed install?
olivexer
1 Rookie
•
66 Posts
0
January 21st, 2010 14:00
I don't know if there is logs in temo dir. One last thing to try maybe reinstalling Windows, but I feel tired of repeating again and again...
aldergas
3 Posts
0
February 7th, 2010 21:00
Exact same problem here, Windows 7 64.
olivexer
1 Rookie
•
66 Posts
0
February 8th, 2010 00:00
I reinstalled XP from scratch, and the problems disappear. I don't know why.