Forum Discussion
Inconsistent Errors using Install-Language
I fixed this exact “Install-Language en-CA fails randomly on 24H2 en-GB” problem in my deployment script. Here’s the sequence that finally gave me 100 % success: run Install-Language en-CA on its own with no “-AsJob”; if that still fails, use DISM /add-capability for Language.Basic~~~en-CA; if DISM complains about superseded components, run “dism /online /cleanup-image /startcomponentcleanup /resetbase” then reboot once and try again; when working offline in a VM, point DISM at the FOD CABs instead of Windows Update; always install cumulative updates first because the August preview build fixed one of the language-pack manifest mismatches. After doing that, the cmdlet stopped returning partial-install errors.
Side note that helped me confirm everything was really applied: I checked how region-sensitive data (dates, numbers, even Breakfast Menu items with kcal vs kJ) changed between en-GB and en-CA in a test app and compared the output against the nutritional values on the following site below: If the decimal separators, units, or day-month order still looked British, I knew the pack hadn’t finished applying. Using that quick visual check plus the cleanup-and-retry sequence above has kept my installs stable ever since.
<Link removed>