Biometic Authentec Unavailable but shows up fine in Device manager

[jetspeedz]

I've tried everything possible to get this problem solved and I'm out of solutions. New Sony laptop has Authentec Inc AES1660 biometric finger print reader. The Oem sony drivers and the latest install fine and the device shows up fine and working under device manager but windows 7 x64 under control panel biometric shows the device as "Unavailable" neither the protector suite or Authentec software work b/c windows does not recognize the device being there. I have looked all over the net and I'm not the only one with this problem. Others who made similar posts on Authentec website have not received any response.

Hoping someone here has a solution?

 

[TVeblen]

I have no experience with any finger print readers. But here are my thoughts:
The device is recognized and working in Device Manager and that means the system and OS are ready to use it.
I'm thinking the device does not show up in Control Panel because it now must somehow be 'connected' or 'started'. You know how you connect a camera or USB stick for the first time, and drivers are loaded for the device, then "your device is ready to use", but when you unplug the device it disappears from the system. It's ready to go, but just disconnected.

I would check the manual to see if there is a way to activate (connect or start) the device. It could be an Fn key (similar to the volume keys, etc) to toggle the device on and off on the keyboard. Or software that is supposed to be installed to create some sort of Control Panel. There might even be a switch on the laptop.

It seems logical that there would be a way to activate/deactivate the device on as as-needed basis.

 

[jetspeedz]

The reader is built into the latop it is not an external device. Also there is no way to activate it other than the simple option in control panel with is already turned on and a windows service which is set to auto. I'm trying to avoid having to do a system restore as i have already put over 100hrs into tweaking it and cleaning it up.

I would assume this is a software problem more than anything b/c device manager sees the hardware and it is active and well. I'll spend another weekend trying to mess with it. Worse comes worse I'll have to start all over or live without it.