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 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.Prerequisites
To apply this hotfix, your computer must be running Windows Server 2008 R2.
Installation instructions
To apply this hotfix, use one of the following methods:
Method 1
You can install this hotfix package to an existing Windows Server 2008 R2 installation. For this method, you do not have to also install hotfix 975535.
- First, disconnect any raw disks from the computer to start the operating system (OS).
- Apply this package to resolve the issue.
- Reconnect the raw disks to the computer.
Method 2
You can integrate this hotfix into the installation media. For this method, this hotfix must be applied together with hotfix 975535.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
975535 You cannot install Windows Server 2008 R2 on a computer that uses EFI
There is no particular order in which to apply these two hotfixes. These hotfixes must be applied to the Boot.wim file. The Boot.wim file loads the Microsoft Windows Preinstallation Environment (Windows PE) in order to install Windows. If you use Windows PE 3.0 to install Windows Server 2008 R2, the Boot.wim file is in the Windows PE image. If you use an installation media to install Windows Server 2008 R2, the Boot.wim file is in the installation media.
Note If the installation media is a DVD, you have to burn a new DVD that has the updated Boot.wim file.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2011542 How to manually apply hotfixes to the preinstall environment on the Windows installation disc
Registry information
To use 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 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 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
File name | File version | File size | Date | Time | Platform |
---|
Winload.efi | 6.1.7600.20617 | 640,904 | 14-Jan-2010 | 08:19 | Not applicable |
Winload.exe | 6.1.7600.20617 | 603,992 | 14-Jan-2010 | 08:16 | x64 |
Winresume.efi | 6.1.7600.20617 | 556,936 | 14-Jan-2010 | 08:19 | Not applicable |
Winresume.exe | 6.1.7600.20617 | 518,168 | 14-Jan-2010 | 08:16 | x64 |
Winload.efi | 6.1.7600.20617 | 640,904 | 14-Jan-2010 | 08:19 | Not applicable |
Winload.exe | 6.1.7600.20617 | 603,992 | 14-Jan-2010 | 08:16 | x64 |
Winresume.efi | 6.1.7600.20617 | 556,936 | 14-Jan-2010 | 08:19 | Not applicable |
Winresume.exe | 6.1.7600.20617 | 518,168 | 14-Jan-2010 | 08:16 | x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Winload.efi | 6.1.7600.20617 | 1,714,048 | 14-Jan-2010 | 07:03 | Not applicable |
Winload.efi | 6.1.7600.20617 | 1,714,048 | 14-Jan-2010 | 07:03 | Not applicable |