Share via

MSU Packages in MDT results with OS Failure

lupinlicious 136 Reputation points
2023-04-15T07:11:44.2133333+00:00

Hello,

I'm having a weird issue and it's enough just to add MSU files into the Packages section for the deployment to fail. I do not even need to "Update Deployment Share". If I delete the MSU files I can continue with the OS deployment.

On the screen, it says - "Operating System deployment did not complete successfully. During the deployment process, 0 errors and warnings were reported"

The smsts.log shows me:
<![LOG[Failed to save the current environment block. This is usually caused by a problem with the program
The parameter is incorrect. (Error: 80070057; Source
<![LOG[Could not find CCM install folder.
<![LOG[Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown
<![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.Operation aborted (Error: 80004004)

I've ADK for Windows 11, version 22H2 version 10.1.22621.1
and for WinPE, I'm using Windows 11, version 22H2 version 10.1.22621.1

I wish to install some standalone Windows updates, and I cannot do so from the packages section I can probably solve it in some other ways. I also had a quick look at Johan's temporary fix, but I still have the same problem.
https://www.deploymentresearch.com/making-mdt-work-with-windows-adk-2004-for-bios-machines/

Best regards

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
855 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 42,901 Reputation points Microsoft Vendor
    2023-04-17T02:33:37.62+00:00

    Hi, @lupinlicious

    Thank you for posting in Microsoft Q&A forum and thanks very much for your feedback. We're glad that the problem is solved now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly.

    Problem/Symptom:

    When add MSU files into the package section, the OSD will fail with MDT deployment.

    Solution/Workaround:

    We have to use .CAB files not .MSU

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click ""Add Comment".

  2. lupinlicious 136 Reputation points
    2023-04-18T16:56:40.2966667+00:00

    So I tried to add the following packages listed below in the section to 'Packages' in MDT and I noticed that two of the cab files are listed as 'Security Updates', which will fail to apply the OS, like what I mentioned earlier. I don't understand why?

    2023-04 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5025221) - 104 GB 2023-01 Update for Windows 10 Version 21H2 for x64-based Systems (KB4023057) - 3 MB] 2022-08 Security Update for Windows 10 Version 21H2 for x64-based Systems (KB5012170) Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 Windows Malicious Software Removal Tool x64 - v5.112 (KB890830) - 43 MB 2022-04 Update for Windows 10 Version 21H2 for x64-based Systems (KB5005463) - 4 MB

    I also created a 'Selection Profile' with the updates and then added a task sequence in the 'Postinstall' section. I added the task sequence between 'Add Windows Recovery (WinRE) and 'Next Phase' and then selected 'Install Updates Offline' with my selection profile. During deployment I cannot see that the offline updates are being installed during the deployment? If I look at the logs of ZTIPatches.log, I can see that it has added three packages but not the same GUID as in the 'Packages' section. Each time I deploy it installs:
    GUID: 530437d3-34ec-4baf-8bf2-d14c973f8ef5
    KB5025221 - 2023-04 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems GUID: ab12df76-8ef0-49d1-b9dc-3c3013c25039
    KB4023057 - 2023-01 Update for Windows 10 Version 21H2 for x64-based Systems

    GUID: 1a04862a-9140-4b47-80b3-492f9d72956a
    KB2267602 - Security Intelligence Update for Microsoft Defender Antivirus

    GUID: 01f7dc80-5870-4a79-bb59-fe9071e01405
    KB5012170 - 2022-08 Security Update for Windows 10 Version 21H2 for x64-based Systems

    GUID: fc5ae207-e126-4617-a7a5-8e2b05f690ef
    KB890830 - Windows Malicious Software Removal Tool x64 - v5.112 GUID: 9151c073-854c-474e-8e4c-3b7b067824b1
    KB5005463 - 2022-04 Update for Windows 10 Version 21H2 for x64-based Systems

    I would like to have all six updates installed "Offline" but apparently it's difficult to achive?

    One other thing that I notice when 'ZTIWindowsUpdate.wsf' come in (version 6.3.8456.1000) and when it start to install drivers like 'Intel Extension, Ports, etc...' It takes ages, 2-3 hours? However, if I change 'Const MSIT_WU_REBOOT_MAX = 7' to '1', it will only download CU, SSU, and Security Updates and inside of Windows the rest of the drivers will get installed just fine without any interaction.

    In the log of 'ZTIWindowsUpdate.log' I can see the following:

    <![LOG[Property MSIT_WU_Count is now = 2]LOG]!><time="14:47:42.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="14:47:42.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="14:47:42.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[FAILURE ( 9902 ): ZTIWindowsUpdate has run and failed too many times. Count = 2]LOG]!><time="14:47:42.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="3" thread="" file="ZTIWindowsUpdate"> <![LOG[Event 41002 sent: FAILURE ( 9902 ): ZTIWindowsUpdate has run and failed too many times. Count = 2]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[Microsoft Deployment Toolkit version: 6.3.8456.1000]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[Begin Windows Update. Reboot=[] Retry=[] Count = 2]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[Property MSIT_WU_Count is now = 3]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> <![LOG[FAILURE ( 9902 ): ZTIWindowsUpdate has run and failed too many times. Count = 3]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="3" thread="" file="ZTIWindowsUpdate"> <![LOG[Event 41002 sent: FAILURE ( 9902 ): ZTIWindowsUpdate has run and failed too many times. Count = 3]LOG]!><time="14:47:43.000+000" date="04-18-2023" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">