Symptoms

Assume that the Win32_Environment Windows Management Instrumentation (WMI) class is queried by multiple requestors on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the query fails, and you receive the following error code:

0x80041001 (WBEM_E_FAILED)

For sample code to reproduce this issue, go to the "More information" section.

Cause

When the Win32_Environment class is queried, the registry hive of each user hive is loaded under the HKEY_USERS registry key, and the user-specific environmental properties of the registry hive are read. A registry hive that is loaded can be unloaded by any user who has the necessary permissions, unless a user still has a key to a subkey of the hive open. In this situation, the loading and unloading processes are protected by a critical section. However, the process of opening a hive key is not protected. Therefore, a hive that is loaded by one thread can be unloaded by another thread. In this situation, this issue occurs.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2 Service Pack 1 (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 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, milestone (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.21xxx

    Windows 7 and 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical 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

File name

File version

File size

Date

Time

Cimwin32.dll

6.1.7601.21958

1,342,976

05-Apr-2012

07:03

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

File name

File version

File size

Date

Time

Cimwin32.dll

6.1.7601.21958

2,059,264

05-Apr-2012

05:24

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

File name

File version

File size

Date

Time

Cimwin32.dll

6.1.7601.21958

4,281,344

05-Apr-2012

04:20

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 the Win32_Environment class, go to the following Microsoft website:

General information about the Win32_Environment classFor 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 7 and for Windows Server 2008 R2

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

File name

X86_a51f8a26ecd21a107fa841e4e84ce214_31bf3856ad364e35_6.1.7601.21958_none_e965b8be45381b18.manifest

File version

Not applicable

File size

719

Date (UTC)

05-Apr-2012

Time (UTC)

10:23

File name

X86_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_d214bf117d8c50ef.manifest

File version

Not applicable

File size

5,224

Date (UTC)

05-Apr-2012

Time (UTC)

07:43

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

File name

Amd64_e6ff67e8c054489da285368726ff6090_31bf3856ad364e35_6.1.7601.21958_none_3e8a5cd37a1bd942.manifest

File version

Not applicable

File size

723

Date (UTC)

05-Apr-2012

Time (UTC)

10:23

File name

Amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_2e335a9535e9c225.manifest

File version

Not applicable

File size

5,228

Date (UTC)

05-Apr-2012

Time (UTC)

08:30

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

File name

Ia64_1ba466913204adcf9731bd105ad8ee82_31bf3856ad364e35_6.1.7601.21958_none_6a1a5c4514db3ebf.manifest

File version

Not applicable

File size

721

Date (UTC)

05-Apr-2012

Time (UTC)

10:23

File name

Ia64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_d21663077d8a59eb.manifest

File version

Not applicable

File size

5,226

Date (UTC)

05-Apr-2012

Time (UTC)

08:30

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.