HKCU\Console\CodePage ... does it do anything? #15663

Open
opened 2026-01-31 04:44:53 +00:00 by claunia · 0 comments
Owner

Originally created by @vefatica on GitHub (Oct 23, 2021).

Microsoft Windows 10 Pro for Workstations
10.0.19043.1288 (2009, 21H1)

I thought that HKCU\Console\CodePage set the default output code page for consoles (and I'm pretty sure that, at least once upon a time, it did). But it does not now. Although I have

hkcu\console
  CodePage : REG_DWORD : 1252

all console apps which don't have another specification start with CP 437 (CP_OEMCP).

But if, for example, I have

hkcu\console\SystemRoot_system32_cmd.exe
    CodePage : REG_DWORD : 1252

then CMD will start with CP 1252.

Shouldn't HKCU\Console\CodePage be setting the default?

And (apparently unrelated to the above) how do I get all shells to use output code page 1252 when running in WindowsTerminal? They all seem to get 437.

Originally created by @vefatica on GitHub (Oct 23, 2021). Microsoft Windows 10 Pro for Workstations 10.0.19043.1288 (2009, 21H1) I thought that HKCU\Console\CodePage set the default output code page for consoles (and I'm pretty sure that, at least once upon a time, it did). But it does not now. Although I have ``` hkcu\console CodePage : REG_DWORD : 1252 ``` all console apps which don't have another specification start with CP 437 (CP_OEMCP). But if, for example, I have ``` hkcu\console\SystemRoot_system32_cmd.exe CodePage : REG_DWORD : 1252 ``` then CMD will start with CP 1252. Shouldn't HKCU\Console\CodePage be setting the default? And (apparently unrelated to the above) how do I get all shells to use output code page 1252 when running in WindowsTerminal? They all seem to get 437.
claunia added the Issue-QuestionResolution-DuplicateProduct-Conpty labels 2026-01-31 04:44:54 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15663