Terminal Services service crashes when Group Policy settings are refreshed in Windows Server 2008

Applies to: Windows Server 2008 Service Pack 2Windows Server 2008 DatacenterWindows Server 2008 Datacenter without Hyper-V More

Symptoms


Consider the following scenario:
  • You install the Terminal Services server role on a computer that is running Windows Server 2008 R2.
  • You enable the following Group Policy settings on the computer:
    Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Require secure RPC communication
    Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Set client connection encryption level communication
  • The Group Policy settings are refreshed by using one of the following methods:
    • You manually update the Group Policy settings by running the gpupdate /force command.
    • The Group Policy settings are automatically refreshed. This occurs every 90 minutes.
In this scenario, the Terminal Services service crashes. Therefore, all Remote Desktop connections on the server are lost, and the data in the Remote Desktop sessions may be lost.

Additionally, the following events are logged in the System log and in the Application log:

Cause


This issue occurs because the Terminal Services service does not correctly reload the Winsta.dll module every time that the Group Policy settings are refreshed.

After the Group Policy settings are refreshed, the Terminal Services service restarts to load the new Group Policy settings. When the service restarts, the service unloads and then reloads the Winsta.dll module. However, the service does not reload the Winsta.dll module correctly. Therefore, the Terminal Services service crashes when a function in the Winsta.dll module is called. 

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 website: 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2). Additionally, you must have the Terminal Services server role installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix if you stop the Terminal Services service before you apply the hotfix. 

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6002.22790451,58402-Feb-201216:35x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6002.22790550,40002-Feb-201217:58x64

Workaround


To work around this issue, disable the following Group Policy settings on the computer:
Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Require secure RPC communication
Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Set client connection encryption level communication

Status


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

More Information


For more information about a similar issue in Windows Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2479710 Remote Desktop service crashes when Group Policy settings are refreshed in Windows Server 2008 R2 after you enable the "Required secure RPC communication" and "Set client connection encryption level" Group Policy settings

For more information about software update terminology, 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

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22790_none_90ae12456ad0ee28.manifest
File versionNot Applicable
File size40,075
Date (UTC)02-Feb-2012
Time (UTC)16:51
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22790_none_ecccadc9232e5f5e.manifest
File versionNot Applicable
File size40,131
Date (UTC)02-Feb-2012
Time (UTC)18:15
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22790_none_f721581b578f2159.manifest
File versionNot Applicable
File size18,965
Date (UTC)02-Feb-2012
Time (UTC)16:40
PlatformNot Applicable