none
Deploying Windows 7 Boot Manager Failed to Start Status: 0xc0000001

    Question

  • I am trying to deploy a Windows 7 Pro 32 bit image using SCCM 2007 SP2.  I created the image by building the computer, installing all required programs and configuration settings then captured the image using an SCCM Capture Media CD to create the WIM image.  The image was then added to our Operating System Images and we created a task sequence to deploy them image.  We have done this for all our XP images and this works perfectly.

    When I deploy the Windows 7 Pro image the task sequence works (ie Partition drive, format, copy image, apply image etc) then once completed it reboots the computer.  Normally with an XP computer the sysprep starts and sets the product code and adds to the domain.  Instead the computer boots with the message "Windows Boot Manager" there is some text regarding potentially cause of hardware/software changes then lower on the message screen "Windows Failed to Start" "Status: 0xc0000001".

    Before this I was running SCCM 2007 SP1 but found this solution: http://blogs.technet.com/b/configurationmgr/archive/2010/02/04/solution-status-0xc0000001-when-deploying-windows-7-via-osd-in-configmgr-2007.aspx which indicated that I needed the WINPe to be 3.x (version 6.1.7600.16385) mine Winpe boot image was 6.0.6001.1800.  So I upgraded to SCCM SP2 and reloaded my boot image so it is now 6.1.7600.1685, however I am still getting the same result of Windows Boot Manager, Windows failed to start 0xc0000001.

    I am trying to deploy this on a Dell Optiplex 780, which is our current standard desktop and push SCCM OSD XP images to with no issues.  The BIOS version of the Optiplex 780 is A06.  I have also loaded the Windows 7 network drivers to the x86 and x64 boot images.

     

    Wednesday, May 04, 2011 3:51 PM

All replies

  • it sounds like the setup windows and configmgr step is failing, can you start another deployment and before it reboots can you please examine the SMSTS.LOG file and see what it says ?


    My step by step SCCM Guides
    I'm on Twitter > ncbrady
    Wednesday, May 04, 2011 5:10 PM
    Moderator
  • Here is the last number of lines in the SMSTS.log, I don't see anything obvious that would cause this error.

    ![LOG[OSDDiskPart.exe completed successfully]LOG]!time="14:26:10.404+240" date="05-04-2011" component="OSDDiskPart" context="" type="1" thread="1608" file="main.cpp:1495"
    ![LOG[Process completed with exit code 0]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="commandline.cpp:1102"
    ![LOG[!--------------------------------------------------------------------------------------------!]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="instruction.cxx:3010"
    ![LOG[Successfully complete the action (Partition Disk) with the exit win32 code 0]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="instruction.cxx:3036"
    ![LOG[Sending status message . . .]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:292"
    ![LOG[Send a task execution status message SMS_TSExecution_ActionCompleteInfo]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:314"
    ![LOG[MP server BKR-SMS.BMCC.LOCAL and port 80. SSL=false. CRL=false.]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:458"
    ![LOG[Site code: BK1]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:489"
    ![LOG[Client machine name: IS73KXP]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:494"
    ![LOG[Client Identity: GUID:AAE66B29-25EC-4056-A3DB-D8815B48905B]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:496"
    ![LOG[Advertisement ID: BK12006D]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:505"
    ![LOG[Package ID: BK100089]LOG]!time="14:26:10.404+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="utility.cxx:507"
    ![LOG[Sending StatusMessage]LOG]!time="14:26:10.420+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="libsmsmessaging.cpp:3806"
    ![LOG[Formatted header:]LOG]!time="14:26:10.420+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="libsmsmessaging.cpp:1500"
    ![LOG[Msg SchemaVersion="1.1" ReplyCompression="zlib"ID/SourceID239bccef-d38f-493f-a1b6-38b68e2e5485/SourceIDSourceHost/TargetAddressmp:[http]MP_StatusManager/TargetAddressReplyTodirect:OSD/ReplyToPriority3/PriorityTimeout3600/TimeoutSentTime2011-05-04T18:26:10Z/SentTimeProtocolhttp/ProtocolBody Type="ByteRange" Offset="0" Length="4198"/Hooks/Payload Type="inline"/TargetHost/TargetEndpointStatusReceiver/TargetEndpointReplyModeSync/ReplyModeCorrelationID//Msg
    ]LOG]!time="14:26:10.420+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="libsmsmessaging.cpp:1501"
    ![LOG[CLibSMSMessageWinHttpTransport::Send: URL: BKR-SMS.BMCC.LOCAL:80  CCM_POST /ccm_system/request]LOG]!time="14:26:10.420+240" date="05-04-2011" component="TSManager" context="" type="1" thread="1552" file="libsmsmessaging.cpp:7446"
    ![LOG[The request has succeeded. 200 OK]LOG]!time="14:26:10.436+240" date="05-04-2011" component="TSManager" context="" type="0" thread="1552" file="libsmsmessaging.cpp:7734"
    ![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!time="14:26:10.436+240" date="05-04-2011" component="TSManager" context="" type="0" thread="1552" file="executionenv.cxx:668"
    ![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!time="14:26:10.436+240" date="05-04-2011" component="TSManager" context="" type="0" thread="1552" file="executionenv.cxx:668"
    ![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!time="14:26:10.436+240" date="05-04-2011" component="TSManager" context="" type="0" thread="1552" file="executionenv.cxx:782"

     

    Wednesday, May 04, 2011 7:14 PM
  • ok to confirm, in your apply operating system image step you are applying an image from a captured image ? and it's image index 1-1 are there any more options in image index ? how is your disc partitioned (check with diskpart) and lastly is the bios hard disc mode set to ATA/SATA/ACHi ?

    My step by step SCCM Guides
    I'm on Twitter > ncbrady
    Wednesday, May 04, 2011 7:34 PM
    Moderator
  • I am applying an image from a captured image.  In the task sequeance for "Apply Operating System " I have the option "Apply operating system form a capture image" selected with the Image package pointing to the Wim file and the Image index 1-1 which is the only option.

    The disk is partitioned with a single NTFS partition with Volume 1 assigned letter C and the partition uses 100% of the disk space, however when I do a detail on the disk I notice that "Boot Disk" is set to No.  The partition disk task I have set the option to create a parimary partition, use 100% of the disk space and make the partition bootable.  This is the same settings I use on all my working XP image deployment tasks.

    The BIOS disk setting is SATA.

    Thursday, May 05, 2011 1:00 PM
  • if you change the bios disk setting, do you notice any change in behaviour ?

    My step by step SCCM Guides
    I'm on Twitter > ncbrady
    Thursday, May 05, 2011 2:50 PM
    Moderator
  • Tried all three settings with the same result.

    Thursday, May 05, 2011 2:57 PM
  • I noticed on the C drive of the deployed image if I open the bootmgr file within the text there is the line:

    "BOOTMGR image is corrupt.  The system cannot boot. BOOTMGR image is corrupt.  The system cannot boot. "

    Could there be something wrong with the image file or the way it was captured?

    Thursday, May 05, 2011 5:17 PM