How to fix MDT Deployment Workbench Windows PE crash

Learn how to stop your Microsoft Deployment Toolkit (MDT) Deployment Workbench from crashing when accessing the Windows PE tab of the deployment share properties.
View the blog post here: www.dannymoran...
Hi, I’m Danny, a London based IT consultant and sporadic blogger. You can view all my blog posts at: www.dannymoran...

[@stevef68]

Thank you! Was having issues capturing a Win11 image. Everything I found said to update the ADKs, but then I got this error message. I haven't deployed x86 in a LONG time, so this quick fix is awesome.

[@danny_moran]

Thanks for watching!

[@KrzysztofJurek]

thanks for the tip 🙂
It also seems to be working fine (as long as you don't need x86) when you create empty folder in that location (as per below path and name).
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs

[@danny_moran]

I haven't actually tried that method of just creating a blank folder. I assumed it would cause some random problem somewhere down the line if any of the x86 files ever get referenced. I'm glad to hear it doesn't cause any issues.
Thanks for watching!

[@double-you5130]

i did that and it didnt work. i had to copy the think like in the video but im running the very latest os and mdt.

[@MentorMel]

Thank you! You've definitely removed some stress from my day. I appreciate you more than you will know ❤❤

[@danny_moran]

Thanks for watching!

[@jonshaw2780]

Thank you, this video saved me a lot of time.

[@danny_moran]

Thanks for watching!

[@TheDJZeroX]

Again, you helped and I learned. Ty

[@danny_moran]

Thanks for watching!

[@Exuberantlemon]

thank you so much!!!!

[@danny_moran]

Thanks for watching!

[@double-you5130]

thanks man such a simple fix - wonder why microsoft is not updating the software to just work on 64 only..

[@danny_moran]

I think it's because Microsoft are no longer supporting MDT, so they don't test the new updates out to see if it breaks anything within MDT.
Thanks for watching!

[@jenda1351]

Great video. Thank you :))

[@danny_moran]

Thanks for watching!

[@jrz08510]

You, Danny, are a god-send!

[@danny_moran]

Thanks for watching! Hope you found it useful!

[@edramos7743]

Worked great. Thanks so much for your help on this!

[@danny_moran]

Glad it helped! Thanks for watching!

[@nicholascardell3371]

THANK YOU!

[@danny_moran]

Thanks for watching!

[@Fiaz92]

Thanks Man!!!!

[@danny_moran]

Thanks for watching!

[@levidobehanzin1850]

Thank you a lot

[@danny_moran]

Thanks for watching!

[@gabrielmoronsanchez3429]

Thanks for the video!!!! 😁😁😁😁

[@danny_moran]

Thanks for watching!

[@pringles2851]

Thanks work Perfectly 😁

[@danny_moran]

Thanks for watching!

[@Mr1lolo94]

+1 - thank you sir!!!

[@danny_moran]

Thanks for watching!

[@TheDryLife]

Good Morning Danny. Your videos have helped me a great deal. Quick question. Is there a way to completely hands free after PXE boot. What I mean is after PXE boot is started can everything be done behind the scenes up to the apps being installed once desktop is loaded.

[@danny_moran]

Yes, you can make it entirely zero-touch.
There are different methods of doing this. If you do a Google search for "MDT zero touch" you should find some guides on how to automate various parts of the process.
Thanks for watching!

[@phpeteur]

thanks !

[@danny_moran]

Thanks for watching, John!

[@davidbriseno910]

Thank you for this! Any way you could lead me to the correct direction on the error below? I deployed my image and when I PXE boot from a windows VM in VMWARE, i get the following error:
Script: X:\deploy\scripts\LiteTouch.wsf
Line: 2
Char: 13
Error: The value for the attribute is not valid: language
Code: 80040049
Source: Windows Script Host
Feel like I have tried everything and nothing seems to work.

[@danny_moran]

Looks like the September 2023 ADK version is causing this issue.
This guide should help you resolve this: www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398/
Hopefully, this resolves the issue.
Thanks for watching!

[@davidbriseno910]

Hey Danny! Great news, after banging my head against the wall. The simple fix was to just use the older windows 11 ADK and not the 22h2 version in your video.
Also, do you think MS will do away with MDT?

[@danny_moran]

MDT is quite neglected at this point, as Microsoft hasn't updated it in quite a while.
Although deploying Windows 11 and Windows Server 2022 work fine (with a couple of workarounds), they're not officially supported, so I doubt that they are going to keep MDT updated going forward.
It's quite frustrating, as MDT is a really useful product, and not everyone needs the additional capabilities that SCCM provides.
I will continue to use MDT in production environments until it's not possible to get it to work or Microsoft provides an alternative lightweight solution (which I doubt will happen).

[@davidbriseno910]

Good thoughts and I have to agree. Thanks for your insight.