You install the Windows Deployment Services (WDS) server role on a computer that is running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003.
In the local area network (LAN), you use a Windows Vista boot image or a Windows Server 2008 boot image to deploy one or more operating system images in Windows Deployment Services. Note This problem does not occur if you use a Windows Vista Service Pack 2 (SP2) boot image or a Windows Server 2008 Service Pack 2 (SP2) boot image.
You try to deploy an image that is based on an ACPI Uniprocessor (ACPI APIC UP) Hardware Abstraction Layer (HAL) to a client that uses an ACPI APIC UP HAL or an ACPI Multiprocessor (ACPI APIC MP) HAL.
In this scenario, the image is not displayed in the menu for the available operating system images during the deployment process. Therefore, you cannot deploy the image to the client.
Note This problem also occurs in Windows 7 boot images and in Windows Server 2008 R2 boot images. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
980711 An ACPI APIC UP HAL operating system image cannot be deployed if a Windows 7 boot image or a Windows Server 2008 R2 boot image is used in the deployment process
The issue occurs because the Wdsclient.dll module incorrectly excludes images that are based on an ACPI APIC UP HAL when the Wdsclient.dll module displays the menu of the available operating system images.
A supported hotfix is available from Microsoft. 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, visit the following Microsoft Web site:
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.
To apply this hotfix, you must be running one of the following operating systems:
Windows Server 2003 Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Windows Server 2008 R2
Windows Vista Service Pack 1 (SP1)
Note These are the operating systems on which you can install the Windows Automated Installation Kit (Windows AIK) for Windows 7. You use Windows AIK for Windows 7 to apply the hotfix to the Windows Vista boot image or to the Windows Server 2008 boot image.
To use the hotfix in this package, you do not have to make any changes to the registry.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global 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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" 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 Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
For the x86-based Windows Vista boot image and for the x86-based Windows Server 2008 boot image
For the x64-based Windows Vista boot image and for the x64-based Windows Server 2008 boot image
For the IA-64-based Windows Server 2008 boot image
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
You must apply this hotfix to the second image of the Windows Vista or Windows Server 2008 boot image file. To do this, follow these steps.
Note The second image is the Windows Preinstallation Environment (Windows PE) image.
Click Start, click All Programs, click Microsoft Windows AIK, right-click the Deployment Tools Command Prompt, and then select Run as administrator.
If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
Extract the Windows6.0-KB935772-Platform.cab file from the hotfix package to a temporary folder. To do this, follow these steps:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, type the following command, and then press ENTER:
Expand.exe CabFilePath -R -F:* TempFolderPath
The CabFilePath placeholder represents the path of the CAB file.
The TempFolderPath placeholder represents the path of the temporary folder.
Disable the problematic boot image to make it unavailable for download in the update process. To do this, open the Windows Deployment Services Microsoft Management Console (MMC) snap-in, right-click the boot image that you want to update, and then select Disable.
Export the problematic boot image from the Windows Deployment Services server to BootWimPath. To do this, right-click the boot image, and then select Export Image. Export the boot image to BootWimPath.
The BootWimPath placeholder represents the local directory where the Boot.wim file is exported.
If you install the Windows AIK on a separate computer, you must copy the Boot.wim file to a directory on that computer. Then, perform step 6 through step 8 on that computer.
Mount the boot image for read access and for write access. To do this, type the following command at the command prompt, and then press ENTER:
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, select Add Boot Image, and then specify the path to the updated Boot.wim file
In the Windows Deployment Services MMC snap-in, right-click the boot image that you added to make sure that it is enabled.
Note You have to disable or delete the problematic boot image.
For more information about Windows Deployment Services, visit the following Microsoft Tech websites: