STATUS_MUI_INVALID_LOCALE_NAME (0XC00B0004) Fix: Bad Culture Name

What Actually Triggers This Error

You'll see STATUS_MUI_INVALID_LOCALE_NAME (0XC00B0004) when an application or Windows component can't parse a locale name in its RC manifest. I've seen this most often after a Windows Update that changed the system language settings, or after manually messing with language packs. The manifest expects something like "en-US" but gets garbage like "en_US" or an empty string. Had a client last week whose QuickBooks install went sideways after a feature update—same error.

Quick Fix (30 seconds): Check Your System Locale

Before you dive into registry edits, just verify Windows isn't confused about its own language.

1. Press Win + R, type intl.cpl, hit Enter.
2. Under the Administrative tab, click Copy settings.
3. Check the box Welcome screen and system accounts, then click OK.
4. Restart the computer. If the error was caused by a mismatch between user and system locale, this syncs them up and you're done.

If that doesn't help, move on.

Moderate Fix (5 minutes): Clean Up Language Pack Registry Keys

This is the sweet spot. Most of the time, the registry has a leftover or broken language pack entry.

1. Press Win + R, type regedit, hit Enter.
2. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MUI\UILanguages
3. You'll see a list of language codes (like en-US, de-DE). If you see any that have weird characters, extra dots, or are missing altogether, delete the bad key. Caution: only delete what's obviously broken. If safe, export the key first.
4. Close Regedit and restart.

Had a scenario where a user's system had en-US and en-US.old. Deleting the stale one fixed it instantly.

Advanced Fix (15+ minutes): Rebuild the MUI Cache

If the registry looked clean, the MUI cache files might be corrupted. This happens when Windows Update partially fails during a language pack install.

1. Open Command Prompt as Administrator.
2. Run this command to check the current system language:
   

   dism /online /get-intl

3. If it shows mismatched values, force a language reset. Let's assume your system should be en-US. Run:
   

   dism /online /set-uilang:en-US
   bcdedit /set {current} locale en-US

4. Next, reset the MUI cache. Delete the contents of C:\Windows\System32\en-US (or your language folder) except the .mui files? No—that's risky. Instead, run:
   

   sfc /scannow

   Then reboot. SFC will replace any corrupted MUI files.

5. If that still fails, do a repair install of the app causing the error. Right-click the installer, select Repair. This forces the manifest to be rewritten.

Last Resort: Restore Missing Manifest

If you're still seeing the error, the app's RC manifest itself is broken. For example, a developer might have shipped a manifest with culture="*" or a blank. You'll need to either patch it (advanced) or reinstall the app fresh. Don't waste time editing the binary—just grab a clean copy.

Preventing It

• Never manually delete language packs from Windows. Use the Settings app.
• If you're a developer, validate your manifest's culture attribute before packing. Wrong dashes cause this.

That's it. Start with the locale copy, then the registry, then MUI rebuild. Nine times out of ten, one of those gets you back to work.