Jump to content


  • 0
Nolfir

MDT fail at the end of the installation

Question

Hello

I have an issue with MDT since approximately 2 month :

 

I have a MASTER i need to update (windows, driver, soft). 

I deploy the master, make updates then capture the .wim to rebuild the iso. I never had any problem until the begining of this year :

After doing winows update (21h2) i can't deploy anymore, i got this error : "MDT Deployment Failure (5624): 5 run DISM"

I put the smts.log in attachment.

 

I don't see the link between windows 21h2 and the error in the smts.log. 

May be it is a problem with 21h2, but if so there would be many thread on internet with this error i guess ?

 

Things i already tried :

-MDT  + adk up to date ( i even tried older version, and w11 version)

- Fix UEFI

- no "full package" in ts

- uninstall this update but impossible : it's going back whatever i do 

 

Does it speak to anyone ? (smts.log does show some error but i am not sure to understand everything)

 

Thanks in advance

 

smsts.log

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

here's the failure...

 

<![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"]LOG]!><time="15:14:36.471+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="CommandLine.cpp:819">
<![LOG[Process completed with exit code 5624]

which then leads to...

Failed to run the action: Install Operating System.
Unknown error (Error: 000015F8; Source: Unknown)

<![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="0" thread="2028" file="instruction.cxx:1037">
<![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows
)

why is there an F:\ drive referenced in the log....

<![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="0" thread="2028" file="instruction.cxx:1037">
<![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="3" thread="2028" file="instruction.cxx:221">
<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="0" thread="2028" file="String.cpp:1364">
<![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="3" thread="2028" file="engine.cxx:249">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:22:24.166+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="utils.cpp:6604">
<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="3" thread="2028" file="tsmanager.cpp:1273">
<![LOG[****************************************************************************]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="tsmanager.cpp:1301">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="3" thread="2028" file="tsmanager.cpp:1302">
<![LOG[Cleaning Up.]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="tsmanager.cpp:794">
<![LOG[Removing Authenticator]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="tsmanager.cpp:922">
<![LOG[Cleaning up task sequence folder]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="utils.cpp:2707">
<![LOG[File "F:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070005)]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="3" thread="2028" file="CcmFile.cpp:219">
<![LOG[Unable to delete file F:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="15:22:24.181+480" date="02-28-2022" component="TSManager" context="" type="1" thread="2028" file="CcmFile.cpp:1154">

see if you have an LTIApply.log anywhere and what does it reveal...

Share this post


Link to post
Share on other sites

  • 0

Hello,

 

I don't know why it's creating this F:\ drive.

In BDD.logs the first diskpart show this :

  Console >   Volume 0     C   Windows      NTFS   Partition    235 GB  Healthy                ZTIDiskpart    01/03/2022 14:17:40    0 (0x0000)
  Console >   Volume 1         BOOT         FAT32  Partition    499 MB  Healthy    Hidden      ZTIDiskpart    01/03/2022 14:17:40    0 (0x0000)
  Console >   Volume 2         Recovery     NTFS   Partition   2442 MB  Healthy    Hidden      ZTIDiskpart    01/03/2022 14:17:40    0 (0x0000)
  Console >   Volume 3     D   DVD_ROM      NTFS   Removable    230 GB  Healthy                ZTIDiskpart    01/03/2022 14:17:48    0 (0x0000)
  Console >   Volume 4     E   UEFI_NTFS    FAT    Removable    512 KB  Healthy                ZTIDiskpart    01/03/2022 14:17:48    0 (0x0000)

 

Here volume 0 is my previous fail installation with MDT. The weird thing is each single file is here but i can't boot on it the bios doesn't show it. (i have try  to format C:\ before the deployment but still same errors).

I can deploy the .wim manually with DISM, it will works from 0 to 100% with 0 error but like MDT i can't boot on it

 

 

Then i got this :

  Console > DISKPART>     ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info    ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------    ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   Volume 1     V   BOOT         FAT32  Partition    499 MB  Healthy    Hidden      ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console > * Volume 2     G   Recovery     NTFS   Partition   2442 MB  Healthy    Hidden      ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   Volume 3     D   DVD_ROM      NTFS   Removable    230 GB  Healthy                ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   Volume 4     E   UEFI_NTFS    FAT    Removable    512 KB  Healthy                ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)
  Console >   Volume 5     F   Windows      NTFS   Partition    235 GB  Healthy                ZTIDiskpart    01/03/2022 14:17:54    0 (0x0000)

 

Why ? 🤪

Also i can't find "LTIApply.log" anywhere.... i got many logs but not this one

I tried to add bdd.logs but it doesn't works, writing "loading" indefinitely. Seems like there is no error anyway, exept this f:\ 

 

I can deploy the .wim manually with DISM, it will works from 0 to 100% with 0 error but like MDT i can't boot on it

 

We will rebuild this master from scratch in one or 2 month so i can live with it but i wish i understand what happen there.

Thanks for trying to help anyway.

(and sorry for my english i hope there is no bleeding eyes )

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.