[GH-ISSUE #129] [BUG] The cmd.exe launched by the launcher may fail to display wide characters correctly because the code page (chcp) is not set #67

Open
opened 2026-10-15 18:06:43 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @HaoJun0823 on GitHub (Mar 25, 2026).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/129

Environment

🪟 Windows

System

Windows 11 25H2

Describe the problem

When using this convenient tool on Windows, I found that "Start SillyTavern" launches another batch file (.bat) via the call command. This causes Windows to call a new cmd.exe launcher instead of the Windows 11 Terminal.

For me, the new cmd cannot display Chinese characters correctly because it lacks a code page (chcp).

My solution was to simply add "chcp 65001 > nul" to each batch script, which sets the batch's code page to UTF-8.

Another solution is to create a new string entry named "Autorun" in the registry (regedit.exe) under "HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor" and set its value to "chcp 65001 > nul". This also solves the problem, but it's a permanent change for all cmd scripts.

I did not submit a pull request for the following reasons:

  1. I am unsure if this is an isolated case I encountered.

  2. I am unsure if this issue applies to other multi-language systems.

  3. I'm not sure if this issue is limited to Windows 11.

Ultimately, I think submitting an issue would be good, and I believe a solution to this minor bug could be included in the documentation.

Additional info

No response

Please tick the boxes

Originally created by @HaoJun0823 on GitHub (Mar 25, 2026). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/129 ### Environment 🪟 Windows ### System Windows 11 25H2 ### Describe the problem When using this convenient tool on Windows, I found that "Start SillyTavern" launches another batch file (.bat) via the `call` command. This causes Windows to call a new cmd.exe launcher instead of the Windows 11 Terminal. For me, the new cmd cannot display Chinese characters correctly because it lacks a code page (chcp). My solution was to simply add "chcp 65001 > nul" to each batch script, which sets the batch's code page to UTF-8. Another solution is to create a new string entry named "Autorun" in the registry (regedit.exe) under "HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor" and set its value to "chcp 65001 > nul". This also solves the problem, but it's a permanent change for all cmd scripts. I did not submit a pull request for the following reasons: 1. I am unsure if this is an isolated case I encountered. 2. I am unsure if this issue applies to other multi-language systems. 3. I'm not sure if this issue is limited to Windows 11. Ultimately, I think submitting an issue would be good, and I believe a solution to this minor bug could be included in the documentation. ### Additional info _No response_ ### Please tick the boxes - [x] I have explained the issue clearly, and I included all relevant info - [x] I have checked that this [issue hasn't already been raised](https://github.com/SillyTavern/SillyTavern/issues?q=is%3Aissue) - [x] I have checked the [docs](https://docs.sillytavern.app/) ![important](https://img.shields.io/badge/Important!-F6094E)
Sign in to join this conversation.
No description provided.