UEFI-based computers cannot start because the WDS PXE program requires you to press F12

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website: 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.

Installation information

To apply this hotfix, follow these steps:

1. Export the Windows 8 or Windows Server 2012 boot image from the WDS server. To do this, use the WDS MMC snap-in or the wdsutil.exe utility.
   1. Start the WDS MMC snap-in or the wdsutil.exe utility.
   2. Locate the boot image that you plan to use.
   3. Right-click that image and export to a known location. For example, create a folder on the root of c: such as c:\bin and then export the image to that folder.
2. Mount the exported boot image by using the index number. For example, mount index 2 of the boot image. To do this, follow these steps:
   1. Start an administrator command prompt. To do this, right-click the lower-left corner of the desktop and then click Command Prompt (Admin).
   2. Change to the folder that you created in step 1c.
   3. For information about the Microsoft Windows Imaging Format (WIM) image format, type the following command and then press Enter. Identify if you have 1 or 2 indexes in this WIM.
      
      
      dism.exe /get-wiminfo /wimfile:c:\bin\exportedwim.wim
      
      
   4. Create a new "mount" folder where WIM will be mounted for file injection. To do this, type the following command and then press Enter:
      
      
      type "md c:\bin\mount"
      
      
   5. Type the following command to mount the WIM.
      
      Note If there are 2 indexes such as when you use the default boot.wim file to create the boot.wim file for WDS, use the second index.
      
      
      dism /mount-wim /wimfile:c:\bin\exportedwim.wim /index:2 /mountdir:c:\bin\mount
      
      
3. Install the .msu package to the Windows 8 or Windows Server 2012 boot.wim file to perform the update. To do this, follow these steps:
   1. Type the following command and then press Enter:
      
      
      dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:Path_to_ package
      
      
   2. Unmount and then commit the changes after the package has successfully installed. To do this, type the following command and then press Enter:
      
      
      dism.exe /unmount-wim /mountdir:c:\bin\mount /commit
      
      
4. Replace the boot image on the WDS server with the updated boot image.
   1. Add the updated Boot.wim file back to the Windows Deployment Services server. To do this, open the Windows Deployment Services MMC snap-in, right-click Boot Images, click Add Boot Image, and then specify the path of the updated Boot.wim file. Alternatively use the wdsutil.exe utility.
   2. In the Windows Deployment Services MMC snap-in, right-click the boot image that you added to make sure that it is enabled.

Prerequisites

To apply this hotfix, you must have Windows 8 or Windows Server 2012 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.