Running Litetouch over a pxe boot, the client machine returns an error 'The value for the attribute is not valid : language' in the Litetouch.wsf script This is a newly built deployment server using the latest ADK and MDT installs. I've never seen this before. Any ideas?

This fixes the problem for me: https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md#hta-applications-report-script-error-after-upgrading-to-adk-for-windows-11-version-22h2 If the link doesn't take you straight to the section, look for the title "HTA Applications Report Script Error After Upgrading to ADK for Windows 11 Version 22H2".

Coming back to this again after I got everything working... here's what I did to get it all working: First, go here, follow these instructions: https://www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398/ Next, follow these instructions, just for the section titled "HTA Applications report script error after upgrading to adk for windows 11 22H2": https://learn.microsoft.com/en-us/mem/configmgr/mdt/known-issues#hta-applications-report-script-error-after-upgrading-to-adk-for-windows-11-version-22h2 Go into MDT, right click your Deployment Share, choose Update Deployment Share, and choose to completely regenerate your boot image. Replace your image in WDS using the new boot image you just generated in Step 3 (it will be in <Path to Deployment Share>\Boot).

I have an error running Litetouch.wsf

Robin Lund 55

Running Litetouch over a pxe boot, the client machine returns an error 'The value for the attribute is not valid : language' in the Litetouch.wsf script

User's image

This is a newly built deployment server using the latest ADK and MDT installs.

I've never seen this before. Any ideas?

Mahmoud Fawzy 20 Reputation points

2023-10-24T13:20:14.8466667+00:00

Guys, no need through all those trouble, Only do 2 things:

1- Install the most recent ADK from Microsoft.

2- for the PE add-on, the most recent one that Microsoft is providing is a faulty one.

so please download this one and it should be working fine:

https://go.microsoft.com/fwlink/?linkid=2120253
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Edward Campbell 0 Reputation points

2024-04-24T15:56:46.76+00:00

Signed in to upvote this.

7 answers

Bill Clark 0 Reputation points

2023-09-29T15:51:20.16+00:00

This fixes the problem for me:

https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md#hta-applications-report-script-error-after-upgrading-to-adk-for-windows-11-version-22h2

If the link doesn't take you straight to the section, look for the title "HTA Applications Report Script Error After Upgrading to ADK for Windows 11 Version 22H2".
Please sign in to rate this answer.
Ian Meier 15 Reputation points

2023-10-01T13:36:22.52+00:00

Sadly, I attempted the work around, it still returned the same error message that I received. The one that I received was that the language value was invalid. If that's an easy edit please let me know, as I am relatively new to scripting and working with ADK/MDT

Jacob Wilkin 10 Reputation points

2023-10-02T04:39:01.4833333+00:00

Tried the same and it also didn't help. Getting the same error

HB 0 Reputation points

2023-10-02T12:31:04.0566667+00:00

Didn't work for me either, maybe this one could help: https://www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398/
Have not tested it

Bill Clark 0 Reputation points

2023-10-02T12:32:21.3333333+00:00

Revisiting this. The HTA app launched once, but after clicking next, it dumped back to the desktop. Hasn't booted back to the HTA app since. I was so pumped that the HTA app launched that I posted before testing it. Sorry!
Sign in to comment
Bill Clark 0 Reputation points

2023-10-03T13:38:06.78+00:00
Coming back to this again after I got everything working... here's what I did to get it all working:

First, go here, follow these instructions: https://www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398/

Next, follow these instructions, just for the section titled "HTA Applications report script error after upgrading to adk for windows 11 22H2": https://learn.microsoft.com/en-us/mem/configmgr/mdt/known-issues#hta-applications-report-script-error-after-upgrading-to-adk-for-windows-11-version-22h2

Go into MDT, right click your Deployment Share, choose Update Deployment Share, and choose to completely regenerate your boot image.

Replace your image in WDS using the new boot image you just generated in Step 3 (it will be in <Path to Deployment Share>\Boot).
Please sign in to rate this answer.
Ian Meier 15 Reputation points

2023-10-03T13:43:48.65+00:00

Will try to attempt this fix as well. How fast did you have to be update the files as DSIM was running?

Bill Clark 0 Reputation points

2023-10-03T14:04:59.74+00:00

On the Win 11 Preview VM I spun up, I had to try 2-3 times because if I waited until 60%, it would finish and delete the files before they were done copying.

If you ctrl-drag/drop the new folder from C:\Windows\SoftwareDistribution\Download (it's a long alphanumeric string for the folder name) right when it hits 50%, you'll get it all before it's deleted.

I tried the "set a temporary deny for SYSTEM on the Download folder" thing they suggested, but that caused the DISM command to error out.

All in all, I think it took me 10 minutes to get the 4 FOD files.
Sign in to comment