Symptoms

Consider the following scenario:

  • You use Windows Server 2012 as a Windows Deployment Services (WDS) server.

  • You have Unified Extensible Firmware Interface (UEFI)-based computers that have no keyboard, mouse, video, or USB ports but only a graphics-capable output device such as a VGA monitor.

    Note This kind of computer is remotely managed through the UEFI console and cannot display the UEFI text-based console.


In this scenario, the UEFI-based computers cannot start because the WDS Pre-Boot Execution Environment (PXE) program requires you to press F12 to continue a network startup in text-based mode.

Cause

This problem occurs because the startup library-based applications, such as Wdfmgr.efi, use the graphics console incorrectly.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

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 8 and Windows Server 2012 file information and notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • 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.2.920 0.16 xxx

    Windows 8 and Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

  • 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 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.

For all supported x86-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Wdsmgfw.efi

6.2.9200.16759

1,023,320

08-Nov-2013

00:02

Not Applicable

Wdsmgfw.efi

6.2.9200.20872

1,023,320

08-Nov-2013

05:23

Not Applicable

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Wdsmgfw.efi

6.2.9200.16759

1,208,152

08-Nov-2013

08:06

Not Applicable

Wdsmgfw.efi

6.2.9200.20872

1,208,152

08-Nov-2013

07:39

Not Applicable

For all supported ARM-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Wdsmgfw.efi

6.2.9200.16759

639,832

08-Nov-2013

03:10

Not Applicable


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8

File name

Package_1_for_kb2908456_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not Applicable

File size

1,783

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Package_1_for_kb2908456~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not Applicable

File size

2,502

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Package_for_kb2908456_rtm_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not Applicable

File size

1,430

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Package_for_kb2908456_rtm~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not Applicable

File size

1,449

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

1,563

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

X86_37e3c4bafc230da2cd6adcfd2b2b8190_31bf3856ad364e35_6.2.9200.20872_none_431120041b14fe39.manifest

File version

Not Applicable

File size

712

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

X86_bbfc30d39515b5ab2a26861a6fcc41aa_31bf3856ad364e35_6.2.9200.16759_none_3f894a6c6e96937b.manifest

File version

Not Applicable

File size

712

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

X86_microsoft-windows-b..nvironment-pxe-base_31bf3856ad364e35_6.2.9200.16759_none_1b6817bc4f8435bc.manifest

File version

Not Applicable

File size

2,962

Date (UTC)

08-Nov-2013

Time (UTC)

00:06

Platform

Not Applicable

File name

X86_microsoft-windows-b..nvironment-pxe-base_31bf3856ad364e35_6.2.9200.20872_none_1bd512a968b85c07.manifest

File version

Not Applicable

File size

2,962

Date (UTC)

08-Nov-2013

Time (UTC)

05:42

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

Amd64_ab0e3cfe199e3c7bcf5305a968272d27_31bf3856ad364e35_6.2.9200.16759_none_10718e75293a32c2.manifest

File version

Not Applicable

File size

716

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Amd64_ffb2ec60d00a200bb201cb4769a9f0e5_31bf3856ad364e35_6.2.9200.20872_none_5c920bd1c4e904f4.manifest

File version

Not Applicable

File size

716

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Amd64_microsoft-windows-b..nvironment-pxe-base_31bf3856ad364e35_6.2.9200.16759_none_7786b34007e1a6f2.manifest

File version

Not Applicable

File size

2,966

Date (UTC)

08-Nov-2013

Time (UTC)

08:11

Platform

Not Applicable

File name

Amd64_microsoft-windows-b..nvironment-pxe-base_31bf3856ad364e35_6.2.9200.20872_none_77f3ae2d2115cd3d.manifest

File version

Not Applicable

File size

2,966

Date (UTC)

08-Nov-2013

Time (UTC)

07:43

Platform

Not Applicable

File name

Package_1_for_kb2908456_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not Applicable

File size

1,793

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Package_1_for_kb2908456~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not Applicable

File size

2,516

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Package_for_kb2908456_rtm_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not Applicable

File size

1,438

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Package_for_kb2908456_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not Applicable

File size

1,457

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

1,571

Date (UTC)

08-Nov-2013

Time (UTC)

19:15

Platform

Not Applicable

Additional files for all supported ARM-based versions of Windows 8

File name

Arm_4ea29e6a3b5006efe5dfcc911e432263_31bf3856ad364e35_6.2.9200.16759_none_f2468b0465aed958.manifest

File version

Not Applicable

File size

712

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Arm_microsoft-windows-b..nvironment-pxe-base_31bf3856ad364e35_6.2.9200.16759_none_1b6a8a144f815482.manifest

File version

Not Applicable

File size

2,962

Date (UTC)

08-Nov-2013

Time (UTC)

03:13

Platform

Not Applicable

File name

Package_1_for_kb2908456~31bf3856ad364e35~arm~~6.2.1.0.mum

File version

Not Applicable

File size

1,821

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable

File name

Package_for_kb2908456_rtm~31bf3856ad364e35~arm~~6.2.1.0.mum

File version

Not Applicable

File size

1,449

Date (UTC)

08-Nov-2013

Time (UTC)

19:14

Platform

Not Applicable


References

See the terminology Microsoft uses to describe software updates for more information.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×