Change Windows 11 Command Prompt Console Language

You can change the Command Prompt language in Windows 11 by modifying the console code page and regional settings rather than changing the entire operating system language. This process involves setting a specific code page, such as UTF-8 or OEM characters, to ensure text renders correctly in Polish, Japanese, or other non-Latin scripts. By adjusting these low-level console properties, you resolve character encoding issues without reinstalling Windows or altering your primary display language preferences.

Understanding Console Code Pages

The Command Prompt relies on code pages to map numeric character values to visible glyphs. When the active code page does not match the encoding of the text being displayed, you will see garbled symbols or question marks instead of letters like "ą" for Polish or Kanji for Japanese. The most common solution is to switch the console to a Unicode-aware code page or the appropriate OEM code page for your target language. To check your current code page, open cmd.exe and type chcp. The output will show something like Active code page: 437 (US) or 65001 (UTF-8). If you are seeing incorrect characters, this number likely needs to be changed. For Japanese users, code page 932 is standard. For Western European languages like Polish, code page 852 or 1250 are often used, though UTF-8 (65001) is increasingly preferred for compatibility.

Temporarily Changing the Language

For immediate testing, you can change the code page for the current session only. This method is useful if you need to run a script with specific encoding requirements but do not want to alter system-wide settings.

1. Open the Start menu and search for Command Prompt.
2. Right-click the result and select Run as administrator to ensure full privileges.
3. Type the following command and press Enter:

chcp 65001

This sets the active code page to UTF-8. You can verify the change by running chcp again; it should now report Active code page: 65001. Any subsequent commands executed in this window will use UTF-8 encoding. Note that this change resets when you close the window. If you need a different language, replace 65001 with the appropriate code page number, such as 932 for Japanese.

Making the Change Permanent via Registry

To apply the code page change permanently for all new Command Prompt windows, you must modify the Windows Registry. This approach ensures that every time you launch cmd.exe, it initializes with the correct encoding. Be cautious when editing the registry, as incorrect changes can affect system stability. Always back up your registry before proceeding.

1. Press Win + R, type regedit, and press Enter.
2. Navigate to the following path:

HKEY_CURRENT_USER\Console

• If the Console key does not exist, right-click the HKEY_CURRENT_USER folder, select New > Key, and name it Console.
• Inside the Console key, look for a DWORD value named CodePage. If it does not exist, right-click in the right pane, select New > DWORD (32-bit) Value, and name it CodePage.
• Double-click CodePage and set its value data to 65001 (for decimal). Ensure the Base is set to Decimal.

After saving the registry entry, close the Registry Editor. Open a new Command Prompt window; it should now default to the specified code page. This method is particularly effective for users who frequently work with international character sets. For more information on managing language settings post-setup, you might find How to Change the Pre-Installed Windows 11 Language Permanently (Post-Setup) helpful for broader localization tasks.

Configuring Font Support

Even with the correct code page, the Command Prompt may fail to display certain characters if the selected font lacks the necessary glyphs. Windows uses a limited set of fonts for the console, and not all support complex scripts like Japanese Kanji or Polish diacritics.

1. Open Command Prompt and right-click the title bar.
2. Select Properties.
3. Go to the Font tab.
4. Choose a font that supports your target language. For universal support, Courier New or Consolas are safe bets, but for Japanese, MS Gothic or Yu Gothic are better options.
5. Click OK and apply the changes.

If you still encounter missing characters, consider switching to Windows Terminal, which offers superior font rendering and configuration options compared to the legacy Command Prompt.

Troubleshooting Encoding Issues

Sometimes, even after setting the code page and font, files created or read by the Command Prompt may have encoding mismatches. This often happens when piping output from one command to another or redirecting to a file. To mitigate this, ensure that any scripts or batch files you create are saved in the same encoding as the active code page. If you experience issues with directory listings or file names containing special characters, refer to Troubleshooting 'dir' Command Prompt Issues for deeper diagnostic steps. Additionally, verifying your keyboard layout does not interfere with input methods is crucial. As noted in guides about managing multiple languages, keeping your input settings streamlined can prevent unexpected behavior. See Windows 10: Leave Only One Language per One Keyboard Layout for best practices on input management.

Frequently Asked Questions

Why do I see question marks instead of Polish characters?

This occurs because the active code page does not support the specific glyph for the character you are typing. Switching the code page to 852 or 65001 using the chcp command typically resolves this issue immediately.

Can I change the Command Prompt language to Chinese without changing Windows?

Yes, you can set the code page to 936 (Simplified Chinese) or 950 (Traditional Chinese) via the registry or chcp command. However, you must also ensure the console font supports CJK characters, such as SimSun or Microsoft YaHei. For more details on switching languages, check out How to Switch Language from English to Chinese in Windows.

Does changing the code page affect PowerShell?

No, PowerShell uses its own encoding settings separate from the legacy Command Prompt. While they share some underlying system configurations, changing the Console registry key primarily impacts cmd.exe. PowerShell handles UTF-8 natively in newer versions, so explicit code page changes are rarely needed there.

What is the safest code page for general international use?

Code page 65001 (UTF-8) is the safest choice for modern applications. It supports virtually all characters from all languages and is becoming the standard for interoperability between different tools and systems.

Will reverting the registry change break my system?

No, deleting or resetting the CodePage DWORD value in the HKEY_CURRENT_USER\Console key simply returns the Command Prompt to its default behavior. Your system files and applications remain unaffected by this user-level console setting.