Uninstalling the ADK and installing the previous version did the trick. Obviously a bug in the latest version.
I have an error running Litetouch.wsf
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?
8 answers
Sort by: Most helpful
-
-
Scott S 11 Reputation points
2023-09-26T19:34:54.93+00:00 I too am having this issue when using the latest version of everything. However, I was able to find an old backup with a version that worked. It appears to be an issue with the PE add-on for the ADK, or the ADK itself (can't be 100% sure since the file appears in multiple locations).
I uninstalled the newest version of the ADK and PE labeled for Windows 11, and installed an older version of the ADK and PE labeled for Windows 10 (ADK product version 10.1.14393.0; PE product version 10.1.19041.1), and everything works as it should now.
I am still using the newest build of the MDT, the properties of the installer show version 6.3.8456.1000
Here is a download link to a zip folder with the ADK, PE, and the same MDT installer I used: LINK
Let me know if this works for you. -
AllenLiu-MSFT 44,101 Reputation points Microsoft Vendor
2023-09-25T06:22:21.0966667+00:00 Hi, @Robin Lund
Thank you for posting in Microsoft Q&A forum.
We may try to regenerate the boot images to see if it helps.
To do this, right-click on the deployment share and select "Update Deployment Share". Make sure to select the "Completely regenerate the boot images" option.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
-
JaredT 0 Reputation points
2023-09-26T15:18:13.73+00:00 I am having this issue too. I've been trying for days to figure it out but no dice. Any suggestions?
-
Matt 1 Reputation point
2023-09-28T19:43:25.1166667+00:00 Seeing this issue as well attempting to create and capture a Windows 11 image....