none
SCCM 2012 R2 Boot Image won't load in Windows XP RRS feed

  • Question

  • I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE

    Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)

    Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)

    More detailed smsts.log below:


    <![LOG[Captured settings for adapter 1]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="netsettings.cpp:99">
    <![LOG[OSDNetSettings finished: 0x00000000]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="main.cpp:192">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:33:52.307+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:1123">
    <![LOG[Installing boot image to hard drive]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:621">
    <![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:644">
    <![LOG[BootLoader::backup: C:\, C:\_SMSTaskSequence\backup]LOG]!><time="09:33:53.213+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:85">
    <![LOG[BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\]LOG]!><time="09:33:54.479+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:382">
    <![LOG[Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD]LOG]!><time="09:33:57.057+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootconfigimplbcd.cpp:703">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:33:57.166+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:827">
    <![LOG[CreateProcess failed. Code(0x800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1018">
    <![LOG[Command line execution failed (800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1245">
    <![LOG[Failed to install boot image. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="bootimage.cpp:681">
    <![LOG[Failed to install boot image UCI00073. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:840">
    <![LOG[Failed to reboot the system. Error 0x(800700c1)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:953">
    <![LOG[Failed to initialize a system reboot. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:577">
    <![LOG[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)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:273">
    <![LOG[An error (0x800700c1) is encountered in execution of the task sequence]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:348">
    <![LOG[Set authenticator in transport]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="0" thread="4856" file="libsmsmessaging.cpp:7734">
    <![LOG[Task Sequence Engine failed! Code: 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:919">
    <![LOG[****************************************************************************]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:953">
    <![LOG[Task sequence execution failed with error code 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:954">
    <![LOG[Cleaning Up.]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:686">

    Thursday, October 31, 2013 5:06 PM

Answers

  • As mentioned, no. There is a known issue that is preventing it today. You should contact CSS.

    One possible solution is to replace the bootsect.exe on the boot image with a version from an earlier version of WinPE. This is not supported however has been reported to work.


    Jason | http://blog.configmgrftw.com

    Sunday, November 3, 2013 11:00 PM

All replies

  • This is a known issue although there is no known work-around or fix. You should contact CSS.

    Jason | http://blog.configmgrftw.com

    Thursday, October 31, 2013 8:47 PM
  • Hi guys,

    I installed ConfigMgr 2012 SP1 R2 and MDT 2013 in a test environment. As a result, I can't use anything related to MDT (create MDT boot image, create MDT TS etc) because of the same error - 800700C1.

    Tried everything I know; checked the configuration etc... still no luck.

    What is strange is that the PEManager.log looks ok if i'm trying to create a boot image. Every component addition exits with error code 0 however, the wizard ends with failed result, sometimes even before the component is fully added.

    Any hints, ideas where I can look for? Any more logs I can check?

    Thanks!!

    Saturday, November 2, 2013 8:43 PM
  • This is a known issue although there is no known work-around or fix. You should contact CSS.

    Jason | http://blog.configmgrftw.com

    So you cannot deploy XP with R2 from the OS itself??

    Sunday, November 3, 2013 7:05 AM
  • I can't get to that point.. cannot create a TS, nor a boot image using MDT
    Sunday, November 3, 2013 8:05 AM
  • As mentioned, no. There is a known issue that is preventing it today. You should contact CSS.

    One possible solution is to replace the bootsect.exe on the boot image with a version from an earlier version of WinPE. This is not supported however has been reported to work.


    Jason | http://blog.configmgrftw.com

    Sunday, November 3, 2013 11:00 PM
  • I can't get to that point.. cannot create a TS, nor a boot image using MDT

    Then you should start a new thread with your specific details.

    Jason | http://blog.configmgrftw.com

    Sunday, November 3, 2013 11:00 PM
  • Hey,

    Do you have guidelines how to replace bootsect.exe?

    PS. I tried to add boot images form WAIK 3.1 (windows 7) to my task sequence. It fails with same error.


    Regards, Mindaugas Laucius

    Monday, November 18, 2013 2:02 PM

  • See the "Workaround" section of this post for an example of downgrading bootsect.exe:

    http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd

    It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.




    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".


    • Edited by NPherson Monday, November 18, 2013 9:09 PM
    Monday, November 18, 2013 9:08 PM
  • See the "Workaround" section of this post for an example of downgrading bootsect.exe:

    http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd

    It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.




    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".


    This workaround worked in my environment.  Fixed my in-place upgrades from XP to Windows 7, and as a bonus, fixed imaging XP as well. yeah, I have to keep XP for awhile. :-(

    Tuesday, November 19, 2013 12:08 PM
  • Hi,

    Hotfix is now available:

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

    http://support.microsoft.com/kb/2910552/en-us


    Abduljalil Abolzahab

    Tuesday, February 18, 2014 11:55 AM
  • Thanks God!!!! I've been with this issue for a long time. I will test the HotFix and will let you know about the results.

    Best Regards

    Saturday, March 15, 2014 12:10 AM
  • Hi,

    Hotfix is now available:

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

    http://support.microsoft.com/kb/2910552/en-us


    Abduljalil Abolzahab

     I have installed the CU1 for R2, which is supossed to contain this fix. Updated the boot images in the distribution points, but the issue still remains. Do you know any addiotional steps for this fix to work?

    Un saludo,

    Pablo

     
    Sunday, March 30, 2014 10:20 AM
  • I tried the CU1 update and it still would not work. Should I have installed the hotfix separately?

    Im almost tempted to just do everyone PXE at this point despite the cost of the additional resource to walk the floors.

    Tuesday, April 8, 2014 11:14 PM
  • The hotfix (mentioned above or CU1 for R2) comes with a client patch. This has to be installed on the clients!

    Torsten Meringer | http://www.mssccmfaq.de


    • Edited by TorstenMMVP Wednesday, May 21, 2014 6:35 AM
    Wednesday, April 9, 2014 6:43 AM
  • Has this issue been resolved. I'm still seeing the issue despite installing R2 CU1 update.
    Wednesday, May 21, 2014 12:31 AM
  • Hi,

    Make sure that you update clients also, not only site server. And update boot images.


    Abduljalil Abolzahab

    Wednesday, May 21, 2014 7:04 AM
  • Are you using WinPE 3.1 based boot images? This is a requirement for the hotfix or CU1 to address the issue.

    Jason | http://blog.configmgrftw.com

    Wednesday, May 21, 2014 12:38 PM
  • I have found that the boot images have to be generated from ADK 8.0 and not 8.1 as that is the problem. I have detailed instructions for importing a legacy boot image in SCCM to support windows XP migrations.

    http://davejaskie.com/2014/04/03/installing-a-legacy-boot-image-in-sccm-to-support-xp-migrations/

    • Proposed as answer by Tregelen Monday, September 1, 2014 4:31 AM
    Sunday, May 25, 2014 1:50 AM
  • WinPE 4.0 based boot images are not technically supported by ConfigMgr 2012 R2. The recommended solution is to use WinPE 3.1 boot images as mentioned. These need to be updated after CU1 is applied and CU1 needs to be deployed to the target XP systems.

    Jason | http://blog.configmgrftw.com

    Tuesday, May 27, 2014 12:34 AM
  • Can you still use Windows XP in-place upgrade to Windows 7 ( Wipe and Load) with the new ADK 8.1 version with  installed with SCCM 2012 SP R2 CU1.?

    Wednesday, June 11, 2014 12:19 AM
  • Yes, but you need to use WinPE 3.1 as your boot image if you are using the refresh scenario. For the new computer scenario, this is not necessary.

    Jason | http://blog.configmgrftw.com

    Wednesday, June 11, 2014 12:22 AM