locked
Error: Litetouch deployment failed return code -1073741819 RRS feed

  • Question

  • Hello!

    I'm new in MDT, I was configuring a deployment for windows W7 and It was working great, but 1 mounth ago I recive a error message: "litetouch deployment failed return code -1073741819" just when the installation wizard should start to copy the file to the PC. The only information that i've found is about error -2147467259.

    The client log didn't show any relevant information and I'm not sure but looks like there aren't any log in the server.

    Any idea about what is happening???

    Log files: https://1drv.ms/f/s!Ap6l8CV7hoqdgTT_b7e82zze1Gwq
    • Edited by Tomeu_Rubi Thursday, September 15, 2016 10:40 AM
    Wednesday, September 14, 2016 9:22 AM

All replies

  • You'll need to look over the logs to hopefully get a hint of what's going on. See - How to find the correct MDT logs

    If you aren't sure what's happening you can post your log to OneDrive and then share it here for one of us to take a look.


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

    Wednesday, September 14, 2016 2:33 PM
  • Thx for your answer Dan, i've edited the original post to include the link to the files. Thanks to your links I could find another BDD.log with more information but anyway I not able to find the source of the problem.
    Thursday, September 15, 2016 10:47 AM
  • Looks like the right smsts.log file isn't posted.

    At 9/15/2016 - 10:57:39 AM we have these errors
    Litetouch deployment failed, Return Code = -1073741819  0xC0000005
    Event 41014 sent: Litetouch deployment failed, Return Code = -1073741819  0xC0000005
    For more information, consult the task sequencer log ...\SMSTS.LOG.

    But the smsts.log file you posted has a time stamp of the previous day and different time.

    I would strongly suggest setting a SLShare value so your logs can be copied. Create a Logs$ share on your server and set the SLShare value to point to that, so the log files will be copied. It makes it easier for you to go back after the fact and look up information about the deployment.

    In the last month have you made any updates to MDT or the ADK? If so did you update your deployment share?


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

    Thursday, September 15, 2016 1:46 PM
  • Lot's of thanks Dan, I couldn't check the SMSTS.log but anyway the error was solved in the last update.
    • Proposed as answer by Apfelwurm2801 Thursday, September 29, 2016 9:50 AM
    Thursday, September 22, 2016 11:43 AM