Windows Server 2008 R2 starts into Windows Recovery Environment
This issue occurs on some Unisys or NEC servers that are running Windows Server 2008 R2 Service Pack 1 (SP1) after you install Microsoft security advisory: Availability of SHA-2 code signing support for Windows 7 and Windows Server 2008 R2: March 10, 2015 on the server.
Note In this situation, you can still start Windows successfully if you insert a bootable DVD (such as a Windows installation disc) in the DVD drive, but don't actually select to start from it.
This issue occurs because of a firmware error on a specific server hardware. The firmware error is caused by a change to the Windows boot loader.
To fix this issue, we've released a hotfix for Windows Server 2008 R2. Even though this issue has only been observed in Windows Server 2008 R2, the hotfix also applies to Windows 7.
Hotfix informationImportant If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't available for that language.
PrerequisitesTo apply this hotfix, install Service Pack 1 in Windows 7 or Windows Server 2008 R2. ERROR: PhantomJS timeout occurred
Registry informationTo use the hotfix in this package, you don't have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix doesn't replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
See the terminology that Microsoft uses to describe software updates.
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2
- 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.22xxx Windows 7 or Windows Server 2008 R2 SP1 LDR 6.1.760 1.23 xxx Windows 7 or 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 in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
x86 Windows 7
|File name||File version||File size||Date||Time||Platform||SP requirement||Service branch|