Fix ERROR_MUI_INVALID_FILE (0X00003AFD) in Windows

You're here because you saw error 0X00003AFD.

It usually pops up when launching an app or Windows feature, especially after a language pack update, a faulty Windows Update, or a third-party tool that tried to strip out languages. The system can't load the MUI (Multilingual User Interface) file because it failed some internal checksum or signature check. Annoying, but fixable in under ten minutes.

The Fast Fix: Replace the Corrupt MUI File

Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)).
Run this DISM command to restore the MUI file for your current system language:
```
DISM /Online /Add-Capability /CapabilityName:Language.Basic~~~en-US~0.0.1.0 /Source:C:\Windows\WinSxS /LimitAccess
```
Replace en-US with your system language code (e.g., de-DE, fr-FR, ja-JP).
Wait for it to finish (takes 1–3 minutes usually). Reboot if prompted.
If that doesn't clear it, run SFC next:
```
sfc /scannow
```
This checks and replaces corrupt system files, including MUI files in C:\Windows\System32\.
Reboot again. Test the app or feature that threw the error.

Why This Works

The DISM command pulls a fresh copy of the language pack from the WinSxS store — Windows's component backup. The reason step 2 works is that WinSxS stores every original file version, including validated MUI files. When a language pack gets corrupted (common after a partial Windows Update failure), DISM swaps it out. SFC then fixes any remaining damage to the MUI file's hash or metadata. The error code 0X00003AFD specifically means the MUI file's signature didn't match what the resource loader expected — this restores the original, signed version.

Less Common Variations & Their Fixes

Third-Party Language Bloatware

If you've used a tool like lpksetup or a cleaner like CCleaner to remove unwanted languages, you might have deleted the MUI file entirely. In that case, DISM won't find a replacement in WinSxS either. Fix: Download the correct language pack ISO from Microsoft's official site and install it manually with lpksetup /i.

Permissions on the MUI Directory

Sometimes the MUI file exists but the current user can't read it. Check the Security tab of C:\Windows\System32\MUI (or System32\??-??\ where ??-?? is your language code). If SYSTEM or TrustedInstaller is the only owner, take ownership and grant Users read permission. Reboot and test.

Corrupt User Profile

Rare, but if the error only happens for one user account, the profile's locale settings might be hosed. Create a new local admin account and see if the error disappears. If it does, migrate your data over — the old profile's NTUSER.DAT has corrupt language preferences.

Prevention

Don't use third-party language removers. They often delete MUI files without proper cleanup. If you must remove a language, use lpksetup /u from an elevated prompt.
Keep Windows Update healthy. A failed update is the #1 cause of MUI corruption. Run DISM /Online /Cleanup-Image /RestoreHealth monthly if you're paranoid.
Don't manually delete files in System32\MUI. You can break every localized app. If you need to free space, use Disk Cleanup's Windows Update Cleanup instead.
Test after installing language packs. If you add a new language, immediately launch a couple of built-in apps like Notepad or Calculator. If they throw 0X00003AFD, you caught it early.

This error is Windows's way of saying "this MUI file looks tampered with or corrupted." Trust the built-in repair tools — they're written by the same people who wrote the MUI loader. Third-party fixes almost always make it worse.