Fix 0x00003B03: UI language install fails on Windows
Windows throws 0x00003B03 when a language pack isn't fully installed or the MUI cache is corrupt. Here's the fix order: quick check, then reinstall, then nuke the cache.
What's actually happening here
The error 0x00003B03 (ERROR_MUI_INTLSETTINGS_UILANG_NOT_INSTALLED) means Windows thinks the language pack files are present, but the Multilingual User Interface (MUI) subsystem can't find a required resource. This usually happens after a failed Windows Update, a botched manual language pack installation, or when you try to set a language that was partially removed. I've seen this on Windows 10 22H2 and Windows 11 23H2, especially after using third-party language switchers.
Fix 1 — 30 seconds: Verify the language is actually installed
Don't trust the Settings app. It lies sometimes. Open PowerShell as admin and run:
Get-WinUserLanguageListLook for the LanguageTag of the language you're trying to set. If it's there but the Status shows NotInstalled, you've found the problem. The OS has a stale registry entry. Run this to force a reinstall:
Install-Language -Language <LanguageTag>Replace <LanguageTag> with something like de-DE, fr-FR, ja-JP, etc. This grabs the correct language pack from Windows Update and fixes the missing resources. Most users stop here and it works.
Fix 2 — 5 minutes: Remove and reinstall the language pack properly
If the PowerShell command above fails or the language still shows as not installed, the cached pack files are corrupt. Here's the proper way to reset it:
- Open Settings > Time & Language > Language & region.
- Under Preferred languages, find the problem language.
- Click the three dots next to it and select Remove.
- Reboot. Yes, really. This clears the in-memory MUI cache.
- Go back to Settings > Language & region, click Add a language, search for it, and install it fresh.
The reboot step is critical. If you skip it, Windows reuses the same broken cache files and you'll get the same error. The reason step 4 works is that Lpksetup.exe (the language pack installer) doesn't flush its internal state until the next boot after a removal.
Fix 3 — 15+ minutes: Nuke the cached MUI resources manually
This is for stubborn cases where the above fixes don't help—usually after a failed feature update. You're going into the system's internal language storage.
Step 1: Take ownership of the MUI cache folder
Open an elevated Command Prompt (not PowerShell for this part—trust me, takeown behaves differently in PowerShell).
takeown /f "C:\Windows\System32\mui\dispspec\*" /r /d y
icacls "C:\Windows\System32\mui\dispspec" /grant Administrators:F /tThis gives you full control over the display spec files that map language IDs to resource files.
Step 2: Delete the broken language folder
Inside C:\Windows\System32\mui\dispspec, find the folder for your language (e.g., 0409 for en-US, 0407 for de-DE). Delete that folder. Do not delete the whole dispspec folder—only the subfolder for the broken language.
Step 3: Rebuild the MUI registry keys
Still in the admin Command Prompt, run:
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\MUI\UILanguages" /v <LanguageTag> /f
reg delete "HKCU\Control Panel\Desktop\MuiCached\<LanguageTag>" /fReplace <LanguageTag> with the actual tag, like de-DE. This wipes the registry entries that point to the now-deleted cache folder.
Step 4: Reinstall the language pack from scratch
lpksetup /i /p "C:\path\to\your\language\pack.cab"If you don't have a standalone CAB file, use this to pull it from Windows Update:
dism /online /Add-Package /PackagePath:<path>But honestly, the easiest path is to let Windows Update handle it. Go to Settings > Windows Update > Check for updates, then retry adding the language. The update mechanism knows how to repair the MUI subsystem.
When you should just give up and use a system restore
If you've tried all three fixes and still get 0x00003B03, the underlying issue is almost always a corrupt component store that affects all MUI operations. Run sfc /scannow from an admin Command Prompt, then dism /online /cleanup-image /restorehealth. If that doesn't fix it, you're looking at a repair install or reset. The language pack system is deeply tied to the servicing stack—once it breaks, sometimes the only reliable fix is a clean slate.
One final note: don't waste time with third-party language pack installers. They always cause this error eventually. The Windows-native path via Settings or DISM is the only one that keeps the MUI registry and cache in sync.
Was this solution helpful?