I have not been able to get around it either. You may notice that if you scan your finger at Windows login it works just fine, of course it cannot log you in, but the FP scanner WORKS. Then, you go to the WAVE security applications and try to register the prints and it says nothing is connected. It all centers on the WAVE software Dell continues to use. I have 12 HP laptops and the security software on those is flawless and very nicely integrated. WAVE systems has never worked well. I had problems with it on my D820 and again on an XPS1530. Dell needs to stop using these poorly written, badly implemented, and pathetically tested products on their machines. They just never seem to get it which is why they continue to struggle.

OK, after speaking to someone good over at WAVE Systems it appears that the problem revolves around two .DLL files in the SYSTEM32 folder. (I am using XP in this example).

bioapi_mds300.dll
bioapi100.dll

If you look at the properties of these files and the modified date shows June 30, 2006 then the fingerprint scanner will NOT work. The driver update Dell has posted is supposed to replace these files with updated ones, but it does not do so and leaves the outdated files in place.

The new .DLL files should have a modified date of May 26, 2008.

I cannot post the new .DLL files as I was asked not to do so, but until Dell get a working update posted you could call or email WAVE systems directly for assistance. My fingerprint scanner now finally works. I do not use it for applications, websites, etc... only Windows authentication so in that regard, so far so good.

Hello RPomygal

thanks for your answer.

My DLL's are newer but it don't work. I think the firmware from Dell was not ok.

bye

freakezoid

Hello,

I got similar problems with the Fingerprint reader on my E6500 with Vista32. Installed the latest driver and ControlPoint Security software and the two DLL-files have the right date of May 2008.

Unfortunately I am not able to provide new fingerprints and somehow the TPM module seems to be inactive in the WAVE center, though it is enabled and activated in the BIOS.

Furthermore all security devices in Device Manager are enabled and operational, but somehow there must be something wrong with the Dell drivers/software. The Broadcom USH Driver.

I really hope this will be solved by Dell as soon as possible..... Using the fingerprint and TPM functionality was about the main criteria for me to choose this laptop.

Peter

Now a service *** was here and install a new Motherboard and fingerprint

and i have the same problem

I had to setup my Latitude E6500 today and ran into the same problem with the fingerprint reader under Windows XP. After it took me one hour of unsuccessful installations and reboots I discovered this thread. Here are my findings:

- Driver: you need to install the driver in file http://ftp.us.dell.com/app/DELL_CONTROLPOINT-SECURITY-M_A06_R204039.exe which is Dell ControlPoint Security Manager / Version:1.01.29 / 15.11.2008 and manually enable the option "AuthenTec Fingerprint Reader" in customized installation. After I've done this the fingerprint reader was found as a device and did not show the yellow (!) anymore in front of it in the device manager. It also was recognized by the Security Manager Software (Sicherheitsmanager).

- DLL-Files: the right bioapi100.dll and bioapi_mds300.dll have the timestamp 29.05.2008 - 17:16 and can be found in the program folder under \Security Device Driver Pack\BioAPI Framework\Patch

- Go to your Windows-Directory \SYSTEM32 (e.g. c:\windows\system32\ and rename the existing files bioapi100.dll and bioapi_mds300.dll (both with timestamp 30.06.2006 - 12:58 here) to something like bioapi100.dll_old and bioapi_mds300.dll_old

- Copy the two files from the directory mentioned above to SYSTEM32 and reboot

After this the fingerprint reader was working here as a device AND it was found when I tried to recognize my fingerprints in Windows. [Update 20.12.2008: I'm now still trying to figure out how I can remove the OLD fingerprints from the Preboot Manager as it shows registered preboot users (Registrierte Preboot-Benutzer): 2 in the Embassy Security Center. - after re-entering my finger prints the no. of registered users changed]

HTH

Greetings from Germany,

Maverick2k

I encountered a similar problem, after enrolling the first user OK in the initial security wizard run,
I got the "connect fingerprint sensor" when trying to enroll a second user's fingerprints.

With the help of Dell support, I downloaded and installed the
Dell_ControlPoint-Security-M_A07R206690 driver update.  I checked for the DLL files
as detailed by Maverick2k, but after the update, fingerprint did not work at all,
and TPM showed a ! in Device Manager.  I tried uninstalling and re-installing both with
and without the extra "AuthenTec Fingerprint Reader" checked.  No luck.
I tried installing all the other critical and recommended updates for the system as
well, again no luck.  I uninstalled and tried re-installing the drivers on the CD
that shipped with the system. 

I was able to get the TPM and fingerprint for one user only working by clearing the TPM
and restoring a backup system image I made before I set up any security.

I HIGHLY recommend taking a backup system image with Norton Ghost or equivalent
at the earliest possible time during the setup of the system, if you are planning
on using the fingerprint capability.  It may be necessary to recover from mishaps.

Also Beware:
After getting one user working with fingerprint (fortunately backed up again) I installed
the DELL_CONTROLLPOINT-CONNECTION_A10_R206351, which I expected to be safe and
unrelated, but it wiped out the Wave/EMBASSY fingerprint login hooks, and restored
the standard Windows (XP) login. d'oh!

I hope that Dell can post an update that can be safely and easily installed to make the fingerprint
and other security features work as intended, but as of 12/26/2008, I recommend not
trusting the posted updates, they don't seem to work.

Mike

Now the Fingerprint is working fine.

Dell made a new Software update and with that it works fine.

But the Service of Dell is bad. I will never never buy a Dell PC again. Support sad do this and i do this and after that the support sad i never sad you have to do this :emotion-43:. Also the support sad to me all is fixed but at that time it don`t work. And i never hear anything from the service.

bye Andreas

Hi everyone,

I have the same problem with my M4400 fingerprint reader, I am not able to enroll my fingerprint because the application say "Connect Fingerprint Sensor".  I have the latest driver/apps (of 26-Jan) and it still won't let me enroll.  Tried this forum tip and still no luck.  Anyone out there have a idea.  I am running Vista Business 32-Bit.  Thanks.

I was getting the "connect a fingerprint sensor" message. Adding the .dll files fixed mine on XP.

I had the same problem on a M4400, as far as the fingerprint scanner driver goes.  It is a 1,2 deal I found... you need the driver package first, R210495 - install and reboot. THEN install the newest Security portion for Control Point, which, while installed see's the FP scanner.  During the driver install (first step) I had to do custom and check the scanner option.  I had to go back and forth with Dell support a dozen times to get this far.  This software is sh%t in my opinion.  Every time I buy a Precision series laptop I regret it (I buy and setup 100's of Dell laptops a year).  I am not sure why I bother anymore, to be honest.

I am at a point where, when registering a fingerprint, it just sits there - it doesn't react to my fingerprint being scanned.  It USED to actually throw a stop error when I scanned my finger, that has gone away, but the scan still doesn't work.  WAY too much money to have to deal with this.  My time is worth a lot, to be honest.  I am making one more attempt to chat with tech support then I am demanding another laptop.

I have not had a fingerprint reader problem with recent sofware, but I'm using Latitude E6500's not the M4400.  On the E6500,
the
Dell_ControlPoint-Security-M_A11_R210495 driver pack and

Dell_ControlPoint-Security-M_A12_R219153 application are generally working OK, except that the Wave Document Manager
has a memory leak which will eventually cause accesses to the document vault to fail, but it takes accesses to generally more
than 1000 files to see the problem.

I do see the following issue.  As recommended, I uninstall the app, then the driver pack.  Then I install the driver pack.
then the app.  After re-installing the driver pack, the USB Smart Card Reader and Broadcom TPM show ! in Device Manager
and are not working.  The message is:

Windows cannot load the device driver for this hardware.
The driver may be corrupted or missing. (Code 39)

I've found that you then have to right-click on the device flagged with ! in the Device Manager, and select "Uninstall".
Then under "Action" select "Scan for Hardware Changes". 
Then it finds both of the devices and they indicate they are working normally.

I recommend also installing the latest
Dell_ControlPoint-System-Man_A11_R218884, since it seems that the security hardware may be a bit sensitive to
power management issues, and the ControlPoint System Manager may improve power management, standby /
resume, etc.

If your machine has a Broadcom USH, I recommend also searching for the latest firmware for it on the Dell Site,and updating.
I found Dell Firmware for Broadcom USH 1.2.00208.017, A07 and used it, and it's not bad.

I am still looking forward to the day when Dell posts an update to the ControlPoint Security Manager with all the 
Wave Embassy Trust Suite functionality working correctly.   

I owned dell latitude E4200 with windows 7 and got the same problem!

It's happen after I updated the ControlVault firmware from A09 to A14.

First the enrollment failed and after that the FP sensored undetected by the enrollment.

I suguest roll back the A09 firmware will restore everything to work agian.

Youri. 

Hello,

I don't know if the issue is still persisting but you should try that :

BROADCOM CORPORATION Dell ControlVault - Fully Managed by Win7 Biometric framework

IMPORTANT _ READ & FOLLOW ABSOLUTELY the Installation Instructions

For 64bits

www.dell.com/.../DriverFileFormats

For 32bits

www.dell.com/.../DriverFileFormats

For me, I tried it just few hours ago and it works perfectly on my Dell Latitude E4200 (Fully tested)

No more need of EMBASSY Security Center ! too heavy for windows system and installation too annoying