Biometric logon ceases to work after problematic install

Performance, hardware, software, general buying and gaming discussion..
Post Reply
Message
Author
jll
Posts: 5
Joined: Fri Oct 02, 2009 3:41 pm
Location: Brussels, Belgium

Biometric logon ceases to work after problematic install

#1 Post by jll » Fri Apr 16, 2010 4:07 am

Biometric logon used to work perfectly on my x200s running Windows 7 Professional. Yesterday I encountered problems when installing Tamos' CommTraffic: I got a BSOD near the end of the installation, then another one while my computer was unattended (and suspended I think). I sent the minidumps to Tamos who said that the crash had been cause by Virtual Box. Ok, since both products fiddle with network drivers I suppose I got into some sort of conflict. Later I managed to reinstall after disabling the Virtual Box network driver.

Since then (before and after the successful re-installation of CommTraffic) biometric logon doesn't work anymore. I get the message "Windows Security: your fingerprints have not been enrolled for logon". I tried removing my fingerprints then enrolling them again, which I could do without a hiccup.

Then I upgraded Authentec's stuff, enrolled again via "Manage your fingerprint data" in the Control Panel. I had to type my password. Then I tried enrolling again, and this time I was prompted to scan my finger. That worked perfectly.

(off topic: Authentec's enrollment app is not very intuitive: you enroll then what ? There's no explicitly "I'm done" button, I had to close the app by clicking the Close X button in the title bar)

This seems to prove that most of the fingerprint hardware and software is okay, but that there's something wrong in the interaction between the logon screen and the biometric stuff.

Does anybody have suggesttions on how to fix this, or at least in what direction I should investigate ?

Thanks,
Jean-Louis

RealBlackStuff
Admin
Admin
Posts: 17516
Joined: Mon Sep 18, 2006 5:17 am
Location: Mt. Cobb, PA USA
Contact:

Re: Biometric logon ceases to work after problematic install

#2 Post by RealBlackStuff » Fri Apr 16, 2010 7:01 am

Personally I would disconnect the FPR, disable it in BIOS and uninstall every last bit of Lenovo's Security software.
It is unreliable crapware.
A BIOS password and a (different) Hard Disk password are just as effective and a lot easier to manage.
Lovely day for a Guinness! (The Real Black Stuff)

Check out The Boardroom for Parts, Mods and Other Services.

Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “Thinkpad - General HARDWARE/SOFTWARE questions”

Who is online

Users browsing this forum: No registered users and 5 guests