Skip to main content
Labels

A hotfix is available to fix restart problems after you install update rollup 2919355 in Windows 8.1 or Windows Server 2012 R2


Collapse imageSymptoms

After you install Update Rollup 2919355 (April 2014) for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2, or after you install any of these systems from media that includes this update rollup, you cannot restart the computer because the computer experiences a restart loop.

Update Rollup 2919355 may have been installed automatically through Windows Update (WU) or through Windows Server Update Services (WSUS) in your environment.

Computers that start from certain Serial Attached SCSI (SAS) storage controllers are affected by this problem. This includes, but is not limited to, the following controller drivers:
  • Dell H200 PERC controller
  • IBM x240 with on-board LSI SAS2004 ROC controller
  • LSI 2308 on-board controllers
  • LSI 9211-4i controllers
  • LSI 9211-8i controllers
  • LSI SAS 9211
  • Supermicro X10SL7-F motherboard
If the "Automatically restart" option to set the computer behavior after a failure is disabled, you receive the following Stop error message during startup:
Stop 0x7B INACCESSIBLE_BOOT_DEVICE
Back to the top | Give Feedback

Collapse imageCause

This problem occurs if the storage controller receives a memory allocation that starts on a 4 gigabyte (GB) boundary. In this situation, the storage driver does not load. Therefore, the system does not detect the boot disk and returns the Stop error message that is mentioned in the "Symptoms" section.

Note This problem may not always occur in this situation. The problem is affected by the computer’s startup process, the driver load sequence, and the memory allocation of the storage controller driver at startup.
Back to the top | Give Feedback

Collapse imageResolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next P1 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The P1 version of this P2 has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Installation information

The hotfix download provides Update 2966870 to resolve the problems that are mentioned in the "Symptoms" section. Before you run the installation media for Windows 8.1 Update or Windows Server 2012 R2 Update, you must inject Update 2966870 into the installation media. To do this, use one of the following methods.

Note The system descriptions in these steps assume that the installation media and computers that are used in this process are all 64-bit AMD64 architecture computers. For x86 or ARM architectures, follow these same steps but replace all references to "amd64" by using "x86 or "WOA," as appropriate.

Method 1: Preinstall this update into custom USB installation media

Use this method if the following conditions are true:
  • You plan to install a Windows operating system from a USB flash drive.
  • You have a Windows 8.1 or Windows Server 2012 R2 operating system available on a different computer.
  • You can use the other computer to manipulate files on the USB flash drive.
  • You have Windows 8.1 Update or Windows Server 2012 R2 Update source files available.
To inject this update into the USB installation media on a USB flash drive, follow these steps:
  1. On a cleanly FAT32-formatted USB flash drive, copy the whole contents of the Windows installation media to the root directory.
  2. Create a folder that is named C:\Bin.
  3. Create a folder that is named C:\Bin\2966870.
  4. Download the hotfix to the C:\Bin\2966870 folder.
  5. If the hotfix is an executable file (.exe), you have to run the file to extract the required files. Make sure that the files extract to C:\Bin\2966870.
  6. Among the extracted files, locate Windows8.1-KB2966870-x64.msu, and then rename it Windows8.1-KB2966870-x64.msu.cab.
  7. Double-click Windows8.1-KB2966870-x64.msu.cab, and then extract the Windows8.1-K2966870-x64.cab file to the C:\Bin\2966870 folder.

    Note This is the file that you will inject.
  8. Create a folder that is named C:\Bin\Mount.
  9. Create a folder that is named C:\Bin\MountRE.
  10. Create a folder that is named C:\Bin\Scratch.
  11. In the Windows 8.1 Update or Windows Server 2012 R2 Update installation media, locate the following files, and then copy the files to C:\Bin:

    \Sources\Boot.wim
    \Sources\Install.wim
  12. On the Windows 8.1-based or Windows Server 2012 R2-based computer, open an administrative command prompt. To do this, right-click Start, and then click Command prompt (Admin)
  13. At the command prompt, type CD C:\Bin, and then press Enter.
  14. Mount the first index of Boot.wim. To do this, run the following Deployment Image Servicing and Management (DISM) command at the command prompt:

    dism /mount-wim /wimfile=boot.wim /index:1 /mountdir=Mount
    Note This command can take some time to finish.
  15. Inject the hotfix into the mounted WIM image. To do this, run the following DISM command:

    dism /image:.\Mount /add-package /packagepath:C:\Bin\2966870\Windows8.1-KB2966870-x64.cab /scratchdir=scratch

    Note This command can take some time to finish.
  16. Verify that the package is added. To do this, run the following DISM command, and then examine the output for the hotfix number that you just injected:

    dism /image:.\mount /get-packages
  17. Unmount and commit the changes to the currently mounted WIM image. To do this, run the following DISM command:

    dism /unmount-image /mountdir:.\Mount /commit
    Note This command can take some time to finish.
  18. Repeat steps 14 through 17 for index 2 of the Boot.wim image, except change the index number in step 14 from 1 to 2.
  19. At the command prompt, run the following DISM command:

    dism /get-imageinfo /imagefile:C:\Bin\install.wim
    Notes
    • A list of images that are included in the WIM and their associated index numbers is displayed.
    • You have to mount and inject the hotfix into the indexes that you plan to use. If you use more than one index, you have to inject the hotfix into multiple indexes.
    The following output shows an example of what the list might display.

    Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Details for image : C:\Bin\install.wim

Index : 1
Name : Windows Server 2012 R2 SERVERSTANDARDCORE
Description : Windows Server 2012 R2 SERVERSTANDARDCORE
Size : 6,897,618,255 bytes

Index : 2
Name : Windows Server 2012 R2 SERVERSTANDARD
Description : Windows Server 2012 R2 SERVERSTANDARD
Size : 12,069,723,893 bytes

Index : 3
Name : Windows Server 2012 R2 SERVERDATACENTERCORE
Description : Windows Server 2012 R2 SERVERDATACENTERCORE
Size : 6,876,269,628 bytes

Index : 4
Name : Windows Server 2012 R2 SERVERDATACENTER
Description : Windows Server 2012 R2 SERVERDATACENTER
Size : 12,066,707,039 bytes

The operation completed successfully.
  20. Mount the index that you want to inject the update into. To do this, run the following DISM command:

    dism /mount-image /imagefile:C:\Bin\install.wim /index:# /mountdir:.\Mount
    Notes
    • In this command, replace the number sign (#) by using the index number from the list in step 19 that corresponds to the index that you are mounting.
    • This command can take some time to finish.
  21. Set the Winre.wim attributes to be mountable. To do this, run the following command:

    Attrib –s –h mount\windows\system32\recovery\winre.wim
  22. Mount the Windows RE image inside the Install.wim file. To do this, run the following DISM command:

    dism /mount-image /imagefile:.\mount\Windows\System32\Recovery\winre.wim /index:1 /mountdir:.\MountRE
  23. Inject the update into the mounted WIM image. To do this, run the following DISM command:

    dism /image:.\Mount /add-package /packagepath:C:\Bin\2966870\Windows8.1-KB2966870-x64.cab /scratchdir:.\scratch
    Note This command can take some time to finish.
  24. To verify that the package is added, run the following DISM command, and then examine the output for the hotfix number that you just injected:

    dism /image:.\mount /get-packages
  25. Inject the update into the mounted Winre.wim image. To do this, run the following DISM command:

    dism /image:.\MountRE /add-package /packagepath:C:\Bin\2966870\Windows8.1-KB2966870-x64.cab /scratchdir:.\scratch
    Note This command can take some time to finish.
  26. To verify that the package is added, run the following DISM command, and then examine the output for the hotfix number that you just injected:

    dism /image:.\MountRE /get-packages
  27. Unmount and commit the changes to the currently mounted Winre.wim image. To do this, run the following DISM command:

    dism /unmount-image /mountdir:.\MountRE /commit
    Note This command can take some time to finish.
  28. Unmount and commit the changes to the currently mounted WIM image. To do this, run the following DISM command:

    dism /unmount-image /mountdir:.\Mount /commit
    Note This command can take some time to finish.
  29. Repeat steps 20 through 28 for each index identified in step 19.
  30. Copy the updated Boot.wim and Install.wim files from the C:\Bin folder to the \Sources folder on the USB flash drive that is currently being used for source media. Replace the existing versions of these files in the \Sources folder on the USB flash drive.

Method 2: Preinstall this update into custom ISO installation media

Use this method if the following conditions are true:
  • You plan to install a Windows operating system from a custom ISO image or DVD.
  • You have a Windows 8.1 or Windows Server 2012 R2 operating system available on a different computer.
  • You can use that computer to manipulate files.
  • You have Windows 8.1 Update or Windows Server 2012 R2 Update source files available
To inject this update into the installation media into an ISO image, follow these steps:
  1. Download and install the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update from the Microsoft Download Center.

    Note This kit provides the tools to create an ISO image that you can use to add installation files to a DVD.
  2. Follow steps 1-30 from Method 1, except do the following:
    • In step 1, instead of copying the files to a USB flash drive in step 1, copy the files to the C:\Bin\Media folder.
    • In step 30, copy the updated Boot.wim and Install.wim files to C:\Bin\Media\Sources, and replace the existing versions of these files in this folder.


    Note By default, this tool looks for the \Media folder.
  3. In the All Apps view, right-click Deployment and Imaging Tools Environment, and then click Run as Administrator.
  4. In the Command Prompt window that opens, navigate to the following location:

    C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg
  5. At the command prompt, run the following command to build a bootable ISO image.

    Note This command builds a bootable Windows ISO image that is named Custom-Windows in the C:\Bin folder.

    oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,betfsboot.com#pEF,e,befisys.bin C:\Bin\media C:\Bin\Custom-Windows.iso
Back to the top | Give Feedback

Collapse imageWorkaround

To recover from the "no boot" state when this problem occurs, try one or both of the following workaround methods.

Method 1

Try to restart the computer several times. You may occasionally be able to boot to the desktop by trying the process multiple times.

Method 2

  1. Start the computer from media for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2, select the Repair your computer option, click Troubleshoot, and then click Command Prompt.

    Note For this workaround, the media that you use should not include Update Rollup 2919355.
  2. At a command prompt, run the following command:

    Bcdedit /store <path of Boot Configuration Data (BCD)> /set {default} truncatememory 4294967296
    Note The path of the BCD file is <drive letter>:\BOOT\BCD, in which the driver letter is the system partition. This command adds an entry to the BCD file under Windows Boot Loader that is named truncatememory. The new entry will have a value format of 0x100000000. For example, run the following command:

    Bcdedit /store C:\BOOT\BCD /set {default} truncatememory 4294967296
  3. Restart the computer. The computer should now boot to the desktop.

    Note If you were installing Update Rollup 2919355 when this problem occurred, the computer will continue to complete the installation of the update. After you successfully start Windows, uninstall Update Rollup 2919355.
  4. To remove the truncatememory boot option, run the following command at a command prompt:

    Bcdedit /deletevalue truncatememory
  5. Start the computer normally.


Back to the top | Give Feedback

Collapse imageStatus

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Collapse imageMore information

For the syntax to create an ISO image that can start on AMD64 (UEFI)-based computers and also on legacy MBR computers, see the following Microsoft Knowledge Base article:

947024 How to create an ISO image for UEFI platforms for a Windows PE CD-ROM for Windows Server 2008
For more information about Oscdimg Command-Line Options, see the following Microsoft TechNet topic:

Oscdimg Command-Line Options
Third-party information disclaimer

assets folding start collapsed
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.
assets folding end collapsed
Back to the top | Give Feedback

Collapse imageProperties

Article ID: 2966870 - Last Review: June 5, 2014 - Revision: 4.0
Applies to
  • Windows 8.1
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Standard
  • Windows Server 2012 R2 Foundation
  • Windows Server 2012 R2 Essentials
  • Windows Server 2012 R2 for Embedded Systems
  • Microsoft Hyper-V Server 2012 R2
  • Windows Storage Server 2012 R2 Workgroup
  • Windows Storage Server 2012 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix KB2966870
Labels:

Comments

Post a Comment

Popular Posts