UNSOLVED
Closed
Finger print reader causes long delay before login screen (D820)
Hi,
On my new D820, when I have the fingerprint / biometric reader enabled and have Windows login set to accept finger prints or passwords, there is a very long delay *after* I hit Ctrl-Alt-Del but before I can swipe my finger or type my password. The delay can be from 1.5 to 2 minutes (I've timed it) and there's a message saying something like "Updating user profile". I'm logging into a Windows domain (this is a company computer) but it happens whether I'm connected or not.
Our corporate IT support doesn't cover the fingerprint reader yet as it's too new (or something). I found some threads here about updating the Wave / Embassy Security Center software, but it's already up-to-date.
Is anyone else experiencing these incredibly long delays after a reboot (or even a cold bootup)? I can type my password in about 2-3 seconds, so with this delay it's not worth it for me to use the fingerprint reader, even for the fun "parlor trick" effect.
On my new D820, when I have the fingerprint / biometric reader enabled and have Windows login set to accept finger prints or passwords, there is a very long delay *after* I hit Ctrl-Alt-Del but before I can swipe my finger or type my password. The delay can be from 1.5 to 2 minutes (I've timed it) and there's a message saying something like "Updating user profile". I'm logging into a Windows domain (this is a company computer) but it happens whether I'm connected or not.
Our corporate IT support doesn't cover the fingerprint reader yet as it's too new (or something). I found some threads here about updating the Wave / Embassy Security Center software, but it's already up-to-date.
Is anyone else experiencing these incredibly long delays after a reboot (or even a cold bootup)? I can type my password in about 2-3 seconds, so with this delay it's not worth it for me to use the fingerprint reader, even for the fun "parlor trick" effect.
- Since first posting the problem I've disabled the fingerprint reader, the TPM chip, and and biometric login software as completely as I can figure (in BIOS when possible). I *still* get the delay, though, when I log in immediately after being given the option. (If I walk away from the computer for a minute or two as it boots, the delay happens in that time, *before* I log in.)
Yes, there's a Userenv event (type: Warning) in my Application Event Log during that time. Event number is 1517, it's always followed by approximately 1:15 before the next event, and the description is:
Windows saved user xxx\yyyyy registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
It's always followed by four ccEvtMgr events concerning Symantec services (which all happen within two seconds) and then another ~1:15 gap before an AgentSrv event having this description:
The description for Event ID ( 0 ) in Source ( AgentSrv ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Service/Server started.
There are no other gaps between events of sufficient time, near startup. It's really annoying, so I do my best to restart as little as possible. - Brief addendum to my previous post: Event 1517 is happening during logoff / shutdown, and before the reboot, according to a comparison of timestamps with Event 6005 (Event log service startup). I guess this leaves Event 0, AgentSrv, as my main suspect.
rcurley
10 Posts
568
0
Posted September 30th, 2006 20:00