Application Using SetOwner May Hang Windows NT User Interface
Article ID: 177684
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q177684
SYMPTOMS
An application runs under Windows NT and the computer appears to stop
responding (hang). The user interface is frozen and it does not respond to
mouse and keyboard input.
The computer can still be accessed from the network, but you are unable to
start services that require a new process to be started.
CAUSE
The application used the Win32 API SetOwner and defined window_1 to be
owned by window_2, but also window_2 to be owned by window_1. When looking
for the top-level window of the hierarchy (the one without an owner), the
Win32 subsystem runs into an endless loop.
The ownership relations created by the applications will render the
application unusable for the operating system, but must not cause the User
Interface to hang.
RESOLUTION
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
STATUS
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.
Keywords: kbhotfixserver kbqfe kbbug kbfix KB177684