Fix ERROR_MUI_FILE_NOT_LOADED (0x00003b01) Fast

Quick answer

Run sfc /scannow in an elevated Command Prompt, then DISM /Online /Cleanup-Image /RestoreHealth. Reboot. If that doesn't fix it, rebuild the MUI cache by deleting C:\Windows\System32\MUI\cache and reinstalling your language pack.

What's actually going on

This error pops up when you're installing an update, opening a specific app like Windows Mail or Notepad, or sometimes even right after boot. The number 0x00003B01 tells you the resource loader cache—the place Windows stores language-specific files (like English, Spanish, or German strings)—doesn't have the MUI entry it needs. MUI stands for Multilingual User Interface. These files live in C:\Windows\System32\MUI and are loaded on demand.

I've seen this most often after a Windows Update that partially fails, or when someone removed a language pack with third-party cleaner tools like CCleaner. The cache gets corrupted or the MUI file itself gets deleted. The system literally can't find the strings to display your interface, so it throws this error and often crashes the app.

Here's the fix path I use on every help desk ticket for this. Start with the simplest repair, then escalate.

Fix 1: System File Checker and DISM

These two tools check and repair protected system files. DISM fixes the component store first, then SFC fixes files using that store.

1. Open Command Prompt as admin. Click Start, type cmd, right-click Command Prompt, choose Run as administrator. Click Yes on the UAC prompt.
2. Run DISM first. Type this exactly: DISM /Online /Cleanup-Image /RestoreHealth. Press Enter. This scans the Windows image and pulls healthy files from Windows Update. It can take 15-30 minutes. You'll see a progress bar. When it finishes, you'll see either "The restoration completed successfully" or "The source files could not be downloaded." If it fails, you'll need an installation media source, but let's cross that bridge later.
3. After DISM finishes, run SFC. Type sfc /scannow and press Enter. This scans all protected system files and replaces corrupted ones. It takes 10-20 minutes. When it's done, you'll see "Windows Resource Protection found corrupt files and successfully repaired them" or "...did not find any integrity violations."
4. Reboot your computer. Then try the action that threw the error. If it's gone, you're done. If not, move to Fix 2.

Fix 2: Rebuild the MUI Cache

If SFC and DISM didn't work, the MUI cache itself is likely corrupted. We'll delete it and let Windows rebuild it.

1. Open File Explorer. Navigate to C:\Windows\System32\MUI. If you can't see it, you might need to enable hidden files: in File Explorer, click View, then check Hidden items.
2. Look for a folder called cache inside MUI. It might be hidden. Right-click the cache folder and choose Properties. If there's a Read-only checkbox, uncheck it and click Apply. You'll need admin permissions to do this—click Continue when prompted.
3. Delete the cache folder. Select it, press Delete. You'll get a confirmation dialog—click Yes. If it says the folder is in use, close all open apps (especially Notepad, Word, or any language-heavy tools) and try again. If it still won't delete, open Task Manager (Ctrl+Shift+Esc), end any processes named TiWorker.exe or TrustedInstaller.exe, then try again. Be careful—only end those two if they're running.
4. Restart your computer. Windows will recreate the cache folder automatically the next time it loads a MUI file. Test your error.

Fix 3: Reinstall the Language Pack

If the cache rebuild doesn't cut it, the language pack itself is damaged. You'll reinstall it.

1. Open Settings. Press Win+I. Go to Time & Language > Language & region.
2. Find your current display language under Preferred languages. For most English users, that's "English (United States)." Click the three dots next to it, then select Language options.
3. Scroll down to Windows display language and see if it says "Language pack installed." If it does, uninstall it. Click Remove. If it doesn't, skip the uninstall step.
4. Now add the language pack back. Go back to the Language & region page, click Add a language, type "English" (or your language), select the correct variant (like English (United States)), and click Next. Check the box for "Set as my Windows display language" and then click Install. This downloads the pack—takes a few minutes.
5. Sign out and back in when prompted. Test your error again.

Alternative fix for stuck DISM failures

If DISM couldn't download files, you need a Windows installation media as a source. Don't bother with third-party repair tools. They almost never fix this.

1. Create a bootable USB with the same Windows version you're running (Windows 10 22H2, Windows 11 23H2, etc.). Use Microsoft's Media Creation Tool from their site.
2. Open Command Prompt as admin again. Run: DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess. Replace C:\RepairSource\Windows with the actual path to your USB's Windows folder. For example, if your USB is drive D:, use D:\sources\install.wim but you'll need to mount it first with dism /mount-wim /wimfile:D:\sources\install.wim /index:1 /mountdir:C:\Mount. That's advanced—only go there if you're comfortable.

Prevention tip

The real fix is never use registry cleaners or system "optimizers" that claim to remove leftover language packs or cache. I've had three machines this month alone where CCleaner's registry cleaner deleted MUI entries. Windows built-in tools (Disk Cleanup, Storage Sense) don't touch MUI files. Stick with them. Also, keep Windows Update current—Microsoft regularly patches MUI loading issues in cumulative updates.

If you're on Windows 10 or 11 Pro, consider enabling the Windows Feature Experience Pack updates via Settings > Windows Update > Advanced options > Optional updates. These sometimes include MUI fixes that don't come through regular patches.