A Terminal Services session to a Windows 2000-based computer stops responding if a user logs off after the user quits a 16-bit Windows program (891577)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

A user logs on to a Microsoft Windows 2000-based computer through a Terminal Services session, and then runs a 16-bit Windows program. After the user quits the 16-bit Windows program, the Ntvdm.exe process does not quit. Instead, the Ntvdm.exe process remains running. If the Override settings from the user profile and Client Connection manager wizard option is configured on the server, the Terminal Services session may stop responding (hang) when the user logs off. You experience these symptoms after you install a security update on the Windows 2000-based computer. This security update is documented in the following Microsoft Knowledge Base article:

840987 MS04-032: Security update for Microsoft Windows

CAUSE

This problem occurs because 16-bit processes run under a shared Ntvdm.exe process. The shared Windows-on-Windows (WOW) process does not unregister itself when the WOW process processes the quit message for the Windows 16-bit program.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

This hotfix requires Windows 2000 Service Pack 4 (SP4).

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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
----------------------------------------------------------
20-Dec-2004  17:29  5.0.2195.7011     46,352  Basesrv.dll      
21-Sep-2003  08:45  5.0.2195.6824    236,304  Cmd.exe  
18-Jun-2004  07:05  5.0.2195.6945    231,184  Gdi32.dll 
18-Jun-2004  07:05  5.0.2195.6946    712,464  Kernel32.dll  
24-Mar-2004  10:17  5.0.2195.6898     37,136  Mf3216.dll   
24-Mar-2004  10:17  5.0.2195.6824     54,544  Mpr.dll      
18-Jun-2004  07:05  5.0.2195.6928    335,120  Msgina.dll 
24-Mar-2004  10:17  5.0.2195.6892     90,264  Rdpwd.sys   
24-Mar-2004  10:17  5.0.2195.6897    403,216  User32.dll    
06-Aug-2003  06:14  5.0.2195.6794    385,808  Userenv.dll 
10-Aug-2004  11:51  5.0.2195.6966  1,632,624  Win32k.sys  
25-Aug-2004  06:59  5.0.2195.6970    182,544  Winlogon.exe    
18-Jun-2004  07:05  5.0.2195.6946    244,496  Winsrv.dll

WORKAROUND

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this problem, follow these steps on the server:
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate, and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW

  3. In the right pane, right-click DefaultSeparateVDM, and then click Modify.
  4. In the Value data box, type yes, and then click OK.
  5. Quit Registry Editor.
Note You may have to restart the server after you follow these steps.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information about Microsoft Security Bulletin MS04-032, visit one of the following Microsoft Web sites: 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 file naming schema for Microsoft Windows software update packages

For additional information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbBug kbfix kbWin2000preSP5fix kbHotfixServer kbQFE KB891577 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.