You are currently offline, waiting for your internet to reconnect

Desktop Does Not Lock When You Remove Your USB Smart Card Reader

This article has been archived. It is offered "as is" and will no longer be updated.
When you unplug your universal serial bus (USB) smart card reader from your computer, the desktop does not lock. This issue occurs even though you have applied a Group Policy setting to lock the desktop when the smart card reader is unplugged.

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File Information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name   --------------------------------------------------------------   17-Jul-2003  09:50  5.0.2195.6738      42,256  Basesrv.dll         17-Jan-2003  08:06  5.0.2195.6656     236,304  Cmd.exe             17-Jul-2003  09:50  5.0.2195.6762     222,992  Gdi32.dll           17-Jul-2003  09:50  5.0.2195.6741     711,440  Kernel32.dll        17-Jul-2003  09:50  5.0.2195.6751     333,072  Msgina.dll          07-Apr-2003  21:54  5.0.2195.6701      90,232  Rdpwd.sys   15-Jul-2003  14:08  5.0.2195.6776   4,858,368  Sp3res.dll          17-Jul-2003  09:50  5.0.2195.6785     380,176  User32.dll          17-Jul-2003  09:50  5.0.2195.6745     385,808  Userenv.dll         16-Jul-2003  15:32  5.0.2195.6784   1,628,784  Win32k.sys   17-Jul-2003  09:20  5.0.2195.6785     182,032  Winlogon.exe        17-Jul-2003  09:50  5.0.2195.6775     243,984  Winsrv.dll          17-Jul-2003  09:50  5.0.2195.6741     711,440  Kernel32.dll        17-Jul-2003  09:50  5.0.2195.6784   1,628,784  Win32k.sys   17-Jul-2003  09:50  5.0.2195.6775     243,984  Winsrv.dll       
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages

Article ID: 821873 - Last Review: 10/26/2013 18:52:49 - Revision: 2.5

Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB821873