MDT errors when building an image with Win 10 1809

[Jeepjockey]

I've got a curly one for you that I've not been able to find a solution for with the usual googling. I'm running a build\capture task sequence which has been running just fine using Win 10 1606 LTSB as the source. I decided to give 1809 a try and updated my MDT infrastructure to the 1809 ADK\Win PE Add-on and MDT 8450.

 

The MDT process now fails at this point “Failed to run the last action: Install Operating System. Execution of task sequence failed.” I’ll post the complete error below. The boot process is fine and I get about 20% into the install OS routine before it errors out. The weird thing is if I replace the Win 10 1809 OS source files with Win 10 1803 OS source files the build completes successfully.

 

Any of you peeps out there come across this before is nobody yet using 1809 as there are way too many issues with it? At this stage it's looking likely that we will go ahead with the 1803 deployment.

 

====================

FAILURE (5627): -2146498514 0x800F082E: Run DISM.exe

LiteTouch deployment failed, Return Code = -2147467259 0x80004005

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.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Install Operating System. Execution of task sequence failed.

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

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecurityInfo() failed.

SetObjectOwner() failed. 0x8007005

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram

GetTsRegValue() is unsuccessful. 0x80070002

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

==================================

 

Cheers

David

[MYK-IT]

Hi @Jeepjockey

 

By pure conincidence, I had the same / similar issue yesterday with our MDT server.

 

I had originally built our MDT Server many months ago, so with wanting to test Windows (1809) deployment etc. I too upgraded with 1809 ADK as well as the WinPE Add-On for MDT8450.

 

I too had the LiteTouch deployment failed, Return Code = -2147467259 0x80004005 failure, and after many hours searching online etc. resulting in the fact that the error doesn't help (or specifically specify what is at fault!) I tracked it down to a corrupted PowerShell script that I was using (for the 1809 task sequence). Basically i had inadvertently copied in some of the text-formatting codes into the PowerShell script!

 

If it helps, the instructions I was following are https://deploymentresearch.com/Research/Post/1676/Building-a-Windows-10-v1809-reference-image-using-Microsoft-Deployment-Toolkit-MDT

[Jeepjockey]

Thanks @MYK-IT I will check this out. One of the things I had tried was cloning the working 1803 task squence and just changed the OS to 1809 but it still failed.

[danflynn]

I was also getting the 0x80004005 error and I finally figured it out after building a new Deployment share. Check your Packages folder in MDT disable all of the packages in there and see if it runs. I had .Net 3.5 enabled.

[snagrat]

I was also getting the 0x80004005 error and I finally figured it out after building a new Deployment share. Check your Packages folder in MDT disable all of the packages in there and see if it runs. I had .Net 3.5 enabled.

 

You need to import the newer .net from the 1809 source

[danflynn]

I figured that just wanted to let the OP know that might also be the cause of their issue. I had only added .Net 3.5 after the 1803 update and forgot about it would figure MDT would just skip the package if it wasn't for that version. Do you know if you can load multiple .Net packages and it will just pick the correct one? Since we have a LTSB 2016 image that needs it and also a 1803/1809 image that needs it.

[chaplic]

I just had the same issue, different cause, posting here for others as I didn't see it elsewhere

 

My issue was I was running the machine to be built in hyper-v with dynamic memory set at defaults. Disabling dynamic memory solved the issue.