mirror of
https://github.com/SillyTavern/SillyTavern-Launcher.git
synced 2026-11-05 00:27:39 +00:00
[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
Labels
No labels
🚏 Awaiting User Response
🐛Bug
🐛Bug
🐛Bug
🦄 Feature Request
✅ Fixed
✅ Fixed
👩💻 Good First Issue
‼️ High Priority
🧑💻 In Progress
🐧 Linux
🐧 Linux
💤 Low Priority
🍎 Mac
❕ Medium Priority
pull-request
🪟 Windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Launcher#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
callcommand. 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:
I am unsure if this is an isolated case I encountered.
I am unsure if this issue applies to other multi-language systems.
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