This hotfix resolves the following issues on a computer that is running an x64-based version of Windows Server 2008 R2.
The operating system only supports a maximum of 128 processors in the xAPIC mode.
Some computers may only support a maximum of 128 processors in the xAPIC mode if only 128 processors can have the smaller APIC IDs than a value of 255.
The computer restarts unexpectedly and you receive a Stop error during the startup process. This issue occurs after you enable the x2APIC mode in the BIOS.
Consider the following scenario:
You have some devices that require lots of message-signaled interrupts (MSI) extended on a computer that has multiple processors installed.
You enable the x2APIC mode in the operating system.
You try to shut down the computer.
In this scenario, the computer crashes and you receive a Stop error message that resembles the following:
STOP: 0x0000005C HAL_INITIALIZATION_FAILED
These issues occur because the x2APIC mode is disabled on a computer that is running an x64-based version of Windows Server 2008 R2.
After you install this hotfix, the x2APIC mode can be enabled on a computer that is running Windows Server 2008 R2, and the computer can support more than 255 processors.
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 Web site:
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.
To apply this hotfix, you must be running Windows Server 2008 R2.
After you install this hotfix, use one of the following methods to enable the x2APIC mode on a computer that is running an x64-based version of Windows Server 2008 R2:
Enable the "x2APIC" mode in BIOS firmware After you install this hotfix on a computer that is running an x64-based version of Windows Server 2008 R2, you can enable the x2APIC mode in BIOS, and then you can start the computer.
Note If the x2APIC mode is enabled in BIOS, you cannot disable the x2APIC mode by using the options of the bcdedit command.
Enable the "x2APIC" mode by using the options of the "bcdedit" command If you do not enable the x2APIC mode in BIOS, you have to use this method. The following are the commands that enable and disable the x2APIC mode:
bcdedit /set x2apicpolicy enable
bcdedit /set x2apicpolicy disable
To use the hotfix in this package, you do not have to make any changes to the registry.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a 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 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:
Windows 7 and Windows Server 2008 R2
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 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 x64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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