Fix ERROR_MUI_FILE_NOT_FOUND (0x00003AFC) in Windows

The 30-Second Fix: Run SFC in Safe Mode

This catches corrupted system files that break MUI resources. Boot into Safe Mode first—don't skip that. In normal mode, SFC often misses files in use.

Hold Shift and click Restart from the Start menu.
Go to Troubleshoot > Advanced Options > Startup Settings > Restart.
Press 4 or F4 for Safe Mode.
Open Command Prompt as admin.

sfc /scannow

Let it finish. It'll take maybe 5 minutes. If it says "Windows Resource Protection found corrupt files but was unable to fix some of them," move to the moderate fix.

When this works: If the error popped right after a Windows Update or driver install. SFC replaces the MUI file from the local cache.

The 5-Minute Fix: DISM to Repair the Component Store

SFC relies on a healthy component store. If that store is broken, SFC can't do its job. DISM fixes the store itself. Still in Safe Mode? Good. If not, reboot into Safe Mode again.

Run these three commands in order. Don't skip the /RestoreHealth one—that's the real fix.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

The last command might need an internet connection. It'll pull fresh files from Windows Update. If your network is sketchy, use a local source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with the path to a Windows installation media or an ISO you've mounted.

After DISM finishes, run SFC again. Yes, again. DISM restores the files SFC needs. Then reboot normally.

When this works: If the error shows up in multiple apps, not just one. That's a sign the whole language subsystem is busted.

The 15-Minute Fix: Rebuild Language Packs Manually

Sometimes DISM can't fix this because the language pack itself is missing or corrupted. You'll need to reinstall it. This is the nuclear option—skip the first two steps at your own risk.

Step 1: Check your current language settings

DISM /Online /Get-Intl

Note the System UI Language and Installed Language(s). You'll need the exact language tag (like en-US or de-DE).

Step 2: Download the language pack LP.cab

For Windows 10 20H2 and later, or Windows 11, grab the LP.cab from Microsoft's catalog. For Windows 10 version 2004 and older, you need a full cumulative update.

Easiest way for modern Windows:

Go to Settings > Time & Language > Language & Region.
Click Add a language for your current language, then Options.
Install the language pack. If it's already installed, remove and reinstall it.

For offline install, download the LP.cab from Microsoft's Language Pack page.

Step 3: Install the language pack via DISM

DISM /Online /Add-Package /PackagePath:C:\Path\To\LP.cab

Reboot after install.

Step 4: Force a rebuild of MUI resources

This is the step most guides miss. Run this command for the affected app:

mt.exe -update -inputresource:C:\Path\To\App.exe -outputresource:C:\Path\To\App.exe

You'll need the Windows SDK or Visual Studio Build Tools installed for mt.exe. Or just use the free Resource Tuner tool to re-add the MUI file manually.

When this works: If the error only happens with a single legacy app that installed its own language files. Windows updates can overwrite them, and this restores the app's specific MUI.

Still Broken? Check the Event Log

Open Event Viewer (eventvwr.msc) and look under Windows Logs > Application. Filter by Event ID 1000 or 1026. The log shows exactly which MUI file is missing (e.g., shell32.dll.mui). That tells you which component is busted.

Then you can target that specific file. Copy it from a working machine of the same Windows version. Put it in C:\Windows\System32\<language-code>.

Pro tip: Don't copy MUI files between different Windows builds (e.g., 21H2 to 22H2). They're version-specific. You'll cause more errors.

"The MUI error is almost always a botched update or a third-party language pack. The built-in tools fix it 95% of the time. The other 5% is an app that installed its own MUI and needs a reinstall."

If none of this works, your last resort is a Windows repair install using the Media Creation Tool. That keeps your files but replaces all system files. Takes about an hour but is bulletproof.