none
FAILURE (5627): 193: Run DISM.exe

    Question

  •  We captured a .wim image using WDS but are now unable to deploy it via MDT. I get the following error:

    FAILURE (5627): 193: Run DISM.exe

    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Failed to save environment to (80070057)

    Failed to run the action: Install Operating System.

    Unknown error (Error: 000015FB; Source: Unknown)

    The execution of the group (install) has failed and the execution has been aborted. An action failed.

    Etc. Anyone have any idea why this is happening and what I might do to remedy it? Any and all help and suggestions are very much appreciated!

    Monday, March 04, 2013 11:25 PM

Answers

  • Check for LTIApply.log in MININT or Windows\Temp\DeploymentLogs. Search for dism to find out what exactly went wrong.

    I once had this problem because I customized partition schema (which I believe is unsupported and not recommended). I created the first partition as OS drive and the second partition as data drive. Turns out, you should create an extra 500MB system partition ahead because dism command line hard-coded in LTIApply.wsf always assumes that the first partition is system and the second partition is OS.
    • Marked as answer by fubeca6 Wednesday, March 06, 2013 11:39 PM
    Tuesday, March 05, 2013 1:07 AM
  • Oh wow, I found something:

    <![LOG[  Console > An error occurred. You cannot service an x86-based image from an x64-based host that does not support WOW64.]LOG]!>

    Okay, so I'm assuming that that means that I'm attempting to deploy an x86 image from x64 LightTouch - which I am, and I'm now assuming that is the problem. I'm going to try to resolve it, and I'll post back.

    • Marked as answer by fubeca6 Wednesday, March 06, 2013 11:39 PM
    Wednesday, March 06, 2013 11:08 PM

All replies

  • It looks like you are using an old unattend.  You probably need to build a new unattend based off of the OS you are using.

    Open of the failing task sequence in MDT.

    On the OS Info tab choose Edit Unattend.xml.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” How to ask a question that is fixable.

    Monday, March 04, 2013 11:51 PM
  • I don't see how that can be, it's a brand new task sequence, and I've not edited the Unattend.xml, though I have edited the CustomSettings.ini and Bootstrap.ini quite a bit BEFORE adding the custom wim. Is there an alteration that needs to be made to either of those files since I've added the new image?
    Monday, March 04, 2013 11:56 PM
  • Additional Info - After receiving the error above, the machine will reboot INTO Windows, but throw an error that "C:/LitTouch.vbs was not found" and when it fully boots it has not been properly joined to the domain.

    Tuesday, March 05, 2013 12:27 AM
  • Check for LTIApply.log in MININT or Windows\Temp\DeploymentLogs. Search for dism to find out what exactly went wrong.

    I once had this problem because I customized partition schema (which I believe is unsupported and not recommended). I created the first partition as OS drive and the second partition as data drive. Turns out, you should create an extra 500MB system partition ahead because dism command line hard-coded in LTIApply.wsf always assumes that the first partition is system and the second partition is OS.
    • Marked as answer by fubeca6 Wednesday, March 06, 2013 11:39 PM
    Tuesday, March 05, 2013 1:07 AM
  • These are the lines that I was able to find that contained DISM. The last one is the only one that indicates  problem, but I'm not sure what it means.

    Line 160: <![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="14:30:45.000+000" date="03-06-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
     

    Line 167: <![LOG[  Console > The DISM log file can be found at X:\Windows\Logs\DISM\dism.log]LOG]!><time="14:30:46.000+000" date="03-06-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
     

    Line 167: <![LOG[  Console > The DISM log file can be found at X:\Windows\Logs\DISM\dism.log]LOG]!><time="14:30:46.000+000" date="03-06-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
     

    Line 167: <![LOG[  Console > The DISM log file can be found at X:\Windows\Logs\DISM\dism.log]LOG]!><time="14:30:46.000+000" date="03-06-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
     

    Line 169: <![LOG[FAILURE ( 5627 ): 193: Run DISM.exe]LOG]!><time="14:30:46.000+000" date="03-06-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">

    Wednesday, March 06, 2013 11:03 PM
  • Oh wow, I found something:

    <![LOG[  Console > An error occurred. You cannot service an x86-based image from an x64-based host that does not support WOW64.]LOG]!>

    Okay, so I'm assuming that that means that I'm attempting to deploy an x86 image from x64 LightTouch - which I am, and I'm now assuming that is the problem. I'm going to try to resolve it, and I'll post back.

    • Marked as answer by fubeca6 Wednesday, March 06, 2013 11:39 PM
    Wednesday, March 06, 2013 11:08 PM
  • Wow, it worked...I swear I'm such an idiot sometimes. Well hopefully this thread will help someone else as absent minded as me.
    Wednesday, March 06, 2013 11:41 PM
  • The log helped my find what was up. thanks for pointing me it the right direction!
    Wednesday, March 06, 2013 11:41 PM