none
WinPE 4.0 Will Not Auto Reboot HP Laptops RRS feed

  • Question

  • **MDT 2012 Update 1 (Version: 6.1.2373.0) with ADK**

    I updated my MDT 2010 with WAIK deployment share to using MDT 2012 Update 1 ADK as my new platform. Almost everything I have done works great except for one thing. When I build any of my HP laptops, right after the base image is layed down on the disc and DISM applies the unattend.xml settings (the PostInstall phase), the task sequence just stops leaving an empty command shell window. If I enter the commands "Exit" or "Wpeutil reboot", the computer will reboot and the TS will resume as if nothing had happend. The behavior does not occur on my Desktop computers or my VM's. Only on Laptops.

    When I rebuild the laptops using my older MDT 2010 Deployment Share and after (in WinPE mode) the TS applies the image and runs Setup, the TS will reboot the laptops without any problems.

    I have made no firmware updates to the laptops (Models 6440b, 6560b, 6470b, 6570b). And I have not changed any of the BIOS settings. But WinPE 3.0 will reboot successfully while WinPE 4.0 will not. The TS has had no modifications made to it other than the name of the main Applications bundle that I now install.

    As a side note, with WinPE 4.0, when It leaves behind the cmd.shell window, either typing in "Exit" or "Wpeutil Reboot" will reboot the laptop successfully. So why isnt this happening for me Automatically?


    From: MDT Forum

    Thursday, November 7, 2013 2:23 PM

All replies

  • It is entirely possible that the script is crashing for some reason.

    1. Check the c:\minint\smsosd\osdlogs\bdd.log file for any indication of errors.

    2. You may wish to run the command manually to observe the error (advance debugging):

    * When you reach WinPE, cancel out of the MDT Wizard, or select "command prompt" from the welcome wizard. That should take you to the cmd.exe prompt.

    * from the cmd.exe, run the following command:
        cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture

    * Then run through your installation normally, at the end of the Post-Install phase, it should then exit from litetouch.wsf, do you see an error?!?! This is what we are looking for. 


    Keith Garner - keithga.wordpress.com

    Friday, November 8, 2013 7:05 AM
    Moderator
  • I have the SMSTS.log here. These are the last 100 lines or so.

    \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

    !--------------------------------------------------------------------------------------------! TSManager 11/7/2013 11:26:16 AM 1812 (0x0714)
    Expand a string:  TSManager 11/7/2013 11:26:16 AM 1812 (0x0714)
    Executing command line: cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf" TSManager 11/7/2013 11:26:16 AM 1812 (0x0714)
    Process completed with exit code 0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    !--------------------------------------------------------------------------------------------! TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Successfully complete the action (Next Phase) with the exit win32 code 0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Sending status message . . . TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Expand a string: %_SMSTSMDataPath%\Logs TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Deleting file without retry TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Clear local default environment TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Updated security on object V:\_SMSTaskSequence. TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSNextInstructionPointer=55 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=55 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSInstructionStackString=46 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a TS execution environment variable _SMSTSInstructionStackString=46 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Save the current environment block TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Successfully save execution state and environment to local hard disk TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Start executing an instruciton. Instruction name: Restart computer. Instruction pointer: 55 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSCurrentActionName=Restart computer TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSNextInstructionPointer=55 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a local default variable Message TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a local default variable MessageTimeout TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a local default variable Target TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSLogPath=X:\Windows\TEMP\SMSTSLog TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Expand a string: smsboot.exe /target:WinPE TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Expand a string:  TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Command line for extension .exe is "%1" %* TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set command line: smsboot.exe /target:WinPE TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Start executing the command line: smsboot.exe /target:WinPE TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    !--------------------------------------------------------------------------------------------! TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Expand a string: WinPEandFullOS TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Executing command line: smsboot.exe /target:WinPE TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    ========================= [ smsboot.exe ] ========================= Reboot 11/7/2013 11:26:17 AM 2008 (0x07D8)
    Command line: '"smsboot.exe" /target:WinPE' Reboot 11/7/2013 11:26:17 AM 2008 (0x07D8)
    SMSTSRebootDelay=30 Reboot 11/7/2013 11:26:17 AM 2008 (0x07D8)
    SMSTSRebootMessage=Initiating system reboot Reboot 11/7/2013 11:26:17 AM 2008 (0x07D8)
    SMSTSRebootRequested=WinPE Reboot 11/7/2013 11:26:17 AM 2008 (0x07D8)
    Process completed with exit code 0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    !--------------------------------------------------------------------------------------------! TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Successfully complete the action (Restart computer) with the exit win32 code 0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Sending status message . . . TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Expand a string: %_SMSTSMDataPath%\Logs TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Deleting file without retry TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Clear local default environment TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Updated security on object V:\_SMSTaskSequence. TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSNextInstructionPointer=56 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=56 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a global environment variable _SMSTSInstructionStackString=46 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Set a TS execution environment variable _SMSTSInstructionStackString=46 TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Save the current environment block TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Successfully save execution state and environment to local hard disk TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Reboot to local harddisk TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Skipped RebootSystem() TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    The action (Restart computer) initiated a reboot request TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Sending status message . . . TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    **************************************************************************** TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2) TSManager 11/7/2013 11:26:17 AM 1812 (0x0714)
    Process completed with exit code 2147945410 TSMBootstrap 11/7/2013 11:26:17 AM 1784 (0x06F8)
    Exiting with return code 0x80070BC2 TSMBootstrap 11/7/2013 11:26:17 AM 1784 (0x06F8)
    ==========[ TsProgressUI started in process 1244 ]========== TsProgressUI 11/7/2013 11:26:17 AM 1328 (0x0530)
    Command line: "X:\Deploy\Tools\X64\TSProgressUI.exe"  /Unregister TsProgressUI 11/7/2013 11:26:17 AM 1328 (0x0530)
    Unregistering COM classes TsProgressUI 11/7/2013 11:26:17 AM 1328 (0x0530)
    Unregistering class objects TsProgressUI 11/7/2013 11:26:17 AM 1328 (0x0530)
    Shutdown complete. TsProgressUI 11/7/2013 11:26:17 AM 1328 (0x0530)

    \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

    If I read this log correctly, it thinks it has done it job and initiated a reboot?

    I will try your suggestion Keith and see what shows up.


    From: MDT Forum

    Friday, November 8, 2013 12:15 PM
  • I ran the Litetouch as described by Keith and it looks like the return from SMSTS.log is 0x80070BC2

    /////////////////////////////////// SMSTS.Log //////////////////////////

    Successfully complete the action (Restart computer) with the exit win32 code 0 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Sending status message . . . TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Clear local default environment TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Updated security on object C:\_SMSTaskSequence. TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a global environment variable _SMSTSNextInstructionPointer=18 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=18 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a global environment variable _SMSTSInstructionStackString=0 12 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 12 TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Save the current environment block TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Successfully save execution state and environment to local hard disk TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Reboot to local harddisk TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Skipped RebootSystem() TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    The action (Restart computer) initiated a reboot request TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Sending status message . . . TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    **************************************************************************** TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2) TSManager 10/10/2013 7:23:42 AM 2488 (0x09B8)
    Process completed with exit code 2147945410 TSMBootstrap 10/10/2013 7:23:42 AM 1392 (0x0570)
    Exiting with return code 0x80070BC2 TSMBootstrap 10/10/2013 7:23:42 AM 1392 (0x0570)
    ==========[ TsProgressUI started in process 2832 ]========== TsProgressUI 10/10/2013 7:23:42 AM 1280 (0x0500)
    Command line: "C:\MININT\Tools\X64\TSProgressUI.exe"  /Unregister TsProgressUI 10/10/2013 7:23:42 AM 1280 (0x0500)
    Unregistering COM classes TsProgressUI 10/10/2013 7:23:42 AM 1280 (0x0500)
    Unregistering class objects TsProgressUI 10/10/2013 7:23:42 AM 1280 (0x0500)
    Shutdown complete. TsProgressUI 10/10/2013 7:23:42 AM 1280 (0x0500)

    ////////////////// End of log SMSTS.log //////////////////////////

    An "Exit" inside the Shell window reboots the laptop and the deployment seems fine, all the way to a good finish. ??

    I Googled 0x80070BC2 with TSMBootstrap but did not find anything that I think applies to me.


    From: MDT Forum

    Tuesday, November 12, 2013 4:12 PM
  • Are there other logs besides the BDD.log and the SMSTS.log that would show what is happening when the TS tries to issue the reboot command?

    From: MDT Forum

    Wednesday, November 13, 2013 11:44 AM
  • Thanks, but I didn't ask for the smsts.log file.  :^)

    0x80070BC2 - ERROR_SUCCESS_REBOOT_REQUIRED

    Is not an error, it's just normal operation, time to reboot.

    What about the bdd.log file? Can you post that on a public share like SkyDrive.

    Also what about running the command *within* WinPE (after you get the cmd.exe window failure).

    cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture

    -k


    Keith Garner - keithga.wordpress.com

    Thursday, November 14, 2013 4:59 AM
    Moderator
  • Hi Keith, Sorry it has taken so longggg to get back, but vacations and all....

    I was following another post on-line (which your name is on) about drivers not loading correctly in WinPE (WPEINIT), and when that happens WinPE disables the auto reboot at the end of the processes.

    So I looked at the WPEINIT.LOG and sure enough I have a failure in the WPEINIT.log for a driver.

    Sorry, my company does not allow Dropbox and stuff like that.

    ============== WPEINIT.LOG =============================

    2013-12-03 07:33:26.448, Info      WPEINIT is processing the unattend file [X:\unattend.xml]
    2013-12-03 07:33:26.448, Info      Spent 844ms initializing removable media before unattend search
    2013-12-03 07:33:26.480, Info      ==== Initializing Display Settings ====
    2013-12-03 07:33:26.480, Info      Setting display resolution 1024x768x32@60: 0x00000000
    2013-12-03 07:33:26.480, Info      STATUS: SUCCESS (0x00000000)
    2013-12-03 07:33:26.480, Info      ==== Initializing Computer Name ====
    2013-12-03 07:33:26.480, Info      Generating a random computer name
    2013-12-03 07:33:26.480, Info      No computer name specified, generating a random name.
    2013-12-03 07:33:26.480, Info      Renaming computer to MININT-F4CEJ8E.
    2013-12-03 07:33:26.480, Info      Waiting on the profiling mutex handle
    2013-12-03 07:33:26.480, Info      Acquired profiling mutex
    2013-12-03 07:33:26.480, Info      Service winmgmt disable: 0x00000000
    2013-12-03 07:33:26.480, Info      Service winmgmt stop: 0x00000000
    2013-12-03 07:33:26.495, Info      Service winmgmt enable: 0x00000000
    2013-12-03 07:33:26.495, Info      Released profiling mutex
    2013-12-03 07:33:26.495, Info      STATUS: SUCCESS (0x00000000)
    2013-12-03 07:33:26.495, Info      ==== Initializing Virtual Memory Paging File ====
    2013-12-03 07:33:26.495, Info      No WinPE page file setting specified
    2013-12-03 07:33:26.495, Info      STATUS: SUCCESS (0x00000001)
    2013-12-03 07:33:26.495, Info      ==== Initializing Optional Components ====
    2013-12-03 07:33:26.495, Info      WinPE optional component 'Microsoft-WinPE-Dot3Svc' is present
    2013-12-03 07:33:26.667, Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
    2013-12-03 07:33:26.683, Info      WinPE optional component 'Microsoft-WinPE-MDAC' is present
    2013-12-03 07:33:26.683, Info      WinPE optional component 'Microsoft-WinPE-PPPoE' is present
    2013-12-03 07:33:27.902, Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
    2013-12-03 07:33:27.917, Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
    2013-12-03 07:33:27.917, Info      STATUS: SUCCESS (0x00000000)
    2013-12-03 07:33:27.917, Info      ==== Initializing Network Access and Applying Configuration ====
    2013-12-03 07:33:27.917, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
    2013-12-03 07:33:27.933, Info      Global handle for profiling mutex is non-null
    2013-12-03 07:33:27.933, Info      Waiting on the profiling mutex handle
    2013-12-03 07:33:27.933, Info      Acquired profiling mutex
    2013-12-03 07:33:28.214, Info      Install MS_MSCLIENT: 0x00000000
    2013-12-03 07:33:28.214, Info      Install MS_NETBIOS: 0x00000000
    2013-12-03 07:33:28.277, Info      Install MS_SMB: 0x00000000
    2013-12-03 07:33:28.370, Info      Install MS_TCPIP6: 0x00000000
    2013-12-03 07:33:28.870, Info      Install MS_TCPIP: 0x00000000
    2013-12-03 07:33:28.870, Info      Service dhcp start: 0x00000000
    2013-12-03 07:33:28.870, Info      Service lmhosts start: 0x00000000
    2013-12-03 07:33:28.949, Info      Service ikeext start: 0x00000000
    2013-12-03 07:33:29.042, Info      Service mpssvc start: 0x00000000
    2013-12-03 07:33:29.042, Info      Released profiling mutex
    2013-12-03 07:33:29.042, Info      Spent 1110ms installing network components
    2013-12-03 07:33:29.417, Info      Installing device ms_ndiswanip X:\windows\INF\netrasa.inf succeeded
    2013-12-03 07:33:37.365, Info      Installing device pci\ven_8086&dev_1503&subsys_179c103c X:\windows\INF\oem162.inf succeeded
    2013-12-03 07:33:37.554, Info      Installing device root\kdnic X:\windows\INF\kdnic.inf succeeded
    2013-12-03 07:33:37.759, Info      Installing device ms_ndiswanipv6 X:\windows\INF\netrasa.inf succeeded
    2013-12-03 07:33:38.026, Info      Installing device ms_ndiswanbh X:\windows\INF\netrasa.inf succeeded
    2013-12-03 07:33:40.367, Info      Installing device pci\ven_8086&dev_0890&subsys_40228086 X:\windows\INF\oem233.inf failed with status 0x80070002
    2013-12-03 07:33:40.476, Info      Spent 11422ms installing network drivers
    2013-12-03 07:33:40.476, Info      STATUS: FAILURE (0x80070002)
    2013-12-03 07:33:40.476, Info      ==== Applying Firewall Settings ====
    2013-12-03 07:33:40.476, Info      STATUS: SUCCESS (0x00000001)
    2013-12-03 07:33:40.476, Info      ==== Executing Synchronous User-Provided Commands ====
    2013-12-03 07:33:40.476, Info      Parsing RunSynchronousCommand: 1 entries
    2013-12-03 07:33:40.476, Info        Command 0: 0x00000000
    2013-12-03 07:45:06.821, Info      Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x0000145a)
    2013-12-03 07:45:06.821, Info      STATUS: FAILURE (0x8007145a)
    2013-12-03 07:45:06.821, Info      ==== Executing Asynchronous User-Provided Commands ====
    2013-12-03 07:45:06.821, Info      STATUS: SUCCESS (0x00000001)
    2013-12-03 07:45:06.821, Info      ==== Applying Shutdown Settings ====
    2013-12-03 07:45:06.821, Info      No shutdown setting was specified
    2013-12-03 07:45:06.821, Info      STATUS: SUCCESS (0x00000001)
    2013-12-03 07:45:06.821, Warning   Applying WinPE unattend settings failed with status 0x80070002; ignoring shutdown settings

    ================ WPEINIT.LOG ==================================

    So, now to figure out why that driver does not want to load...


    From: MDT Forum

    Tuesday, December 3, 2013 1:08 PM
  • I don't see *ANY* problems with the WPEInit.log file.

    It appears that WinPE tried installing two drivers, one for pci\ven_8086&dev_1503 which is a Gigabit device was a *SUCCESS*. The other was for pci\ven_8086&dev_0890 which failed, but that's OK, since it's a Wireless device, and most deployment systems (MDT included) won't work over wireless.

    -k


    Keith Garner - keithga.wordpress.com

    Tuesday, December 3, 2013 5:39 PM
    Moderator