Forum Discussion
Inconsistent Errors using Install-Language
I'm working on a setup script to configure a new W11 installation, and among its tasks is to install en-CA. This was working fine up until recently, when I started getting errors back from the cmdlet... the occurrence of the issue as well as the particular error codes returned are not consistent.
Funny thing, I was actually having similar issues way back when I first started the script. Installing the language would fail 100% of the time, and after some time I found it seemed related specifically to the feature version and base language I was using (24H2 en-GB). I think so, at least, since it's my only explanation. Problem magically disappeared one day, bug presumably patched.
But now, it's happening again. The cmdlet returns "Language pack or features could only be partially installed. Please try again." with varying error codes, and only sometimes... looking up the HRESULTs doesn't give useful information, and checking the Deployment Image Servicing and Management tool and CBS logs only gives the info "install state superseded"... superseded by what, I ask!
Naturally, I don't feel comfortable deploying the script when one of its major tasks has a seemingly random chance to fail, but I'm a bit lost on how to go about this. Anyone know what the deal here might be?
I'm running in a VM on, as mentioned, W11 24H2 en-GB. Command is Install-Language en-CA -AsJob (parallelizing to save time). Issue started happening a few days ago with no changes to the VM or script, and persisted on a brand new VM.
3 Replies
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 https://mcd-breakfast-menu.com . 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.
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>
I have the same issue on Windows 11 23H2...
