Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An update for Windows Recovery is available for Windows 7 and Windows Server 2008 R2


View products that this article applies to.

INTRODUCTION

An update for Windows Recovery is available for Windows 7 and Windows Server 2008 R2. This update resolves an issue in which Windows Recovery incorrectly starts. This issue can occur if you use the System Key utility (Syskey) to enable encryption for the Windows Accounts Database, and then you enter your password incorrectly several times. This update requires specific configuration of the Windows Recovery Image, WINRE.WIM.
  • If the version of Windows that you are running is configured by an OEM, please contact the OEM vendor for more information.
  • If the version of Windows that you are running is configured by your organization, please contact the IT support team of your organization for more information.
  • If you are an OEM or on the IT support team and have to be able to configure this update, please see steps in the following section.

↑ Back to the top


More Information

If you use Syskey to enable encryption, and then you incorrectly enter your password in the logon screen, Windows Recovery incorrectly starts. This update resolves this issue.

Windows Recovery Environment (Windows RE) is an extensible recovery platform that is based on Windows Preinstallation Environment (Windows PE). When a computer does not start, Windows automatically fails over into this environment, and the Startup Repair tool in Windows RE automates the diagnosis and repair. For more information about Windows RE, see the Technet Article: What is Windows RE?

Syskey provides an extra line of defense against password-cracking software. Syskey uses strong encryption techniques to help secure account password information that is stored in the Security Account Manager (SAM) database or in directory services. For more information about Syskey, see the Technet Article: System Key Utility Technical Overview.


Information on how to update Windows Recovery images

Warning This section contains steps should only be performed by a qualified technical person who is familiar with the Windows recovery mechanism. Serious problems might occur if you perform the steps incorrectly. Incorrect steps can leave windows recovery mechanism in unrecoverable state. Therefore, make sure that you follow these steps carefully. For added protection, perform a complete system backup before you continue. Also, be aware that you may need the Windows installation media that was originally used to install the operating system.

For more information about the procedures and terminology used in this article, visit the following Microsoft webpages:
The following procedures should be performed by an administrative user at an administrative command prompt. These procedures only contain guidance steps for a generic installation. These steps may be different for your installation.

Locate and copy an installed version of WinRE.wim

Assuming that WinRE.wim is already configured on the system, follow these steps:



  1. Type the following command to find the location of the installed Windows RE image file (Winre.wim):

    reagentc /info

    Notes
    • The WinRE.wim file may have the SYSTEM and HIDDEN file attributes set. Use the Attrib command to remove these attributes.
    • WinRE.wim may be in a hidden directory or a hidden partition. Use the DIR /A command to find hidden folders and files. If it is necessary, use the Diskpart utility to unhide the partition.
  2. Note the location of the WinRE.wim. For example, <WinREdrive>\WindowsRE\<GUIID>.
  3. Copy the currently installed WinRE.wim file to a local folder such as C:\WinRE. The local folder must differ from the installation location. Make sure that you keep a backup of C:\WinRE\WinRE.wim.

Locate and copy WinRE.wim from the installation media

Assuming that WinRE.wim is not configured on the system, follow these steps:
  1. Locate the WinRE.wim file on the Windows installation media that was used to install the operating system.
  2. Create the following local folders:
    • C:\OS_Image
    • C:\OS_Image\Mount
    • C:\Winre
  3. Copy the Install.wim file from Windows installation media to C:\OS_Image. If the installation media is located on drive D, the Install.wim file will be located in the D:\sources folder.
  4. Type the following DISM command to mount the Install.wim file:

    DISM /mount-wim /wimfile:C:\OS_Image\Install.wim /index:1 /MountDir:C:\OS_Image\mount
  5. Type the following command to copy the Windows RE image (Winre.wim) file from the mounted Windows image to C:\WinRE:


    Copy C:\OS_image\mount\windows\system32\recovery\WinRE.wim C:\winre\
  6. Type the following command to unmount the mounted Windows image:


    DISM /unmount-wim /MountDir:C:\OS_Image\mount /discard
  7. Remove the C:\OS_Image and C:\OS_Image\Mount folders together with the Install.wim file that was copied to them.

Inject the KB2883457 security update package to WinRE.wim

  1. Copy the KB2883457 security update package to folder C:\WindowsUpdate.
  2. Create the following local folder:
    • C:\WinRE\Mount
  3. Type the following command to mount the Winre.wim file:


    DISM /mount-wim /wimfile:C:\winre\WinRE.wim /index:1 /MountDir:C:\winre\mount
  4. Type the following command to insert the security package into the mounted Winre.wim file:


    DISM /image:C:\Winre\mount /Add-Package /Packagepath:C:\WindowsUpdate
  5. Type the following command to verify that the security package is integrated successfully:


    DISM /image:C:\winre\mount /Get-Packages
  6. Type the following command to commit the changes to the Winre.wim file:


    DISM /unmount-wim /MountDir:C:\Winre\mount /commit

Deploy or copy a modified WinRE.wim

If WinRE.wim is already installed and configured, follow these steps:
  1. Move C:\WinRE\WinRE.wim to the folder where WinRE.wim was located earlier. For example, to <WinREdrive>\WindowsRE\<GUIID>. Overwrite the existing WinRE.wim if you are prompted.
  2. Use the Attrib command to restore the SYSTEM and HIDDEN file attributes to the previous settings.
  3. If <WinREdrive> was previously hidden earlier, use the Diskpart utility to hide the partition again.
  4. Deploy and configure the customized Windows RE image if it was not located from installation media.
  5. The C:\WinRe and C:\WinRE\Mount folders can now be removed.

Validate and rollback if it is necessary

  1. Verify that you can start in the modified WINRE environment and can perform previously configured recovery functions.
  2. If validation fails, make sure that you revert the changes that were made. To do this, follow these steps:
    1. Unconfigure and remove the WinRE.wim if it was copied from installation media.
    2. Replace the modified WinRE.wim with the backup copy if you modified an already configured WinRE.wim.

↑ Back to the top


Download Information

The following files are available for download from the Microsoft Download Center:


For all supported x86-based versions of Windows 7

Download Download the package now.

For all supported x64-based versions of Windows 7

Download Download the package now.

For all supported x64-based versions of Windows Server 2008 R2

Download Download the package now.

Release Date: October 8, 2013

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

↑ Back to the top


File information

Windows 7 and Windows Server 2008 R2 file information
  • 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.7601. 18xxxWindows 7 and Windows Server 2008 R2SP1GDR
    6.1.7601. 22xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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.
Note The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.


For all supported x86-based versions of Windows 7

File nameFile versionFile sizeDateTimePlatform
Bootrec.exe6.1.7601.18246299,00828-Aug-201300:59x86
Recenv.exe6.1.7601.18246602,11228-Aug-201300:59x86
Startrep.exe6.1.7601.18246528,89628-Aug-201300:59x86
Bootrec.exe6.1.7601.22435299,00828-Aug-201301:02x86
Recenv.exe6.1.7601.22435602,11228-Aug-201301:03x86
Startrep.exe6.1.7601.22435528,89628-Aug-201301:02x86

For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

File nameFile versionFile sizeDateTimePlatform
Bootrec.exe6.1.7601.18246365,05628-Aug-201301:14x64
Recenv.exe6.1.7601.18246742,40028-Aug-201301:14x64
Startrep.exe6.1.7601.18246620,03228-Aug-201301:14x64
Bootrec.exe6.1.7601.22435365,05628-Aug-201301:16x64
Recenv.exe6.1.7601.22435741,88828-Aug-201301:16x64
Startrep.exe6.1.7601.22435620,03228-Aug-201301:16x64

↑ Back to the top


Acknowledgments

Microsoft thanks the following for working with us to help protect customers:
  • Meron Sellem for working with us on the Windows Recovery Environment Startup Repair issue

↑ Back to the top


Keywords: kbbug, kbexpertiseinter, kbfix, kblangall, kbmustloc, kbsecbulletin, kbsecreview, kbsecurity, kbsecvulnerability, kbsurveynew, kb, atdownload

↑ Back to the top

Article Info
Article ID : 2883457
Revision : 3
Created on : 4/13/2020
Published on : 4/13/2020
Exists online : False
Views : 267