IPMI subsystem cannot obtain power information when the BMC interrupt is enabled on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

Applies to: Windows Vista Service Pack 2Windows Vista BusinessWindows Vista Business 64-bit Edition More

Symptoms


Assume that you try to use an application to obtain power information from a computer that has the baseboard management controller (BMC) interrupt enabled. The application uses the satellite management controllers in the Intelligent Platform Management Interface (IPMI) subsystem to connect to the BMC. In this situation, the application cannot obtain power information.

This issue occurs on a computer that is running one of the following operating systems:
  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2

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 one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

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:

968849 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:

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

Registry information

To apply the hotfix in this package, 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 Vista and 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.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • 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 and for Windows Vista" section. MUM files 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 Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.0.6002.2279465,53609-Feb-201213:37x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.0.6002.2279477,82409-Feb-201214:30x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.0.6002.22794162,81609-Feb-201216:01IA-64
Windows 7 and Windows Server 2008 R2 file information notes
  • 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:
    VersionProductMilestoneService branch
    6.1.760
    1.17xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important 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 and for Windows 7" 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 7
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.1.7601.1777665,53610-Feb-201203:44x86
Ipmidrv.sys6.1.7601.2192066,04810-Feb-201203:37x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.1.7601.1777678,84810-Feb-201204:22x64
Ipmidrv.sys6.1.7601.2192078,84810-Feb-201204:08x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Ipmidrv.sys6.1.7601.17776168,44810-Feb-201203:20IA-64
Ipmidrv.sys6.1.7601.21920168,44810-Feb-201203:33IA-64

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 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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameX86_ipmidrv.inf_31bf3856ad364e35_6.0.6002.22794_none_fdbbc397021b95fc.manifest
File versionNot Applicable
File size1,674
Date (UTC)10-Feb-2012
Time (UTC)08:30
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_ipmidrv.inf_31bf3856ad364e35_6.0.6002.22794_none_59da5f1aba790732.manifest
File versionNot Applicable
File size1,676
Date (UTC)10-Feb-2012
Time (UTC)08:30
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_ipmidrv.inf_31bf3856ad364e35_6.0.6002.22794_none_fdbd678d02199ef8.manifest
File versionNot Applicable
File size1,675
Date (UTC)10-Feb-2012
Time (UTC)08:30
PlatformNot Applicable

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

Additional files for all supported x86-based versions of Windows 7
File nameX86_ipmidrv.inf_31bf3856ad364e35_6.1.7601.17776_none_fd7180b54a034787.manifest
File versionNot Applicable
File size2,087
Date (UTC)10-Feb-2012
Time (UTC)06:17
PlatformNot Applicable
File nameX86_ipmidrv.inf_31bf3856ad364e35_6.1.7601.21920_none_fe2b2d4662fdc0b9.manifest
File versionNot Applicable
File size2,087
Date (UTC)10-Feb-2012
Time (UTC)06:06
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_ipmidrv.inf_31bf3856ad364e35_6.1.7601.17776_none_59901c390260b8bd.manifest
File versionNot Applicable
File size2,091
Date (UTC)10-Feb-2012
Time (UTC)07:16
PlatformNot Applicable
File nameAmd64_ipmidrv.inf_31bf3856ad364e35_6.1.7601.21920_none_5a49c8ca1b5b31ef.manifest
File versionNot Applicable
File size2,091
Date (UTC)10-Feb-2012
Time (UTC)07:03
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_ipmidrv.inf_31bf3856ad364e35_6.1.7601.17776_none_fd7324ab4a015083.manifest
File versionNot Applicable
File size2,089
Date (UTC)10-Feb-2012
Time (UTC)07:04
PlatformNot Applicable
File nameIa64_ipmidrv.inf_31bf3856ad364e35_6.1.7601.21920_none_fe2cd13c62fbc9b5.manifest
File versionNot Applicable
File size2,089
Date (UTC)10-Feb-2012
Time (UTC)06:54
PlatformNot Applicable