This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 52%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
Hello I'm getting the same error described here:
Same version of MDT, same version of Windows, same version of the ADK. I'm getting the exact same error in the screenshot. They linked an answer here:
https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md
However their answer is to start using Configuration Manager, which costs lots of money.
The issue looks over 6 months old. Has there been any progress on this? Has anyone been able to fix this error and use MDT to deploy Windows 11 22H2 images?
I've read lots of places that you can image Windows 11 with PXE boot functionality using both MDT and WDS. I've been running into nothing but problems trying to do this. Is it really possible?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 7.000000000000001%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Here is the definitive fix:
Uninstall all older versions of apps:
Microsoft Deployment Toolkit
Windows Assessment and Deployment Kit
Windows Assessment and Deployment Kit Windows Preinstallation Environment
Then delete folders:
"C:\Program Files\Microsoft Deployment Toolkit"
"C:\Program Files (x86)\Windows Kits
Download the latest:
Microsoft Deployment Toolkit (6.3.8456.1000 as of 9-5-2023)
https://www.microsoft.com/en-us/download/details.aspx?id=54259
Windows Assessment and Deployment Kit (10.1.22621.1 as of 9-5-2023)
https://go.microsoft.com/fwlink/?linkid=2165884
Windows Assessment and Deployment Kit Windows Preinstallation Environment (10.1.22621.1 as of 9-5-2023)
https://go.microsoft.com/fwlink/?linkid=2166133
Install with default settings
Then open notpad and paste the following:
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>1</Order>
<Path>reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>2</Order>
<Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
</unattend>
Save it as: "Unattend_PE_x64.xml" and replace the same name file located here:
\usstore\HelpdeskTools\Tools\Windows Imaging Software\ADK-22H2-v2\Copy to C Drive\Program Files\Microsoft Deployment Toolkit\Templates
Now make an empty folder located here:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs
Go to the application "DeploymentWorkbench" on your imaging server point to your Deployment Share Folder and tell it to update
Reboot the server:
Now create a whole new boot image by right-clicking on MDT Deployment Share (your location) inside of Deployment Workbench and choosing option (Completely regenerate the boot image) and upload that to your Windows Deployment Service (location usually c or d:\DeploymentShare\boot)
Notes: The best and most glitch free windows PE drivers for both AMD and Intel chipsets including RAID Drivers that I have found are from HP here: https://ftp.hp.com/pub/caps-softpaq/cmit/softpaq/WinPE10.html?source=aw&subacctid=407399&subacctname=Wildfire+Systems%2C+Inc.&adcampaigngroup=122739jumpid=af_gen_nc_ns&utm_medium=af&utm_source=aw&utm_campaign=Wildfire+Systems%2C+Inc.&campaignID=&utm_content=407399_Wildfire+Systems%2C+Inc._&awc=7168_1693927210_4fed9fc7cbdc4f67bb3f50dac5719d46&sn=1
Uninstall all older versions of apps:
Microsoft Deployment Toolkit
Windows Assessment and Deployment Kit
Windows Assessment and Deployment Kit Windows Preinstallation Environment
Then delete folders:
"C:\Program Files\Microsoft Deployment Toolkit"
"C:\Program Files (x86)\Windows Kits
Download the latest:
Microsoft Deployment Toolkit (6.3.8456.1000 as of 9-5-2023)
https://www.microsoft.com/en-us/download/details.aspx?id=54259
Windows Assessment and Deployment Kit (10.1.22621.1 as of 9-5-2023)
https://go.microsoft.com/fwlink/?linkid=2165884
Windows Assessment and Deployment Kit Windows Preinstallation Environment (10.1.22621.1 as of 9-5-2023)
https://go.microsoft.com/fwlink/?linkid=2166133
Install with default settings
Then open notpad and paste the following:
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>1</Order>
<Path>reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>2</Order>
<Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
</unattend>
Save it as: "Unattend_PE_x64.xml" and replace the same name file located here:
\usstore\HelpdeskTools\Tools\Windows Imaging Software\ADK-22H2-v2\Copy to C Drive\Program Files\Microsoft Deployment Toolkit\Templates
Now make an empty folder located here:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs
Go to the application "DeploymentWorkbench" on your imaging server point to your Deployment Share Folder and tell it to update
Reboot the server:
Now create a whole new boot image by right-clicking on MDT Deployment Share (your location) inside of Deployment Workbench and choosing option (Completely regenerate the boot image) and upload that to your Windows Deployment Service (location usually c or d:\DeploymentShare\boot)
Notes: The best and most glitch free windows PE drivers for both AMD and Intel chipsets including RAID Drivers that I have found are from HP here: https://ftp.hp.com/pub/caps-softpaq/cmit/softpaq/WinPE10.html?source=aw&subacctid=407399&subacctname=Wildfire+Systems%2C+Inc.&adcampaigngroup=122739jumpid=af_gen_nc_ns&utm_medium=af&utm_source=aw&utm_campaign=Wildfire+Systems%2C+Inc.&campaignID=&utm_content=407399_Wildfire+Systems%2C+Inc._&awc=7168_1693927210_4fed9fc7cbdc4f67bb3f50dac5719d46&sn=1
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 2%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAH%3C/text%3E%3C/svg%3E)
Allan Khouri's fix worked for me! Very helpful, thank you.
I did some googling and found a solution that seems to have fixed the script error.
I am worried because this is this is the second regedit I've had to do to get MDT to work. In addition to a .dll edit and now a .xml file edit.
This is a total hackjob.
Hi,
Thank you for posting in Microsoft Q&A forum.
You can submit feedback about this issue:
https://feedbackportal.microsoft.com/feedback/forum/4669adfc-ee1b-ec11-b6e7-0022481f8472
I will also keep an eye on this, if there is any update, I will let you know.
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more