Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/250042

From BetaArchive Wiki

Article ID: 250042

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0, Terminal Server Edition



This article was previously published under Q250042

SYMPTOMS

Periodically all clients see delayed "buffered" keyboard input and programs temporarily are not responsive.

CAUSE

This issue can occur when a user logs on to the server with client printer mapping enabled.

Client printer mapping causes a large number of writes to the registry when a user logs in. These then have to be flushed to disk, and the registry flusher holds the registry lock exclusively while flushing. So, any program that tries to access the registry must wait until the flusher releases the lock, which can take several seconds.

RESOLUTION

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack



Windows Base Terminal Server, Version 4.0

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack




STATUS

Windows NT Server 4.0, Terminal Server Edition

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Windows Base Terminal Server, Version 4.0

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbbug kbfix kbprint kbqfe kbenv kbhotfixserver KB250042