locked
MST 2012 - failed to inject drivers - Surface PRO via PXE boot RRS feed

  • Question

  • Standalone media works, boot via USB works. but when I PXE boot it fails right in the beginning at inject drivers. Error = Path not found (76).  Unhandled error returned by ZTIDrivers: Path not found
    Tuesday, August 20, 2013 9:02 PM

All replies

  • Was this resolved with this question?  http://social.technet.microsoft.com/Forums/en-US/0a3b57dc-05e5-47c4-bbfb-77165f29c004/mdt-2012-image-deployment-on-surface-pro

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek


     no, it wasnt.  not sure what path is incorrect.  PXE is working, however, inject drivers fails right away.
    Wednesday, August 21, 2013 2:57 PM
  • Is your Inject Drivers step in the Task Sequence using All Drivers or a specific Selection Profile?  It's obviously talking to the Deployment Share since it started a Task Sequence.  On a machine in WinPE that hits this failure, can you grab and post the bdd.log?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Wednesday, August 21, 2013 3:05 PM
    Answerer
  • Is your Inject Drivers step in the Task Sequence using All Drivers or a specific Selection Profile?  It's obviously talking to the Deployment Share since it started a Task Sequence.  On a machine in WinPE that hits this failure, can you grab and post the bdd.log?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    I tried All drivers and Selection profile with the same results. log: http://sdrv.ms/14jySj0

    do I need to add the drivers in the WDS settings?

    Wednesday, August 21, 2013 5:29 PM
  • interesting.. USB boot I now have the same issue. hmmmm.
    Wednesday, August 21, 2013 6:37 PM
  • but standalone media booting from USB works.. so I dont think its an issue with the drivers themselves.  when it fails, I notice it says, Inject drivers and then it starts to copy the first driver in the list of out of box drivers and then fails.  I removed that first driver as a test and still bombs on the next driver.  confusing.
    Wednesday, August 21, 2013 8:17 PM
  • apparently its not stemming from a driver issue.. It is now failing on LTIApply (path not found)..
    Thursday, August 22, 2013 7:13 PM
  • still having this issue.. failing at Inject drivers.. path not found.. any ideas?
    Tuesday, August 27, 2013 1:53 PM
  • With all the Path Not Founds you are having, maybe you should create a new Deployment Share and then compare the scripts folders between both and ensure that you have all the right files.  Almost sounds like some of the scripts got deleted.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Thursday, August 29, 2013 1:35 AM
    Answerer
  • OK, I will give it a try.  Thanks
    Thursday, August 29, 2013 3:53 PM
  • I created a new deployment share and have the same results.
    Tuesday, September 3, 2013 6:52 PM
  • Yuck. I just looked at the smsts.log you had posted on skydrive, thanks.

    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 8/21/2013 1:14:56 PM 1680 (0x0690)

    My notes reveal that this issue was observed by several people earlier in the year on native uEFI machines. I was unable to track down the issue before my time was up. This does appear to be a bug in the SMS Stand Alone Task Sequencer.

    Best bet is to file a bug on the MDT 2013 Connect site. Be very specific on the bug, and the repro scenario. THis has been an difficult bug to track down.


    Keith Garner - keithga.wordpress.com

    • Proposed as answer by Keith GarnerMVP Wednesday, September 4, 2013 5:49 AM
    Wednesday, September 4, 2013 5:49 AM