Microsoft KB Archive Search

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.

  1. Home
  2. You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in System Center 2012 R2 Configuration Manager

You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in System Center 2012 R2 Configuration Manager

View products that this article applies to.

Symptoms

Assume that you install or upgrade to Microsoft System Center 2012 R2 Configuration Manager on a System Center Configuration Manager site server. When you try to deploy a task sequence that has an associated Windows PE 3.1 boot image to a Windows XP-based computer in an update scenario, the deployment fails, and the following error message is logged in the Smsts.log file:

Installing boot image to hard drive TSManager datetime 3048 (0x0BE8)
Backing up existing boot system before trying to set up new boot system TSManager datetime 3048 (0x0BE8)
BootLoader::backup: C:\, C:\_SMSTaskSequence\backup TSManager datetime 3048 (0x0BE8)
BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\ TSManager datetime 3048 (0x0BE8)
Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD TSManager datetime 3048 (0x0BE8)
Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager datetime 3048 (0x0BE8)
CreateProcess failed. Code(0x800700C1) TSManager datetime 3048 (0x0BE8)
Command line execution failed (800700C1) TSManager datetime 3048 (0x0BE8)
Failed to install boot image.
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Failed to install boot image CCR00004.
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Failed to reboot the system. Error 0x(800700c1) TSManager datetime 3048 (0x0BE8)
Failed to initialize a system reboot.
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)
Fatal error is returned in check for reboot request of the action (Restart in Windows PE).
is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

↑ Back to the top

Cause

This problem occurs because of a compatibility issue between Windows XP and the Windows Assessment and Deployment Kit (ADK) 8.1.

↑ Back to the top

Resolution

To resolve this problem, apply the hotfix that is described in this article. This hotfix applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this hotfix to a site server will let you create client update packages.

You must use a Windows PE 3.1 boot image, and the architecture of the boot image (x86 or x64) must match the architecture of the target Windows XP operating system.

After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, follow these steps:
  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select the Update Distribution Points action.

    Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
  5. Repeat steps 3 and 4 for all boot images that were previously distributed.

Hotfix information

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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must have System Center 2012 R2 Configuration Manager installed.

Restart information

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

Note We recommend that you close Configuration Manager Administration Console before you install this hotfix package.

Hotfix replacement information

This hotfix replaces the following hotfix:

2905002 An update is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager

File information
The English version of this hotfix 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.

For all x86-based systems
File nameFile versionFile sizeDateTimePlatform
Configmgr2012ac-r2-kb2910552-i386.mspNot Applicable846,84801-Oct-201301:20Not Applicable
Configmgr2012adminui-r2-kb2910552-i386.mspNot Applicable2,169,34401-Oct-201301:20Not Applicable
Createtsmediaadm.dll5.0.7958.10011,619,63201-Oct-201301:05x86
Tscore.dll5.0.7958.11041,824,94401-Oct-201301:20x86
For all x64-based systems
File nameFile versionFile sizeDateTimePlatform
Configmgr2012ac-r2-kb2910552-x64.mspNot Applicable1,016,83201-Oct-201301:20Not Applicable
Createtsmediaadm.dll5.0.7958.10012,034,86401-Oct-201301:05x64
Mcs.msiNot Applicable9,641,98401-Oct-201301:20Not Applicable
Tscore.dll5.0.7958.11042,455,72801-Oct-201301:20x64

↑ Back to the top

Status

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

↑ Back to the top

References

See the following Microsoft TechNet website:
How to Customize Windows PE Boot Images to Use in Configuration Manager

Learn about how to update boot images.

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbautohotfix, kbfix, kbhotfixserver, kbsurveynew, kbexpertiseinter, kb, SCCM

↑ Back to the top

Article Info
Article ID : 2910552
Revision : 2
Created on : 4/26/2017
Published on : 4/26/2017
Exists online : False
Views : 415