How to fix Error 1113 on Windows 11

by

Windows 11 Error 1113: “No Mapping for the Unicode Character Exists in the Target Multi-Byte Code Page”

Why This Error Happens

This error occurs when Windows attempts to convert a Unicode character to a specific multi-byte code page (like ANSI or a legacy locale-specific encoding), but the character has no equivalent representation in that target encoding. It commonly arises with file names, folder paths, or document content containing special characters, emojis, or non-Latin scripts (such as Cyrillic, Chinese, or Arabic) when the system’s regional/language settings don’t support them. This is frequently triggered by mismatched “Language for non-Unicode programs” settings, corrupted file system metadata, or legacy applications that rely on ANSI code pages instead of full Unicode (UTF-8) support.

Step-by-Step Resolution Guide

  1. Enable UTF-8 System-Wide Language Support
  • Go to Settings > Time & Language > Language & Region.
  • Click Administrative language settings (opens Region dialog).
  • Under the Administrative tab, click Change system locale.
  • Check the box “Beta: Use Unicode UTF-8 for worldwide language support”.
  • Click OK and restart your PC.
  1. Match the Non-Unicode Program Language to the Source Content
  • In the same Region dialog (Administrative tab), click Change system locale.
  • From the dropdown, select the language matching the character set causing the issue (e.g., Chinese Simplified if the error involves Chinese file names).
  • Restart the computer for changes to take effect.
  1. Rename or Move the Problematic File/Folder
  • Identify the specific file, folder, or registry key path triggering the error (often visible in the error dialog or application log).
  • Use PowerShell to rename it using only ASCII characters:
    powershell
    Rename-Item -Path "C:\Path\To\File" -NewName "SafeFileName.txt"
  • Avoid special Unicode characters (emojis, accented letters, non-Latin scripts) in critical system or application paths.
  1. Update or Patch the Affected Application
  • Check for updates to the specific software throwing the error (via Settings > Windows Update or the vendor’s site), since many older apps have since been patched for full UTF-8 compatibility.
  • If using a script or batch file, ensure it explicitly declares UTF-8 encoding (e.g., chcp 65001 in Command Prompt before execution).
  1. Repair Corrupted System Files
  • Open Command Prompt as Administrator and run:

    sfc /scannow
  • Follow with:

    DISM /Online /Cleanup-Image /RestoreHealth
  • Restart once complete.

Alternative or Verification Steps

  • Verify the fix: Re-run the action that originally triggered Error 1113 (e.g., open the file, run the script, or execute the application) and confirm no error dialog appears.
  • Alternative workaround: If UTF-8 system-wide settings cause compatibility issues with other legacy software, revert the locale change and instead use a dedicated Unicode-aware tool (e.g., 7-Zip instead of legacy compression tools) to handle the specific file or path causing the conflict.