No, but I finished updating the script for W11 24H2 (26100.1). Thanks for reminding me.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
PowerShell GUI for Downloading Language Packs - W10_11LangPack.ps1
- Thread starter garlin
- Start date
Faltomalto
Member
Can you create a program that integrates the script W10MUI (abodi) script with your pwershell GUI
I don't see the point. W10MUI is written for users who don't have NTLite, or other image modding tools.Can you create a program that integrates the script W10MUI (abodi) script with your pwershell GUI
Both software overlap in most basic LP and local FOD package integration functions. W10MUI does some work that NTLite doesn't, like adding a language selection menu in WinPE or including local versions of Features on Demand (FOD) packages. LIP's & LXP's are still not that popular, mostly because they don't completely cover all parts of the Windows UI.
You can find FOD's on the list of Optional Features here: Language Packs
Extracted FOD packages can be added as local Updates.
I'm not trying to replace NTLite, but make it easier to locate the required files it needs to add language support. If you think NTLite needs more integration features, share your feedback with nuhi.
Windows 11, version 23H2 (22631.3520)
Change ID
Sorry, that's not how it works.Windows 11, version 23H2 (22631.3520)
Change ID
LP's don't get refreshed after the RTM or GA releases, and 22H2 & 23H2 share the same LP's.
Windows 11, version 22H2 (22621.1) amd64
Code:
d41c9188d2cda4138840bf499c173a40d72af6cb *Microsoft-Windows-Client-LanguagePack-Package_en-us-amd64-en-us.esd
e7e86fcb2cb686c1944782c274da8042c962983d *Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64.cab
cd1424a3c5a4dc0e5cf36fe0c8d48c5342352ac1 *Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64_cd1424a3.cab
84e2492629838ba9498493fd702888d4fe522874 *Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64.cab
6a520a35555da88b9391d9def6721b7b72c7fee0 *Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64_6a520a35.cab
b6b475c452556c54191d2c269ef5435637345f36 *Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64.cab
da4aed69783b27b0d94e7e23ebce34ba0e428621 *Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64_da4aed69.cab
66d8a6c549aefaffc2792a5a890c397e5bcd78eb *Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64.cab
2e4fc62f9539025000d692040af056656edce522 *Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64_2e4fc62f.cab
b17d8087aeff2464be827842051b23fb39bdf5e0 *Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64.cab
d2d19c1887d2075aeb6abd4e986f0ac5bd4f09b7 *Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64_d2d19c18.cabWindows 11, version 23H2 (22631.3520) amd64
Code:
d41c9188d2cda4138840bf499c173a40d72af6cb *Microsoft-Windows-Client-LanguagePack-Package_en-us-amd64-en-us.esd
e7e86fcb2cb686c1944782c274da8042c962983d *Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64.cab
cd1424a3c5a4dc0e5cf36fe0c8d48c5342352ac1 *Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64_cd1424a3.cab
84e2492629838ba9498493fd702888d4fe522874 *Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64.cab
6a520a35555da88b9391d9def6721b7b72c7fee0 *Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64_6a520a35.cab
b6b475c452556c54191d2c269ef5435637345f36 *Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64.cab
da4aed69783b27b0d94e7e23ebce34ba0e428621 *Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64_da4aed69.cab
66d8a6c549aefaffc2792a5a890c397e5bcd78eb *Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64.cab
2e4fc62f9539025000d692040af056656edce522 *Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64_2e4fc62f.cab
b17d8087aeff2464be827842051b23fb39bdf5e0 *Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64.cab
d2d19c1887d2075aeb6abd4e986f0ac5bd4f09b7 *Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64_d2d19c18.cabMy script clearly lists which UpdateID's are used for querying files.
As abbodi will confirm, MS can randomly invalidate some of the oldest UUP sets and you need to substitute the nearest build version that's still available. The script prints the SHA-1 file hashes so you can confirm them against a known reference.