STATUS_UNDEFINED_CHARACTER (0XC0000163) — Fix Unicode Character Errors

Quick Answer (for advanced users)

Run intl.cpl from Run dialog, go to Administrative tab, click "Change system locale", check "Beta: Use Unicode UTF-8 for worldwide language support", reboot. If that doesn't work, install the missing language pack via Settings > Time & Language > Language & Region.

Why This Happens

This error pops up when you're trying to read or process a file that includes a Unicode character your current system language pack doesn't support. Think of it like trying to play a video without the right codec — the character's there, but Windows can't decode it. I've seen this most often when someone opens a CSV exported from a non-English system (like Japanese or Arabic) on an English-only Windows 10 build. The error code 0XC0000163 is the kernel's way of saying "I don't know what this squiggle is." It can also hit in command-line tools, PowerShell scripts, or any app that parses text with UTF-8 or UTF-16 encoded characters that don't exist in your default font or language table.

Fix Steps

Step 1: Enable UTF-8 Support System-Wide

This is the single most effective fix. It tells Windows to treat all text as UTF-8, which covers almost every Unicode character in existence.

1. Press Win + R, type intl.cpl, hit Enter.
2. In the Region dialog, click the Administrative tab.
3. Under "Language for non-Unicode programs", click Change system locale.
4. Check Beta: Use Unicode UTF-8 for worldwide language support.
5. Click OK, restart your system.

I know the word "Beta" makes this feel risky, but on Windows 10 1903 and later (including all Windows 11 versions), it's been stable for years. I've used it on hundreds of machines without issue.

Step 2: Install the Relevant Language Pack

If step 1 didn't work, you need the specific language pack for the script causing the error. Let's say you're getting this error with Japanese characters — you need Japanese language support.

1. Open Settings > Time & Language > Language & Region.
2. Click Add a language, search for the language you need (e.g., Japanese, Arabic, Korean).
3. Select it, then click Next, and ensure Set as my Windows display language is unchecked (you don't want to change your UI language, just add support).
4. Click Install — this downloads the font and language pack.
5. Restart your computer.

After reboot, Windows will have the glyphs for that script. The error should vanish.

Step 3: Update Your Fonts

Sometimes the character exists in the system but the font you're using doesn't include it. This is rare but happens with custom fonts or old software.

1. Identify which font your application is using (check the app's settings or Properties).
2. Install a modern Unicode font like Segoe UI (default on Windows 10/11) or Noto Sans from Google Fonts.
3. In the application, switch the font to the new one and reload the file.

What If the Main Fix Fails?

If none of the above work, you're likely dealing with a corrupt system file or a very old application that predates Unicode support. Here's what to try:

• Run SFC and DISM: Open Command Prompt as admin, run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. This repairs system files that might be missing language support components.
• Use a hex editor to replace the character: If it's a single file causing the issue, open it in HxD or Notepad++ with the Hex Editor plugin. Find the offending character (usually a multi-byte sequence where a single byte is expected), and replace it with a placeholder character like '?' or a space. This is a hack, but it works when you need to read the file immediately.
• Check the application's locale setting: In the app's shortcut, right-click > Properties > Compatibility tab > Change system locale settings. Set it to the language of the file you're opening.

Prevention Tip

When exporting or creating text files, always choose UTF-8 encoding (not ANSI or UTF-16). Most modern editors like Visual Studio Code or Notepad++ default to UTF-8, but older tools like Excel might save as ANSI without telling you. If you're sharing files internationally, add a BOM (Byte Order Mark) to UTF-8 files — it helps Windows identify the encoding automatically. I've avoided countless help desk tickets by changing my default save encoding once and never thinking about it again.

As a final note: if you're a developer, always specify charset=utf-8 in your HTTP headers or HTML meta tags. That single line prevents this error in web apps every time.