DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2479710 - Last Review: April 12, 2011 - Revision: 1.0

Hotfix Download Available
View and request hotfix downloads
 

On This Page

SYMPTOMS

Consider the following scenario:
  • You install the Remote Desktop Session Host role service 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\Remote Desktop Services\Remote Desktop Session Host\Security\Required secure RPC communication

    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Set client connection encryption level
  • 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 every 90 minute.
In this scenario, the Remote Desktop service crashes. Therefore, all remote desktop connections on the server are lost, and the data in these sessions may be lost.

Additionally, the following events are added to the System log and to the Application log:

Log Name: System
Source: Service Control Manager
Date: <date & time>
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:
The Remote Desktop Services service terminated unexpectedly. It has done this <n> time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.


Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: WINSTA.dll_unloaded, version: 0.0.0.0, time stamp: 0x4a5be0c3
Exception code: 0xc0000005
Fault offset: 0x000007fefd4316d0
Faulting process id: 0x160c
Faulting application start time: 0x01cb33f98ceefde9
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: WINSTA.dll

CAUSE

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

When the Group Policy settings are refreshed, the Remote Desktop service restarts to load the Group Policy changes. When the service restarts, it unloads and then reloads the Winsta.dll module. However, the service does not reload the Winsta.dll module correctly. Therefore, the Remote Desktop 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 is 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 Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must have the Remote Desktop Session Host role service installed.

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this 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 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. 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 x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.1.7600.20890711,16828-Jan-201106:17x64
Termsrv.dll6.1.7601.21650680,96028-Jan-201106:24x64

WORKAROUND

To work around this issue, disable the following Group Policy settings on the computer:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Required secure RPC communication

Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Set client connection encryption level

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 software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_613bf3192aa6e7ef927fef0fad4acd54_31bf3856ad364e35_6.1.7600.20890_none_c53d9a1c07c4e387.manifest
File versionNot applicable
File size1,106
Date (UTC)28-Jan-2011
Time (UTC)15:15
PlatformNot applicable
File nameAmd64_f3e5b7a7a1ff5bc383d04e0d9e2b5c51_31bf3856ad364e35_6.1.7601.21650_none_32b4a86ea8dd8a45.manifest
File versionNot applicable
File size1,106
Date (UTC)28-Jan-2011
Time (UTC)15:15
PlatformNot applicable
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20890_none_eb0e0674871f4fad.manifest
File versionNot applicable
File size29,203
Date (UTC)28-Jan-2011
Time (UTC)06:48
PlatformNot applicable
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.21650_none_ed1fa32a84254bd5.manifest
File versionNot applicable
File size29,749
Date (UTC)28-Jan-2011
Time (UTC)06:58
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,762
Date (UTC)28-Jan-2011
Time (UTC)15:15
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20890_none_f562b0c6bb8011a8.manifest
File versionNot applicable
File size10,688
Date (UTC)28-Jan-2011
Time (UTC)05:46
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.21650_none_f7744d7cb8860dd0.manifest
File versionNot applicable
File size11,234
Date (UTC)28-Jan-2011
Time (UTC)05:50
PlatformNot applicable

APPLIES TO
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2479710
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support