Hi, having an issue with WDS/MDT/ADK setup to deploy Windows 11 Installed a fresh 2019 Server (1809) , fully patched added WDS feature downloaded and installed MDT (latest 6.3.8456.1000) downloaded and installed ADK for WIN11 (latest 10.1.22621.1) downloaded and installed ADK-WINPE for WIN11 (latest 10.1.22621.1) First disable x86 support on the deploymentshare, otherwise you cannot build your WIM/ISO bootimages. MS has removed x86 support from WINPE11. After booting from the generated bootimage, the wizard.hta script crashes .... See picture . tried it on several MDT servers, error stays. Anyone an idea ?

Having the same issue on the new version of ADK. Been digging through logs and the wizard.hta script to see if I can narrow it down, but no luck yet. between this and the x86 tab crash I'm wondering if Microsoft did any testing at all with this release.

This fix is working : https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md

I have the same issue, closing the window and continuing is one option (it works ok)

We reverted to the 10.1.22000.1 Release of the PE environment. I do not trust it, if this is faulty, what else isn't functioning that relies on the script engine ...?

I think its crazy that they clearly released this version without testing it.

MDT and ADK setup for Windows 11 cause script error in deployment

Jaco van den Berg 31

Hi,

having an issue with WDS/MDT/ADK setup to deploy Windows 11

Installed a fresh 2019 Server (1809) , fully patched
added WDS feature
downloaded and installed MDT (latest 6.3.8456.1000)
downloaded and installed ADK for WIN11 (latest 10.1.22621.1)
downloaded and installed ADK-WINPE for WIN11 (latest 10.1.22621.1)

First disable x86 support on the deploymentshare, otherwise you cannot build your WIM/ISO bootimages. MS has removed x86 support from WINPE11.

After booting from the generated bootimage, the wizard.hta script crashes .... See picture .

tried it on several MDT servers, error stays. Anyone an idea ?

RazaullahKhan 6 Reputation points

2022-10-26T23:14:53.377+00:00

The fix is explained in https://learn.microsoft.com/en-us/mem/configmgr/mdt/known-issues

12 answers

Amber 6 Reputation points

2022-06-03T18:48:03.727+00:00

Having the same issue on the new version of ADK. Been digging through logs and the wizard.hta script to see if I can narrow it down, but no luck yet. between this and the x86 tab crash I'm wondering if Microsoft did any testing at all with this release.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Nicolas 6 Reputation points

2022-09-27T07:26:52.03+00:00

This fix is working :

https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md
Please sign in to rate this answer.

1 person found this answer helpful.
Reiner 6 Reputation points

2022-09-27T08:03:00.373+00:00

Works like a charm, thank you so much for adding the workaround here!

Beauregard, Christian 31 Reputation points

2022-09-27T13:11:55.243+00:00

Hi

So i completely remove the XML and replace it with the content of the article because, i have way more stuff in there than what is shown on GitHub

Beauregard, Christian 31 Reputation points

2022-09-27T13:57:22.83+00:00

So i backed up the file, replaced the content, updated my deployment share and regenerated my boot image, the script error has disapear but some of my task sequences have disapeared

Beauregard, Christian 31 Reputation points

2022-09-27T14:32:21.78+00:00

Hi, did you lose anything in your task sequence? Thefix worked for me but lost some task sequences in the process

Reiner 6 Reputation points

2022-09-28T05:45:19.933+00:00

No, everything was like before. I made a backup of the Unattend_PE_x64.xml and edited the file like that:

Changed the order number from the existing <RunSynchronus> space from 1 to 2

added the following lines above <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>

Are you running the latest version? There should be a folder in C:\DeploymentShare\Control for every task sequence you created, and each has it's files ts,xml and Unattend.xml. Are these folders and files still there that you can recover your task sequences?

Beauregard, Christian 31 Reputation points

2022-09-29T15:02:43.857+00:00

Hi

Thanks for the reply, the issue was 18 inch in front of the screen, after moving everyhting, i set the task to run only on X64 and for some reason, that made it hide, i clicked back the "All platform" and everything fine now.

The tweaks also fixed everything, just had to make all my tasksequences again for, fortunately, it's easy to copy paste my custom settings

Thanks

A Ska 241 Reputation points

2022-10-03T15:59:19.017+00:00

Dear

Tried with no luck.
Added reg key, xml substitution (see image), Complete update and rebuild but same javascript error.
ADMK is: 10.1.22621.1

Any idea?

Beauregard, Christian 31 Reputation points

2022-10-03T17:49:05.707+00:00

Hi

i have to ask, did you replace the Lite touch on your WDS after rebuilding?

It worked for me, no more java script error

A Ska 241 Reputation points

2022-10-03T19:02:44.333+00:00

Dear

What do you mean by "replace the Lite touch"?

Beauregard, Christian 31 Reputation points

2022-10-03T19:07:55.9+00:00

Hi,

When you rebuild your boot image aka completely regenerate your boot image, then you have to replace that image in your Windows Deployment service as well.

Navigate to your WDS, in the boot image folder, right-click your lite touche image or whatever name you have given it and choose replace image. Navigate to your C:\DeploymentShare\Boot or whatever other letter you have if it's on another partition and replace, should be fine afterwards

A Ska 241 Reputation points

2022-10-04T17:46:48.433+00:00

Dear

What do you mean by "replace the Lite touch"?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Raz Steinmetz 6 Reputation points

2022-06-01T11:06:24.837+00:00

I have the same issue, closing the window and continuing is one option (it works ok)
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jaco van den Berg 31 Reputation points

2022-06-02T08:51:11.757+00:00

We reverted to the 10.1.22000.1 Release of the PE environment.
I do not trust it, if this is faulty, what else isn't functioning that relies on the script engine ...?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Raz Steinmetz 6 Reputation points

2022-06-02T10:15:49.07+00:00

I think its crazy that they clearly released this version without testing it.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

MDT and ADK setup for Windows 11 cause script error in deployment

12 answers

Your answer