Add Multilingual Support to Windows 10 Distribution - automated batch script

You are right. I saw everything else, but I did not see that Windows 7 does not meet the minimum requirements for adding a second language in an iso file.

Is that why there are so many errors?!

 

Although the errors are again the same as in the picture I uploaded in my comment from the previous page, I followed your advice with this code you wrote and the newly created iso is: 19044.1288.211006-0319.21H2_RELEASE_SVC_PROD1_CLIENT_X64FRE_EN_BG.iso - with 420 MB is more-small from the original base en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso.

I burned the new iso to a flash drive just to check if the start screen would present an option to choose an installation between English and the second added language. Indeed this choice was shown and when the second language was selected the installation was entirely in the added language. It's getting late and I don't have time to complete the installation. This is my second attempt to add a language to an iso file and it turned out to be successful.

Question: Should I be worried about something that the errors in the script are again the same - as in the picture on the front page? Although the new iso has the second language correctly added.

I would even ask you to update the script with those commands you wrote in your previous comment. It's really nice to have the option through Windows 7 (to cover minimal hacking) to be able (officially via your script) to build Windows 10 with the addition of a second language. Or this code you wrote, add it to the script, because your opinion, which contains this code, will be far behind in this thread and... On the other hand - it is logical that through Windows 7 it is possible to create an iso with added second language - as a springboard for Windows 10 (From Windows 7 to migrate to Windows 10).

Since I have no idea what to look at C:\Windows\Logs\DISM and the files created - I am attaching them here and if possible - you tell what and what are the errors.

 

I think I'm sure because from the script window I saw identical errors as my picture from the previous page and I didn't think I needed to take a new picture, but maybe I should have.

As far as I understand - I will have to make the iso file again, but correctly write DEFAULTLANGUAGE to bg-bg. Later today - I will do this, with the correct language spelling, take a picture of the script window with the errors it will show and reattach the files located in C:\Windows\Logs\DISM. At least you know what to look for in them, I'm not familiar at least, but I got excited about adding a second language and it's actually very helpful.

 

I watched the script window the whole time and didn't see an error being written. The finished file now has a new name: 19044.1288.211006-0319.21H2_RELEASE_SVC_PROD1_CLIENT_X64FRE_BG_EN.iso.

Now I plan to apply the said new iso file 19044.1288.211006-0319.21H2_RELEASE_SVC_PROD1_CLIENT_X64FRE_BG_EN.iso via Slimdown10 script

By the way - I am attaching the files from C:\Windows\Logs\DISM so you can look at them and find out if everything is fine or if there is something wrong?!

Thanks for this useful tool, it turned out to be possible even through my current Windows 7 x64 to add a second language to the Windows 10 iso.

 

With 19044 and earlier I never had any issues but I think Im having same issues as Anarethos did on previous page. My current ISO is from MCT and is 19045.2006.
Script works fine integrating Sv-SE and zh-TW but choosing any other language then English during setup doesnt even get me to OOBE, setup itself works fine.

may I ask what updates are required?

 

you can always find latest updates here



^ current set for 19045.2913

SSU + LCU are mandatory for W10MUI

 

Much appreciated
I believe Im to integrate all x64? I seem to recieve the same error

 

you didn't mention your ISO architecture, if it's x86_64 (amd64) then integrate x64 updates

the safest option is to copy full updates set to the "Updates" folder next to the latest W10UI script and it should be fine
generally it's best to integrate languages and updates to the base 19041.1 build, you can get one on UUP dump, but it should work with your refreshed ISO anyway if correct files are provided for W10MUI

 

Yea Im servicing x64 only, I downloaded all updates and placed them in the folder but didnt update to the latest W10U script tho.

Latest UI script didnt help
Edit 2: Using only LCU (SSU combined) works

Edit3 2/5: I had to disable Windows Defender, only after that would the ISO work

 

deleted

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

And by modifying boot.wim?

 

I don't think so, adding autounattend.xml is enough to directly reached to EULA screen.

 

Can you give an example?
When I add mine for pl-PL - the language selection window opens immediately, but en-US.

 

Oh I see what you mean, try to set WINPE as 1(as mentioned in OP) and try again.

 

You need to login to view this posts content.