Symptoms

Consider the following scenario:

  • You have a server that's running Windows Server 2012 R2.

  • You use the Microsoft Intelligent Platform Management Interface (IPMI) driver to query for information on the server from the Baseboard Management Controller (BMC) through the Windows Management Instrumentation (WMI) interface. For example:

    1. You run WBEMTest.exe.

    2. You connect to the following namespace: root\hardware

    3. You click Enum classes.

    4. You choose the sensor and then open the instance.

In this scenario, sensor information is not obtained by the IPMI driver. Additionally, error 0x80041004 is generated.

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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 update, you must first have update 2919355 installed in Windows Server 2012 R2 or Windows 8.1.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) 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 8.1 and Windows Server 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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.3.960 0.17 xxx

    Windows 8.1 and Windows Server 2012 R2

    RTM

    GDR

  • 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 8.1 and Windows Server 2012 R2" section. MUM and 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 x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Ipmidrv.sys

6.3.9600.17230

68,608

10-Jul-2014

06:48

x86

For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Ipmidrv.sys

6.3.9600.17230

79,872

10-Jul-2014

07:45

x64

For all supported ARM-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Ipmidrv.sys

6.3.9600.17230

65,536

10-Jul-2014

05:26

Not Applicable

Additional file information for Windows 8.1 and for Windows Server 2012 R2

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

File name

X86_ipmidrv.inf_31bf3856ad364e35_6.3.9600.17230_none_907aac3f07071a81.manifest

File version

Not Applicable

File size

2,104

Date (UTC)

10-Jul-2014

Time (UTC)

10:10

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name

Amd64_ipmidrv.inf_31bf3856ad364e35_6.3.9600.17230_none_ec9947c2bf648bb7.manifest

File version

Not Applicable

File size

2,108

Date (UTC)

10-Jul-2014

Time (UTC)

12:24

Platform

Not Applicable

Additional files for all supported ARM-based versions of Windows 8.1

File name

Arm_ipmidrv.inf_31bf3856ad364e35_6.3.9600.17230_none_907d1e9707043947.manifest

File version

Not Applicable

File size

2,104

Date (UTC)

10-Jul-2014

Time (UTC)

08:05

Platform

Not Applicable

Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

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.