none
SCCM/WINPE Error - 8460p Task Sequence Error - Bootmgr is missing after windows configuration and setup is ran

    Question

  • Hi all,

    I am Currently running SCCM version 4.00.6487.2000 and PE 3.0. (2008 SP2 32bit)
    We have built an image of an Elitebook 8460p x64 bit with imported drivers, then created driver package and assigned to a task sequence (same as we always do).  The problem is that the task sequence seems to fail during the 5 stage and after (window setup and configuration manager portion) and boots into a BOOTMGR is missing, Press ctrl+alt+delete to restart.  I have verified that the nic and mass storage driver match an existing 8460p laptop that was setup using a windows 7 cd and driver cd that came with the laptop.  I have read quite a bit regarding the bootmgr error message and it seems to point to the diskpart and hidden partitions but assigning the hidden 100mb during the partition piece does not help the matter.  Any suggestions would be greatly appreciated.

    Other info:
    OS = Windows 7 Enterprise x64 bit
    nic = intel(R) 82579LM Gigabit Network Connection version 11.8.84.0 version date = 12/21/2010
    mass storage = Intel(R) ESB2 SATA AHCI Controller version 10.1.2.1004 version date = 1/12/2011

     




    • Edited by eelo Tuesday, May 24, 2011 6:58 PM
    Tuesday, May 24, 2011 5:07 PM

Answers

  • Start up a Litetouch PE instance, and press F8 to start the command pompt.

    Then Startup Diskpart.exe and see which partition is marked "active"

    sel disk 0
    Sel part 1
    Detail Part
    Sel Part 2
    Detail Part
    ... And so on...

    the partition marked "Active" *must* contain the hidden file \BootMgr and the hidden folder \Boot.
    If not, something got messed up, use bcdboot.exe to recover.

     


    Keith Garner (KeithGa.com) - Deployment Consultant - http://deployment.XtremeConsulting.com
    Tuesday, May 24, 2011 6:14 PM

All replies

  • Start up a Litetouch PE instance, and press F8 to start the command pompt.

    Then Startup Diskpart.exe and see which partition is marked "active"

    sel disk 0
    Sel part 1
    Detail Part
    Sel Part 2
    Detail Part
    ... And so on...

    the partition marked "Active" *must* contain the hidden file \BootMgr and the hidden folder \Boot.
    If not, something got messed up, use bcdboot.exe to recover.

     


    Keith Garner (KeithGa.com) - Deployment Consultant - http://deployment.XtremeConsulting.com
    Tuesday, May 24, 2011 6:14 PM
  • Could it be an issue with the HP hidden partition? is there one on the laptop? also, I think you meant 2008 SP2 32bit and not (2008 R2 SP2 32bit)


    -- Get it: http://www.truesec.com/deploymentcd http://www.amazon.com/Deployment-Fundamentals-Vol-Migrating-Windows/dp/1451570031/ref=sr_1_1?ie=UTF8&qid=1301091117&sr=8-1 And get out of the deployment swamp
    Tuesday, May 24, 2011 6:24 PM
  • Shrek46 - The initial out of the box partitioning on the laptop did include a hidden partition.  What i did was load a 64 bit windows 7 Enterprise cd (laptop came with Pro i believe).  I cleared all the partitions and upon doing so, it leaves disk 0 = 100mb system partition (what others refer to as hidden) and disk 1 = 300 gb partition.  I have to load the NIC from the cd included in shipment so the pc will even communicate with the DP's.  When I push the Task sequence , i only partition disk 0 with - the OS primary 100% of the remaining disk.  
    e
    Tuesday, May 24, 2011 7:24 PM


  • Keith - I have identified the active disk as 1 (not hidden), no other disks exist.  I tried to update the task sequence from 0 to 1 and it bombed after the task sequence was selected. 
    e
    Tuesday, May 24, 2011 7:25 PM
  • I'm having basically the same issue with my 8460p tester from HP, I had a thread here that went stale after I posted my bdd.log as requested, the link is here http://social.technet.microsoft.com/Forums/en-US/mdt/thread/b57da292-be1a-4686-bdb6-2461d2af9ea6

    definitely hoping someone can shed some light on this.

    Tuesday, May 24, 2011 7:54 PM
  • I happen to have an 8540W here which I can test on, so I hope to be able to run a test tonight and see what happens.
    -- Get it: http://www.truesec.com/deploymentcd http://www.amazon.com/Deployment-Fundamentals-Vol-Migrating-Windows/dp/1451570031/ref=sr_1_1?ie=UTF8&qid=1301091117&sr=8-1 And get out of the deployment swamp
    Tuesday, May 24, 2011 8:18 PM
  • sounds like a plan - let me know. I'll keep plugging away on my end as well.
    e
    Tuesday, May 24, 2011 8:31 PM
  • Any luck with this? I'm having the same issue with the 8460p.
    Wednesday, June 01, 2011 6:52 PM
  • I haven't made any headway with it yet, there is another similar thread I mentioned earlier and I haven't gotten any kind of fix as of yet

    Wednesday, June 01, 2011 6:59 PM
  • ok i finally got this to work-
    In my case I was importing drivers from the base cd that came with the 8460.  Try removing the touchpad driver and rebuilding the driver portion of your task sequence.  I was able to leave all drivers intact except for the touchpad driver (Synap). 

    *hint you may need to rebuild your import folder all together inorder to get the driver completlely back out.

    Hope this helps.

    -E
    e
    Wednesday, June 01, 2011 7:03 PM
  • So let me get this straight... the touchpad drivers are what are causing this issue!? 

    I'm going to remove them completely just to be sure and trying again, hopefully I can duplicate this resolution.

    Wednesday, June 01, 2011 7:10 PM
  • be sure to remove them from the import folder on your server too (not just within configmgr). 


    e
    Wednesday, June 01, 2011 7:15 PM
  • Removing all of the drivers for the 8460p with the force remove option enabled I then imported only the storage and nic drivers (to keep things to a minimum) and it still fails installing windows 7 enterprise sp1. I will try some other things and report back. Thanks
    Wednesday, June 01, 2011 8:11 PM
  • Just to add my ten cents here,

    I've also noticed a problem with the Synaptics Touchpad Driver when attempting Operating System Deployment using SCCM.  It seems that during the install process the Synpd.inf gets marked as boot-critical when it really isn't, and this causes the install to bomb.  

    If you have your Task Sequence set to "Continue On error", install will appear to complete, but you'll me missing the Windows Boot Manager, a sure sign that the install has failed.

    You can find out if this happening to you too for yourself by looking at the SetupAct.log file after the install bombs.  If you see some lines like:

    2012-04-13 10:20:45, Info PnPIBS: Installing driver X:\WINDOWS\INF\oem71.inf ...
    
    2012-04-13 10:20:45, Info PnPIBS: Installing driver X:\WINDOWS\INF\oem79.inf ...
    
    2012-04-13 10:20:45, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]
    
    2012-04-13 10:20:45, Info [SETUP.EXE] Called script [X:\WINDOWS\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
    
    2012-04-13 10:20:45, Info [0x070042] DIAG   CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
    

    In my environment, we had to remove this driver from all laptop models before OSD would complete successfully. 


    • Proposed as answer by Stephen Owen Monday, April 16, 2012 4:14 PM
    • Edited by Stephen Owen Tuesday, April 17, 2012 8:10 PM Added info
    Monday, April 16, 2012 4:13 PM
  • was the problem solved with the nic-interface? Can not connect to deploymentshare?
    Tuesday, October 16, 2012 11:26 AM