Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Roaming user profiles are corrupted when a monitoring program executes a WMI query on a Windows Server 2008 R2 SP1-based RDS server


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Server 2008 R2 Service Pack 1 (SP1)-based Remote Desktop Services (RDS) server.
  • User accounts are configured to use roaming profiles when users log on to the RDS server by using a Remote Desktop Protocol (RDP) session.
  • You enable the following Group Policy setting to delete cached copies of the roaming user profiles when the users log off:
    Computer Configuration\Administrative Templates\System\User Profiles\Delete cached copies of roaming profiles
  • You run a monitoring program that periodically executes a Windows Management Instrumentation (WMI) query on the RDS server.
In this scenario, the roaming user profiles are corrupted, and the users cannot log on to the server.

↑ Back to the top


Cause

This issue is caused by a race condition that occurs when the WinLogon thread tries to obtain the roaming profiles from the roaming server and execute the WMI query at the same time.

↑ Back to the top


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 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 R2 SP1.

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:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

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 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:
    VersionProductMilestoneService branch
    6.1.760
    1.22xxx
    Windows Server 2008 R2SP1LDR
  • 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 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 x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.1.7601.223402,058,75225-May-201320:51x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.1.7601.223404,281,85625-May-201320:00IA-64

↑ Back to the top


Status

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

↑ Back to the top


More Information

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 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_bba626cc2058247522c9557d6dad01fd_31bf3856ad364e35_6.1.7601.22340_none_a384ccd5038394fc.manifest
File versionNot applicable
File size723
Date (UTC)26-May-2013
Time (UTC)02:23
PlatformNot applicable
File nameAmd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.22340_none_2e36060535e90633.manifest
File versionNot applicable
File size5,228
Date (UTC)25-May-2013
Time (UTC)21:26
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_a703e43c8ce0db40a2e3fa4d84053ba5_31bf3856ad364e35_6.1.7601.22340_none_d731ee8ec5f719e7.manifest
File versionNot applicable
File size721
Date (UTC)26-May-2013
Time (UTC)02:23
PlatformNot applicable
File nameIa64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.22340_none_d2190e777d899df9.manifest
File versionNot applicable
File size5,226
Date (UTC)25-May-2013
Time (UTC)20:43
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2831347
Revision : 1
Created on : 1/7/2017
Published on : 7/10/2013
Exists online : False
Views : 176