0XC00B0003

STATUS_MUI_INVALID_RC_CONFIG (0XC00B0003) Fix

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Jul 31, 2026 👁 12 views Windows Errors Beginner
This error means Windows can't read a language resource file. You'll see it when installing updates or language packs. The fix is usually simple.

What This Error Means

Error 0XC00B0003 with the message STATUS_MUI_INVALID_RC_CONFIG shows up when Windows can't load a language resource file correctly. MUI stands for Multilingual User Interface — it's the system that handles language packs and display languages. When one of these files gets corrupted or goes missing, you'll see this error.

Most people hit this during a Windows Update, especially when installing cumulative updates or optional language features. I've also seen it after a botched language pack removal or a system restore that didn't complete properly. The good news: it's almost always fixable without reinstalling Windows.

Fix 1: Run SFC and DISM (Simple, 30 seconds)

This is the first thing you try. It takes about 30 seconds to start and runs in the background. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools scan for corrupted system files and replace them with good copies.

  1. Open Command Prompt as administrator. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This scans your system image and fixes corruption. It might take 10-15 minutes, and you won't see much progress — just a percentage. That's normal.
  3. After DISM finishes, type SFC /SCANNOW and press Enter. SFC checks all protected system files. Wait for it to complete. It'll say "Windows Resource Protection did not find any integrity violations" or tell you it found and fixed files.
  4. Restart your PC when both are done. Try running the update or task that gave you the error. If it's gone, you're all set.

If SFC or DISM fails to run, or if the error persists after this, move to Fix 2.

Fix 2: Check and Repair Language Files (Moderate, 5 minutes)

When SFC and DISM don't cut it, the problem is usually a specific MUI file. You can identify and fix it manually. This takes about 5 minutes.

  1. Open Event Viewer: Press Win+R, type eventvwr.msc, and press Enter.
  2. Go to Windows Logs > System. Look for events with Source "MUI" or Event ID 1001 around the time you saw the error. Double-click any that mention 0XC00B0003. The details will list the exact .mui file that's corrupt — something like C:\Windows\System32\en-US\shell32.dll.mui.
  3. Write down that file path. Now you need to replace it. The safest way: open another Command Prompt as administrator.
  4. Type takeown /f "C:\Windows\System32\en-US\shell32.dll.mui" (replace the path with yours). This gives you ownership of the file.
  5. Then type icacls "C:\Windows\System32\en-US\shell32.dll.mui" /grant Administrators:F to get full control.
  6. Now delete the file: del "C:\Windows\System32\en-US\shell32.dll.mui". Don't worry — Windows will recreate it next time it needs it.
  7. Run SFC /SCANNOW again from the same command prompt. SFC will detect the missing file and restore it from the Windows component store.
  8. Restart your PC.

This worked for a client on Windows 11 22H2 who hit the error after removing a Korean language pack. The event log pointed to C:\Windows\System32\ko-KR\shell32.dll.mui. Once we deleted it and ran SFC, the error disappeared.

Fix 3: Perform a Repair Install (Advanced, 15+ minutes)

If neither of the above fixes the problem, the MUI corruption runs deeper. A repair install (also called an in-place upgrade) reinstalls Windows while keeping your files, apps, and settings. It's the nuclear option, but it's safer than a clean install.

  1. Go to Microsoft's Windows 11 download page (or the Windows 10 page — same process). Download the Media Creation Tool.
  2. Run the tool. Choose "Upgrade this PC now" when prompted.
  3. Click "Keep personal files and apps" — this is the default. Do not change it unless you want to start fresh.
  4. Let the installer run. It downloads updates and replaces all system files, including corrupted MUI files. This takes 30-60 minutes depending on your PC.
  5. When it finishes, your PC restarts. The error should be gone.

I've done this on dozens of machines. It fixes errors that SFC and DISM can't touch. The only downside is time — you need a solid internet connection and about an hour.

What Not to Do

Don't run third-party registry cleaners. They won't fix MUI errors and can break things. Don't delete random .mui files from System32 — only remove the ones identified by Event Viewer. And don't try to manually copy .mui files from another PC unless you know the exact version matches. Mismatched language files can cause more errors.

If none of these fixes work, you might be dealing with a failing hard drive or severe system corruption. Run chkdsk C: /f from an admin command prompt to check for disk errors. If that finds bad sectors, the fix is a new drive and a fresh Windows install.

Related Errors in Windows Errors
0XC022002E Fix STATUS_FWP_CONTEXT_INCOMPATIBLE_WITH_LAYER (0XC022002E) 0X00002083 Fix ERROR_DS_ATT_VAL_ALREADY_EXISTS (0X00002083) 0X00000FD8 Fix PEERDIST_ERROR_SHUTDOWN_IN_PROGRESS (0X00000FD8) 0X0000023B Fixing ERROR_IO_PRIVILEGE_FAILED (0x0000023B) in Windows
STATUS_MUI_INVALID_RC_CONFIG 0XC00B0003 Windows update error language pack error MUI resource file Windows 10 error Windows 11 error SFC scan DISM restore health corrupt language files system file checker

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.