none
ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76) RRS feed

  • Question

  • Hi! Getting ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76) during windows 7 x86 Ent installing. LTIApply log:

    <![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Will boot into Windows PE architecture x86 to match OS being deployed.]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[OSDTargetDriveCache was determined earlier : C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Open Control File: OperatingSystems]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[------  Applying Windows image using DISM.exe ------]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI applying image \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent\Sources\install.wim using DISM]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Event 41023 sent: LTI applying image \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent\Sources\install.wim using DISM]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property SourcePath is now = \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Cleaning off old operating system]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76)]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Event 41002 sent: ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76)]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">

    Why so? Also, BDD.log have this line

    <![LOG[Vista identified, skipping update of Device Path]LOG]!><time="09:54:40.000+000" date="01-25-2016" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">

    Why Windows 7 identified as Vista?

    Monday, January 25, 2016 8:58 AM

Answers

  • Yes, and after every change I'm updating deployment share. I'm even had generated completely new boot image. However it's didn't help. Then I made new TS with same tasks, as in broken TS and it's work - dunno why.
    • Marked as answer by Net Ranger Tuesday, January 26, 2016 6:10 AM
    • Edited by Net Ranger Tuesday, January 26, 2016 6:11 AM
    Tuesday, January 26, 2016 6:10 AM

All replies

  • What are your share and file permissions set to?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, January 25, 2016 1:25 PM
    Moderator
  • The share is \\sno-fs03\d$\deploymentshare and I have full permissions there.
    Monday, January 25, 2016 1:43 PM
  • Have you made any recent changes to your deployment share like upgrading to a new version of MDT? Was this a working task sequence and then it suddenly stopped working?


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, January 25, 2016 10:28 PM
  • Yes, and after every change I'm updating deployment share. I'm even had generated completely new boot image. However it's didn't help. Then I made new TS with same tasks, as in broken TS and it's work - dunno why.
    • Marked as answer by Net Ranger Tuesday, January 26, 2016 6:10 AM
    • Edited by Net Ranger Tuesday, January 26, 2016 6:11 AM
    Tuesday, January 26, 2016 6:10 AM
  • Well when you updated to the MDT version that supports Windows 10, the instructions/known issues were that you had to create new task sequences and not keep using the old ones, so maybe that was the problem in this instance.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, January 26, 2016 2:17 PM
  • The broken TS, as well as working, both were created in the same MDT version (6.3)
    Tuesday, January 26, 2016 2:38 PM
  • 6.3 reply isn't interesting. The build number is though. 8290 or 8298 are 2013 update 1. Neither build would I use. However 8330 is good.  If your task sequences were any older version that 8330 then what you saw where you needed to recreate the TS is expected.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    Thursday, January 28, 2016 6:33 AM
    Moderator
  • The broken TS, as well as working, both were created in the same MDT build (dunno which one. All i know is that i didn't made any updates of MDT). Prolly a bad task in TS.
    • Edited by Net Ranger Thursday, January 28, 2016 6:59 AM
    Thursday, January 28, 2016 6:58 AM
  • You can look at add remove programs, any script or BDD.log to see the build number.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, January 28, 2016 8:36 AM
    Moderator