Fingerprint reader vs. Windows Update

[greghead]

I have a T43. It's Tuesday. Time for another round of Microsoft security updates. I did them today. Rebooted as instructed.

Now when the screensaver kicks in with the password option, the prompt doesn't let me use the fingerprint reader. Where the text would appear instructing me to swipe my finger, instead it now says "Waiting for system services...". And stays "waiting" for at least 5 minutes. I have to use CTRL+ALT+DEL then type the password, the old-fashioned way.

Not a show-stopper, but annoying. I like the fingerprint reader, especially to avoid typing pwd when other people are around.

Anyone else seeing this yet? Any solutions?

I'll debug this more when I have time: Try additional warm and cold reboots. Maybe try a ThinkPad software update for the fingerprint reader (although I hate futzing with updates). Maybe other ideas.

Meanwhile I wanted to go ahead and report this for everyone FYI.

[christopher_wolf]

I have a T43. It's Tuesday. Time for another round of Microsoft security updates. I did them today. Rebooted as instructed.

Now when the screensaver kicks in with the password option, the prompt doesn't let me use the fingerprint reader. Where the text would appear instructing me to swipe my finger, instead it now says "Waiting for system services...". And stays "waiting" for at least 5 minutes. I have to use CTRL+ALT+DEL then type the password, the old-fashioned way.

Not a show-stopper, but annoying. I like the fingerprint reader, especially to avoid typing pwd when other people are around.

Anyone else seeing this yet? Any solutions?

I'll debug this more when I have time: Try additional warm and cold reboots. Maybe try a ThinkPad software update for the fingerprint reader (although I hate futzing with updates). Maybe other ideas.

Meanwhile I wanted to go ahead and report this for everyone FYI.

Sounds like fast user switching got re-enabled by the Windows Update; for the FPR to work properly, the fast-user switching has to be off if I remember correctly. Usually, you can't toggle the setting because the FPR has an overlaying layer that is called whenever the shell wants to ask the user for a password.

[greghead]

Thanks, Christopher.

First, the fingerprint reader is working again now. I did a power off/on and it's back to normal. A warm reboot apparently wasn't sufficient.

As for Fast User Switching: Actually I've never had FUS enabled on this laptop. When I go to User Accounts and click "Change the way users logon and logff", Windows gives me this message:

"A recently installed program has disabled the Welcome screen and Fast User Switching. To restore these features, you must uninstall the program. The following file name might help you identify the program that made the change: vrlogon.dll".

Would vrlogon.dll be the custom IBM logon for the FPR?

[christopher_wolf]

Thanks, Christopher.

First, the fingerprint reader is working again now. I did a power off/on and it's back to normal. A warm reboot apparently wasn't sufficient.

As for Fast User Switching: Actually I've never had FUS enabled on this laptop. When I go to User Accounts and click "Change the way users logon and logff", Windows gives me this message:

"A recently installed program has disabled the Welcome screen and Fast User Switching. To restore these features, you must uninstall the program. The following file name might help you identify the program that made the change: vrlogon.dll".

Would vrlogon.dll be the custom IBM logon for the FPR?

Yup, that is normal.

Because of the FPR, Windows will not let you toggle FUS; apparently it conflicts with the way the FPR handles things. Windows Updates, however, have a tendency to take the system configs back to the settings on a stock Windows XP install; simply just turning stuff you turned off back on, etc. It might have enabled FUS despite the lock and caused a problem with the FPR vrlogon.dll.

Although I didn't know you only tried a warm reboot to begin with.

[greghead]

Although I didn't know you only tried a warm reboot to begin with.

Grasshopper should not post before trying warm reboot?