none
Starting a Standalone Deployment (boot to USB) launches a DOS windows with wpeinit and then nothing RRS feed

  • Question

  • So I can boot my laptop from USB to my Deployment Share PC and the Microsoft Deployment Wizard comes up fine and works like it should.  I created a standalone Media set in the Deployment Kit and copied it to a bootable USB drive.  When I boot to it it comes up to a DOS screen with this in it:

    X:\windows\system32>wpeinit

    X:\windows\system32>blinking cursor

    It does not launch the Deployment Wizard and I can't figure it out.  I'm using a WinPE10 driver Injection profile (the same as when I connect to the Deployment Share).  Below is my wpeinit.log file.  Can anyone help?  I'm running the ver 8450 of the Toolkit.  

    2018-01-25 09:34:00.668, Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
    2018-01-25 09:34:00.668, Info      Spent 704ms initializing removable media before unattend search
    2018-01-25 09:34:00.699, Info      ==== Initializing Display Settings ====
    2018-01-25 09:34:00.699, Info      No display settings specified
    2018-01-25 09:34:00.699, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:00.699, Info      ==== Initializing Computer Name ====
    2018-01-25 09:34:00.699, Info      Generating a random computer name
    2018-01-25 09:34:00.699, Info      No computer name specified, generating a random name.
    2018-01-25 09:34:00.699, Info      Renaming computer to MININT-592JJO0.
    2018-01-25 09:34:00.699, Info      Waiting on the profiling mutex handle
    2018-01-25 09:34:00.699, Info      Acquired profiling mutex
    2018-01-25 09:34:00.699, Info      Service winmgmt disable: 0x00000000
    2018-01-25 09:34:00.699, Info      Service winmgmt stop: 0x00000000
    2018-01-25 09:34:00.715, Info      Service winmgmt enable: 0x00000000
    2018-01-25 09:34:00.715, Info      Released profiling mutex
    2018-01-25 09:34:00.715, Info      STATUS: SUCCESS (0x00000000)
    2018-01-25 09:34:00.715, Info      ==== Initializing Virtual Memory Paging File ====
    2018-01-25 09:34:00.715, Info      No WinPE page file setting specified
    2018-01-25 09:34:00.715, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:00.715, Info      ==== Initializing Optional Components ====
    2018-01-25 09:34:00.715, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:00.715, Info      ==== Initializing Network Access and Applying Configuration ====
    2018-01-25 09:34:00.715, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
    2018-01-25 09:34:00.715, Info      Global handle for profiling mutex is non-null
    2018-01-25 09:34:00.715, Info      Waiting on the profiling mutex handle
    2018-01-25 09:34:00.730, Info      Acquired profiling mutex
    2018-01-25 09:34:00.776, Info      Service dhcp start: 0x00000000
    2018-01-25 09:34:00.776, Info      Service lmhosts start: 0x00000000
    2018-01-25 09:34:00.968, Info      Service ikeext start: 0x00000000
    2018-01-25 09:34:01.093, Info      Service mpssvc start: 0x00000000
    2018-01-25 09:34:01.093, Info      Service NetBIOS start: 0x00000000
    2018-01-25 09:34:01.155, Info      Service LanmanWorkstation start: 0x00000000
    2018-01-25 09:34:01.155, Info      Service mrxsmb10 start: 0x00000000
    2018-01-25 09:34:01.171, Info      Released profiling mutex
    2018-01-25 09:34:01.171, Info      Spent 453ms installing network components
    2018-01-25 09:34:02.124, Info      Installing device root\kdnic X:\windows\INF\kdnic.inf succeeded
    2018-01-25 09:34:02.968, Info      Spent 1797ms installing network drivers
    2018-01-25 09:34:03.093, Error     QueryAdapterStatus: no adapters found.
    2018-01-25 09:34:03.093, Info      Spent 0ms confirming network initialization; status 0x80004005
    2018-01-25 09:34:03.093, Info      WaitForNetworkToInitialize failed; ignoring error
    2018-01-25 09:34:03.093, Info      STATUS: SUCCESS (0x003d0001)
    2018-01-25 09:34:03.093, Info      ==== Applying Firewall Settings ====
    2018-01-25 09:34:03.093, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:03.093, Info      ==== Executing Synchronous User-Provided Commands ====
    2018-01-25 09:34:03.093, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:03.093, Info      ==== Executing Asynchronous User-Provided Commands ====
    2018-01-25 09:34:03.093, Info      STATUS: SUCCESS (0x00000001)
    2018-01-25 09:34:03.093, Info      ==== Applying Shutdown Settings ====
    2018-01-25 09:34:03.093, Info      No shutdown setting was specified
    2018-01-25 09:34:03.093, Info      STATUS: SUCCESS (0x00000001)

    Thursday, January 25, 2018 2:50 PM

All replies

  • Have you seen this article?

    https://social.technet.microsoft.com/Forums/en-US/53abc60e-a64c-4d9a-a2cf-137e17097c8f/winpe-command-prompt-issue-reappears-in-mdt-2012-with-dart-installed?forum=mdt

    Monday, January 29, 2018 2:06 PM
  • Have you seen this article?

    https://social.technet.microsoft.com/Forums/en-US/53abc60e-a64c-4d9a-a2cf-137e17097c8f/winpe-command-prompt-issue-reappears-in-mdt-2012-with-dart-installed?forum=mdt

    Last Friday I deleted the Media and completely re-generated it.  This fixed the issue for me.  Appreciate the link.  Thank you!
    Monday, January 29, 2018 2:11 PM