153

Currently I'm running Windows 7 x64 and usually I want all console tools to work with UTF-8 rather than with default code page 850.

Running chcp 65001 in the command prompt prior to use of any tools helps but is there any way to set is as default code page?

Update:

Changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\OEMCP value to 65001 appear to make the system unable to boot in my case.

Proposed change of HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\Autorun to @chcp 65001>nul served just well for my purpose. (thanks to Ole_Brun)

  • 1
    Note the purposed solution could break Windows' find.exe (which would cause problems with Android SDK build): superuser.com/questions/176737/… – J Rao Jan 18 '15 at 5:24
  • 1
    Using the UTF-8 code-page also breaks the more command (it gives the misleading error message Not enough memory.) Opening the command-prompt with the /U switch does not help. – Synetech Mar 7 '16 at 22:00
  • 13
    The Windows console is riddled with bugs when the encoding is set to an unsupported multi-byte code page like 65001. Any software using the output counts of the Win32 WriteFile/ReadFile APIs will get the wrong results and consequently stuff build on that like the MSVCRT's implementation of the stdlib will produce mangled/repeated output and hang on input when confronted with non-ASCII. Until MS get around to fixing it — and it has been decades with no sign of that happening — globally changing console code page to 65001 is an extraordinarily bad idea. – bobince Oct 14 '16 at 8:51
  • 3
    Any use of the A versions of Windows functions is broken. All code needs to be ported to use the W versions. – Demi Apr 7 '17 at 14:42
  • 1
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\OEMCP is used as fallback for non-unicode (non-utf) environments, obviously you try to force it to a 'unicode', as you see it is controversal by definition. Windows hangs probably because some system stuff on boot depends on non-unicode charset to work. – venimus Aug 23 '17 at 15:00
109

To change the codepage for the console only, do the following:

  1. Start -> Run -> regedit
  2. Go to [HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\Autorun]
  3. Change the value to @chcp 65001>nul

If Autorun is not present, you can add a New String

| improve this answer | |
  • 1
    @Regent In the question, the registry value you mentioned that worked for you is @chcp 65001>nul, while in this accepted answer, it is chcp 65001. What are the differences between the two? – galacticninja Mar 16 '15 at 8:41
  • 9
    @galacticninja simply putting chcp 65001 will cause every opened command prompt to print 'Active code page: 65001' whilst @chcp 65001>nul will prevent any output. – Regent Mar 26 '15 at 15:51
  • 8
    Autorun is not present for me under Windows 8.1. – kleinfreund May 10 '15 at 9:09
  • 4
    @kleinfreund @Luke: if Autorun is not present, you can add a New String Value with the contents of @chcp 65001>nul – Dacto Oct 23 '18 at 20:45
  • 2
    @Dr.jacky Not sure exactly what they mean with dangerous. I've just answered the question of the OP. Whether you should do it or not is a different question. I believe there might be some issues with Python, so you may want to check that out before setting codepage to 65001 at least. – Nils Magne Lunde Dec 18 '18 at 6:59
48

Personally, I don't like changing the registry. This can cause a lot of problems. I created a batch file:

@ECHO OFF
REM change CHCP to UTF-8
CHCP 65001
CLS

I saved at C:\Windows\System32 as switch.bat.

I created a link for cmd.exe on the Desktop.

In the properties of the cmd shortcut, changed the destination to: C:\Windows\System32\cmd.exe /k switch

Voilá, when I need to type in UTF-8, I use this link.

| improve this answer | |
  • 8
    Note that it will print Active code page: 65001 to stdout. So if you are doing something like CHCP 65001 && mycommand.exe then you'll get the codepage printed out at the start. You need to CHCP 65001 >nul && mycommand.exe – frumbert Jun 12 '15 at 5:33
38

Edit the Registry:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage]
"OEMCP"="65001"

Then restart. With this fix, if you are using Consolas font, it seems to lock PowerShell into a small font size. cmd.exe still works fine. As a workaround, you can use Lucida Console, or I switched to Cascadia Mono:

https://github.com/microsoft/cascadia-code

| improve this answer | |
  • The thing is, it only works for CMD, but not for console by itself. – AnrDaemon Sep 6 '19 at 9:10
25

In the 1809 build of Windows 10 I've managed to permanently solve this by going to the system's Language settings, selecting Administrative language settings, clicking Change system locale... and checking the Beta: Use Unicode UTF-8 for worldwide language support box and then restarting my pc.

This way it applies to all applications, even those ones that I don't start from a command prompt!
(Which was necessary for me, since I was trying to edit Agda code from Atom.)

| improve this answer | |
  • 3
    Thanks, it solved my issue! – Jabba Feb 22 at 10:09
  • 3
    This is the best and correct answer for modern Windows. – CAD97 Apr 1 at 21:06
  • 1
    This certainly did the job for me. However, it had a nasty side-effect: QuickBooks (I used 2017 Professional) suddenly failed to recognize any of my account names, since they contain Unicode characters, and this setting really messed things up with that software. Just a heads-up... – Mike Allen Apr 15 at 18:42
  • 1
    Hmm, the system must have got used to a stripped version of those names or something similar. Never thought this would break stuff while fixing other things, but I guess you can never make a change without messing up something. 🙃 (xkcd.com/1172) Thanks for the information, I hope that it doesn't happen to many other people, but at least now they can be prepared. – Isti115 Apr 15 at 19:24
6

This can be done by creating a PowerShell profile and adding the command "chcp 65001 >$null" to it:

PS> Set-ExecutionPolicy RemoteSigned
PS> New-Item -Path $Profile -ItemType file -Force
PS> notepad $Profile

This doesn't require editing the registry and, unlike editing a shortcut, will work if PowerShell is started in a specific folder using the Windows Explorer context menu.

| improve this answer | |
  • 1
    @PimpJuiceIT, no.. see the first line of this answer. – Dacto Dec 14 '18 at 17:21
5

The command to change the codepage is chcp <codepage>. Example: chcp 1252. You should type it in a Powershell window. To avoid the hassle of typing it everytime (if you always have to change the codepage), you may append it to the program's command line. To do so, follow these steps:

  1. Right-click the Powershell icon on Start menu and choose "More" > "Open file Location".
  2. Right-click the Powershell shortcut and select "Properties".
  3. Add the following to the end of the "Target" command line: -NoExit -Command "chcp 1252"

Be happy. Don't fuss with Windows Registry unless you have no other option.

| improve this answer | |
  • This one worked perfectly for me. -NoExit -Command "chcp 1252 > null" also omits the message about the selected code page in the beginning. – CodeMonkey Aug 3 '18 at 8:53
2

If you're using ConEmu then:

  1. Open up Settings from the upper right menu
  2. Go to Startup -> Environment
  3. Add chcp 65001 on a new line.
  4. Click "Save Settings".
  5. Close ConEmu and re-open it

enter image description here

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.