: Since it relies on external UUP dump servers, changes to Microsoft's APIs can cause specific versions of the script to become "retired" or "out of date," requiring users to download the latest update from the NTLite forum thread .
If you've integrated language packs but don't see them available during Windows Setup, the registry key BlockCleanupOfUnusedPreinstalledLangPacks may be preventing their display. This is normal behavior—the languages remain installed and can be activated using the PowerShell commands mentioned earlier.
It helps in finding language packs for older or specific builds of Windows 10 and 11 that might not be easily accessible through the standard UI. w10 11langpack.ps1
Are you looking to for a single PC, or are you building a custom Windows image for multiple devices? Managing Windows 11 languages and region settings (Part 1)
# 3. Add to the user's preferred language list to make it visible in Settings $UserList = Get-WinUserLanguageList : Since it relies on external UUP dump
In enterprise environments where IT departments need to "image" or set up hundreds of machines, this script can be integrated into deployment sequences (like MDT or SCCM) to ensure regional settings are uniform across a fleet. Cleanup and Optimization:
: The modern AppX package for UI translations. It helps in finding language packs for older
Get-WindowsPackage -Online | Where-Object $_.PackageName -like "*LanguagePack*" -and $_.PackageName -notlike "*en-us*" | Remove-WindowsPackage -Online -NoRestart
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process 2. Running the Script
To ensure the language displays perfectly—including handwriting recognition, Text-to-Speech (TTS), and regional spell-checking—you must also install the Features on Demand .cab files that the script downloads alongside the base language pack. You can apply these using the same Add-WindowsPackage command as shown above. Best Practices and Troubleshooting
Using NTLite: