Fix STATUS_RESOURCE_LANG_NOT_FOUND (0XC0000204)

Quick answer: Run DISM /RestoreHealth and SFC /ScanNow from an admin Command Prompt. That fixes language resource corruption in most cases.

What causes 0XC0000204?

Windows uses resource files that contain text, icons, and other UI elements for each language you have installed. The error code STATUS_RESOURCE_LANG_NOT_FOUND (0XC0000204) pops up when an application or system component tries to load a language-specific resource — like a string or dialog box — but the expected language ID isn't present in the binary file. This happens most often after a failed Windows Update that installed a language pack update, or after someone manually removed a language pack without uninstalling it properly. I've also seen it on systems where a third-party antivirus quarantined a system DLL that was tied to a language resource.

The crummy part: this error can show up in different places. You might see it during boot, when opening Control Panel, or when launching a specific app like Notepad or Snipping Tool. The core issue is almost always a corrupted or mismatched file in the system's language resources.

Step-by-step fix

Step 1: Run DISM to repair the system image

Press Windows Key + X and choose Windows Terminal (Admin) or Command Prompt (Admin).
Type or paste this command then press Enter:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Wait. This can take 10 to 30 minutes. You'll see a progress bar. Don't close the window.
When it finishes, you should see "The restore operation completed successfully." If you get an error about a missing source, you can specify a Windows installation ISO with the /Source parameter, but for most corrupted language resources, the online repair works fine.

Step 2: Run SFC to fix individual system files

In the same admin Command Prompt, run:
```
sfc /scannow
```
Let it complete. It'll check every protected system file and replace any bad ones with cached copies.
After it finishes, you'll see either "Windows Resource Protection found corrupt files and successfully repaired them" or a message saying it couldn't repair some—but DISM usually handles the language stuff first, so SFC is the cleanup.

Step 3: Restart and test

Close the command window and restart your PC.
Try whatever was giving you the 0XC0000204 error. If it's gone, you're done.

Alternative fixes if the main one fails

Fix 2: Remove and re-add your language pack

If DISM and SFC didn't do it, the language pack itself might be borked. Here's how to swap it out:

Go to Settings > Time & Language > Language & Region (Windows 11) or Language (Windows 10).
Under Preferred languages, find your current language (like English United States) and click the three dots next to it, then choose Language options.
Scroll down to Windows display language. Note the pack that's installed. Then click Remove on that pack.
Now click Add a language, search for the same language, and install the display language pack.
After it installs, you might need to sign out and back in, or restart.

Fix 3: Use system restore or a repair install

If you're still stuck, you can roll back to a restore point from before the error started. Type rstrui in the Run dialog (Win+R) and follow the prompts. If you don't have a restore point, your next move is an in-place upgrade repair: download the Windows 11 or 10 Media Creation Tool, run it, and choose Upgrade this PC now. This keeps your files and apps but replaces all system files, including language resources. It's a pain but it works.

Prevention tip

Don't manually delete language packs or mess with C:\Windows\WinSxS folder contents. Windows builds those as hard links, and yanking one can cause this error weeks later when an update tries to use it. If you need to remove a language pack, always go through Settings > Language & Region and use the proper Remove option. Also, keep Windows Update enabled — those cumulative updates often contain fixes for resource corruption that DISM alone can't patch.