Consider the following scenario. You install Windows Management Framework 3.0 on a computer (computer A) that is running Windows Server 2008 or Windows Server 2008 R2. On a computer (computer B) that is running Windows Server 2012, you try to use Server Manager to retrieve performance data for computer A. In this scenario, Server Manager does not retrieve the performance data correctly.
This issue occurs because Performance Data Helper (PDH) functions cannot open log files that are generated for an impersonated thread. After a PDH function opens a log file, the function creates a separate helper thread to read samples from the file. However, the helper thread is not passed the token that belongs to the impersonated user. In this situation, the thread uses the default token that belongs to the process. Therefore, the PDH function may have insufficient permissions to retrieve the performance data.
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 one of the following operating systems:
Windows Server 2008 Service Pack 2 (SP2)
Windows Server 2008 R2 Service Pack 1 (SP1)
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:
How to obtain the latest service pack for Windows Server 2008
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:
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 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.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
2
.
18xxx
Windows Server 2008
SP2
GDR
6.0.600
2
.
22xxx
Windows Server 2008
SP2
LDR
Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
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 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 Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Advapi32.dll
6.0.6002.18596
800,768
08-Mar-2012
15:12
x86
Advapi32.dll
6.0.6002.22814
801,792
08-Mar-2012
14:49
x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Advapi32.dll
6.0.6002.18596
1,067,008
08-Mar-2012
15:43
x64
Advapi32.dll
6.0.6002.22814
1,067,008
08-Mar-2012
15:38
x64
Advapi32.dll
6.0.6002.18596
800,768
08-Mar-2012
15:12
x86
Advapi32.dll
6.0.6002.22814
801,792
08-Mar-2012
14:49
x86
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Advapi32.dll
6.0.6002.18596
1,963,008
08-Mar-2012
14:56
IA-64
Advapi32.dll
6.0.6002.22814
1,961,984
08-Mar-2012
14:12
IA-64
Advapi32.dll
6.0.6002.18596
800,768
08-Mar-2012
15:12
x86
Advapi32.dll
6.0.6002.22814
801,792
08-Mar-2012
14:49
x86
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
Version
Product
Milestone
Service branch
6.1.760
1.17xxx
Windows Server 2008 R2
SP1
GDR
6.1.760
1.21xxx
Windows Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Advapi32.dll
6.1.7601.17792
877,568
08-Mar-2012
06:33
x64
Advapi32.dll
6.1.7601.21938
877,568
08-Mar-2012
06:14
x64
Advapi32.dll
6.1.7601.17792
640,512
08-Mar-2012
05:32
x86
Advapi32.dll
6.1.7601.21938
640,512
08-Mar-2012
05:27
x86
For all supported IA-64-based versions of Windows Server 2008 R2
Back to the top
