1

Trying to get a basic MDT deployment process setup. Right now, for testing, I have MDT loaded with a full set of install files from the Win 10 Ent x64 ISO. I'm using PXE boot via WDS to point over to the MDT boot image. During the task sequence it gets to Installing Operating System and makes it to 100%. Then it jumps to an error that I haven't been able to work out yet.

Operating system deployment did not complete successfully.
Please review the log files to determine the cause of the problem.
During the deployment process, 8 errors and 2 warnings were reported.
Details...

FAILURE ( 5616 ): 15299: Verify BCDBootEx
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015F0; 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: 000015F0; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEnd Program
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Any help would be appreciated.

EDIT: Forgot to mention, I did already go through this process since the VM is running in BIOS mode: https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7

EDIT 2:
Task Sequence screenshot as requested
Task Sequence screenshot as requested

Dave
  • 41
  • 1
  • 7
  • IN your task sequence BitLocker setting may be problematic with your hardware/bios mode.. try excluding it and see whether it is the exact problem – Aravinda Jan 25 '21 at 23:38
  • @Aravinda I do have SkipBitLocker=YES in the rules, but I went ahead and disabled the only task I saw regarding BitLocker. It was down in State Restore in the Task Sequence. Got the exact same results. – Dave Jan 26 '21 at 00:30
  • That was an access denied/not found error for the registry query, do you have a post appointment config step? (Before the first reboot). can you send a screenshot of your task sequence around the install operating system task? – Elliot Huffman Jan 26 '21 at 17:07
  • @ElliotLabsLLC I don't see one. I do have a Configure step in the Postinstall if that is what you mean. I've added a screenshot of the task sequence to the original post. – Dave Jan 26 '21 at 18:19
  • Ah, I see you're using the OSD template. The config step is there. I am drawing a blank – Elliot Huffman Jan 26 '21 at 22:07
  • Did you ever figure this error out. I am getting the exact same error after switching my OS to the new 21h1 image. if I switch it back to my old OS in the task sequence it works no problem. – Carlos Cordeiro Oct 21 '21 at 20:22

2 Answers2

0

I had exactly the same error and the fix from Windows 10 deployments fail with Microsoft Deployment Toolkit on computers with BIOS type firmware helped me. Perhaps you missed a step from the instructions?

You can see in Wireshark whether you have the same problem as the one solved in the article. Set the filter to "dhcp" and at one of the steps, the client returns the ia64 architecture instead of the desired one.

Andrew Schulman
  • 8,561
  • 21
  • 31
  • 47
user2924768
  • 1
  • the solution worked for me thanks https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7 – Adil Jun 19 '21 at 15:45
0

Here is an answer for this particular scenario:

  1. You have the same exact error as the question.
  2. You are using an EFI machine (so KB4564442 doesn't apply).
  3. You are using the latest MDT, ADK, and PE add-on from Microsoft as of 2022/02/14.
  4. Your deployment share has a space (other other "unfriendly" character).

My solution was to rename the deployment share and remove the space in its name, regenerate my boot images, and try again.

In my case, what prompted me to try this was I checked BDD.LOG and found these lines.

<![LOG[About to run command: \\wds.example.com\MDT]LOG]!><time="14:28:47.000+000" date="02-15-2022" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has returned: 1]LOG]!><time="14:28:47.000+000" date="02-15-2022" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE ( 5616 ): 1: Verify BCDBootEx]LOG]!><time="14:28:47.000+000" date="02-15-2022" component="LTIApply" context="" type="3" thread="" file="LTIApply">

The first line is an attempt to run a command, but it then ended where the space in my share name "MDT Gold" occurred, so this broke the command. Changing to "MDTGold" fixed it.

Brendan McCoy
  • 1