Certificate Propagation service crashes when you disconnect an RDS client from a Windows 7 or Windows Server 2008 R2-based RDS server

Assume that you have a Windows 7 or Windows Server 2008 R2-based Remote Desktop Services (RDS) server. You connect an RDS client to the server by using a smart card, and then you disconnect the connection immediately. In this situation, the Certificate Propagation service crashes and other services that are contained in the same Svchost group on the RDS server unexpectedly stop. Additionally, the following event is logged in the Application log:
�

Log Name: Application
Source: Application Error
Date: Date and time
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Description:
Faulting application name: svchost.exe_ProfSvc, version: file version, time stamp: time stamp,
Faulting module name: iedkcs32.dll, version: file version, time stamp: time stamp
Exception code: 0xc0000005
Fault offset: Offset
Faulting process id: Id
Faulting application start time: Time
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\System32\iedkcs32.dll

Note The following services that are contained in the same Svchost group as the Certification Propagation service are affected by this issue:

• Application Experience service
• Application Information service
• Application Management service
• Certificate Propagation service
• Group Policy Client service
• IP Helper service
• Server service
• User Profile service
• Task Scheduler service
• System Event Notification service
• Remote Desktop Configuration service
• Shell Hardware Detection service
• Windows Management Instrumentation service
• Windows Update service

This issue is caused by a race condition that occurs when the RDS client is connected to the server and then disconnected. Two�separate threads are created to handle the connection and disconnection events. The session that is used by the first thread is deleted by the second thread because of the race condition. Therefore, an access violation occurs in the first thread.

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 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 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. You must have the Remote Desktop Services role installed on the computer that is running Windows Server 2008 R2, or have the Remote�Server Administration Tools feature installed on the computer that is running Windows 7.

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

Registry information

To apply this hotfix, you do not have to make any changes to 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 7 and 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

  Version	Product	Milestone	Service branch
  6.1.760 1.22xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

• 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

To work around this issue, restart all the stopped services manually.

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2