Application May Hang Calling LogonUser() API

Article translations Article translations
Article ID: 187936 - View products that this article applies to.
This article was previously published under Q187936
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When running an application that calls LogonUser() from multiple threads, the second call to LogonUser may cause the application to hang. This occurs when the user context under which the application is running does not have the SE_TCB_NAME privilege.

NOTE: To set this privilege for a user, you can grant the user the advanced user right to "Act as part of the operating system," in User Manager under User Rights Policy.


To resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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


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 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.


Article ID: 187936 - Last Review: October 26, 2013 - Revision: 2.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB187936

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from