starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

conhost.exe problem with fonts. #22368

New Issue
Closed
opened 2026-01-31 08:11:09 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 08:11:09 +00:00
Owner
Copy Link

Originally created by @0wwafa on GitHub (Oct 10, 2024).

I have quite a few fonts in my system.
The problem now is that when using conhost.exe, fonts like Source Code Pro, Lucida Console and even DejaVuSans, seem to have lost unicode.
None of them show unicode.
I have no idea what happened.

Originally created by @0wwafa on GitHub (Oct 10, 2024). I have quite a few fonts in my system. The problem now is that when using conhost.exe, fonts like Source Code Pro, Lucida Console and even DejaVuSans, seem to have lost unicode. None of them show unicode. I have no idea what happened.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 08:11:09 +00:00
claunia commented 2026-01-31 08:11:10 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 10, 2024):

Please provide your Windows version (winver command) and screenshots of the issue.

(We have a bug template when you click on "New issue". Please use it when filing issues that you think are bugs. That makes our lives a lot easier. Screenshots also always help us a ton!)

@lhecker commented on GitHub (Oct 10, 2024): Please provide your Windows version (`winver` command) and screenshots of the issue. (We have a bug template when you click on "New issue". Please use it when filing issues that you think are bugs. That makes our lives a lot easier. Screenshots also always help us a ton!)
claunia commented 2026-01-31 08:11:10 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

Please provide your Windows version (winver command) and screenshots of the issue.

(We have a bug template when you click on "New issue". Please use it when filing issues that you think are bugs. That makes our lives a lot easier. Screenshots also always help us a ton!)

Microsoft Windows [Version 10.0.19045.5011]

screenshot is useless... unicode character are just displayed as a box or a box with a question mark inside.
the only font where this does not happen is the newly installed "Cascadia" but all old fonts that work in terminal and in any other application, don't work anymore in conhost... I think I am a good programmer but I have no clue of what happened.

@0wwafa commented on GitHub (Oct 11, 2024): > Please provide your Windows version (`winver` command) and screenshots of the issue. > > (We have a bug template when you click on "New issue". Please use it when filing issues that you think are bugs. That makes our lives a lot easier. Screenshots also always help us a ton!) Microsoft Windows [Version 10.0.19045.5011] screenshot is useless... unicode character are just displayed as a box or a box with a question mark inside. the only font where this does not happen is the newly installed "Cascadia" but all old fonts that work in terminal and in any other application, don't work anymore in conhost... I think I am a good programmer but I have no clue of what happened.
claunia commented 2026-01-31 08:11:10 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

Cascadia:
Image

Consolas (or even Ubuntu or my favourite DejaVu Mono Sans)
Image

@0wwafa commented on GitHub (Oct 11, 2024): Cascadia: ![Image](https://github.com/user-attachments/assets/bf48e26b-539e-4b1a-9532-03e41d3428c1) Consolas (or even Ubuntu or my favourite DejaVu Mono Sans) ![Image](https://github.com/user-attachments/assets/f530ca9c-19c7-489f-8154-d6ee66cad087)
claunia commented 2026-01-31 08:11:11 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

The weirdest thing is that my fonts (Consolas, DejaVu, etc) they all work in other applications...
For example, UltraEdit64 supports unicode and it shows correctly with all those fonts.
It's like conhost has now some problem probably related to codepage (but the codepage is set correctly to 65001)
if it helps:Image

@0wwafa commented on GitHub (Oct 11, 2024): The weirdest thing is that my fonts (Consolas, DejaVu, etc) they all work in other applications... For example, UltraEdit64 supports unicode and it shows correctly with all those fonts. It's like conhost has now some problem probably related to codepage (but the codepage is set correctly to 65001) if it helps:![Image](https://github.com/user-attachments/assets/bf6cbb21-b934-4efc-bf21-5ea02c28a37d)
claunia commented 2026-01-31 08:11:11 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

The crazy thing is that if I use Cascadia, conhost.exe works:

Any other font I tried don't work anymore in pure conhost.

Image

@0wwafa commented on GitHub (Oct 11, 2024): The crazy thing is that if I use Cascadia, conhost.exe works: Any other font I tried don't work anymore in pure conhost. ![Image](https://github.com/user-attachments/assets/c781c4f7-4ae6-45dc-934c-9a5934735413)
claunia commented 2026-01-31 08:11:11 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 11, 2024):

screenshot is useless... unicode character are just displayed as a box or a box with a question mark inside.

The screenshots are still valuable to me because I currently maintain the text renderer and that lets me diagnose most issues right away. It also let me diagnose your issue immediately when combined with your Windows version number. 🙂 (Please make sure to provide such things in all future issues you file, if possible!)

The good news is that your issue was fixed by pull request #10478. The reason it works with Cascadia is because it includes the ⣿ glyph U+28FF, while Consolas and the other fonts don't. Now that we support font fallback again it'll work with your other fonts as well. The bad news is that we missed the time window to backport it to Windows 10. This means the fix is only available on Windows 11 22H2 and later.

I'll be closing the issue for now. Let me know if you think I made a mistake, or if you have any other questions.

@lhecker commented on GitHub (Oct 11, 2024): > screenshot is useless... unicode character are just displayed as a box or a box with a question mark inside. The screenshots are still valuable to me because I currently maintain the text renderer and that lets me diagnose most issues right away. It also let me diagnose your issue immediately when combined with your Windows version number. 🙂 (Please make sure to provide such things in all future issues you file, if possible!) The good news is that your issue was fixed by pull request #10478. The reason it works with Cascadia is because it includes the ⣿ glyph U+28FF, while Consolas and the other fonts don't. Now that we support font fallback again it'll work with your other fonts as well. The bad news is that we missed the time window to backport it to Windows 10. This means the fix is only available on Windows 11 22H2 and later. I'll be closing the issue for now. Let me know if you think I made a mistake, or if you have any other questions.
claunia commented 2026-01-31 08:11:12 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

Anyway.. I think some microsoft update f*ked up conhost.exe because if I do:

i:\OpenConsole.exe wsl

Unicode works!

but if I do:
conhost.exe wsl it does not.

Image

@lhecker reopen this please. there is a need for a windows update!

@0wwafa commented on GitHub (Oct 11, 2024): Anyway.. I think some microsoft update f*ked up conhost.exe because if I do: ``` i:\OpenConsole.exe wsl ``` Unicode works! but if I do: conhost.exe wsl it does not. ![Image](https://github.com/user-attachments/assets/94c4e371-9706-4aba-beb7-1d4de436b1f6) @lhecker reopen this please. there is a need for a windows update!
claunia commented 2026-01-31 08:11:12 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

All the incriminated files are dated:
Friday, ‎June ‎14, ‎2024, ‏‎5:18:03 PM

I am using windows 10 education.

How can I roll back those files??

@0wwafa commented on GitHub (Oct 11, 2024): All the incriminated files are dated: Friday, ‎June ‎14, ‎2024, ‏‎5:18:03 PM I am using windows 10 education. How can I roll back those files??
claunia commented 2026-01-31 08:11:12 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future)
The same "wrong" version is in C:\Windows\WinSxS\amd64_microsoft-onecore-console-host-core_31bf3856ad364e35_10.0.19041.4355_none_e2506339d96f482b

@0wwafa commented on GitHub (Oct 11, 2024): Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future) The same "wrong" version is in C:\Windows\WinSxS\amd64_microsoft-onecore-console-host-core_31bf3856ad364e35_10.0.19041.4355_none_e2506339d96f482b
claunia commented 2026-01-31 08:11:13 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 11, 2024):

Anyway.. I think some microsoft update f*ked up conhost.exe because if I do:

Well, you aren't using conhost in that image, you're using OpenConsole and presumably a very recent version of it. That version will work of course, since it will contain #10478. You can't compare that with your system conhost which is 5+ years old.

How can I roll back those files??

...put differently: Your conhost is not broken due to a recent update.

Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future)

Right now we don't support deploying OpenConsole as a conhost. You can only replace C:\Windows\System32\conhost.exe with it, but that will trigger the SFC failure you mentioned. (Note: If you do that, we can't help you if anything breaks. Please make backups.)

Unfortunately, the only way to fix it is to either use Windows Terminal, wezterm (which also includes a modern OpenConsole), or to upgrade to Windows 11 22H2 or newer.

@lhecker commented on GitHub (Oct 11, 2024): > Anyway.. I think some microsoft update f*ked up conhost.exe because if I do: Well, you aren't using conhost in that image, you're using OpenConsole and presumably a very recent version of it. That version will work of course, since it will contain #10478. You can't compare that with your system conhost which is 5+ years old. > How can I roll back those files?? ...put differently: Your conhost is not broken due to a recent update. > Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future) Right now we don't support deploying OpenConsole as a conhost. You can only replace `C:\Windows\System32\conhost.exe` with it, but that will trigger the SFC failure you mentioned. (Note: If you do that, we can't help you if anything breaks. Please make backups.) Unfortunately, the only way to fix it is to either use Windows Terminal, wezterm (which also includes a modern OpenConsole), or to upgrade to Windows 11 22H2 or newer.
claunia commented 2026-01-31 08:11:13 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Oct 11, 2024):

Anyway.. I think some microsoft update f*ked up conhost.exe because if I do:

Well, you aren't using conhost in that image, you're using OpenConsole and presumably a very recent version of it. That version will work of course, since it will contain #10478. You can't compare that with your system conhost which is 5+ years old.

NO. If I do: START >> run >> cmd.exe the conhost.exe in c:\windows\system32 runs.
And that is flawed and not 5 year old but dated: Friday, ‎June ‎14, ‎2024, ‏‎5:18:03 PM

How can I roll back those files??

...put differently: Your conhost is not broken due to a recent update.

WRONG again. IT IS.

Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future)

Right now we don't support deploying OpenConsole as a conhost. You can only replace C:\Windows\System32\conhost.exe with it, but that will trigger the SFC failure you mentioned. (Note: If you do that, we can't help you if anything breaks. Please make backups.)

Unfortunately, the only way to fix it is to either use Windows Terminal, wezterm (which also includes a modern OpenConsole), or to upgrade to Windows 11 22H2 or newer.

That's wrong too.
I changed the shortcuts to CMD.EXE and BASH.exe (ubuntu in wsl) to open with openconsole.exe (and not terminal, which sucks).
And everything work.

But everything worked also a couple of updates ago.

@0wwafa commented on GitHub (Oct 11, 2024): > > Anyway.. I think some microsoft update f*ked up conhost.exe because if I do: > > Well, you aren't using conhost in that image, you're using OpenConsole and presumably a very recent version of it. That version will work of course, since it will contain [#10478](https://github.com/microsoft/terminal/pull/10478). You can't compare that with your system conhost which is 5+ years old. > NO. If I do: START >> run >> cmd.exe the conhost.exe in c:\windows\system32 runs. And that is flawed and not 5 year old but dated: **Friday, ‎June ‎14, ‎2024, ‏‎5:18:03 PM** > > How can I roll back those files?? > > ...put differently: Your conhost is not broken due to a recent update. WRONG again. IT IS. > > Please tell me how to install conhost.exe system wide (in a way that SFC /scannnow does not overwrite it in the future) > > Right now we don't support deploying OpenConsole as a conhost. You can only replace `C:\Windows\System32\conhost.exe` with it, but that will trigger the SFC failure you mentioned. (Note: If you do that, we can't help you if anything breaks. Please make backups.) > > Unfortunately, the only way to fix it is to either use Windows Terminal, wezterm (which also includes a modern OpenConsole), or to upgrade to Windows 11 22H2 or newer. That's wrong too. I changed the shortcuts to CMD.EXE and BASH.exe (ubuntu in wsl) to open with openconsole.exe (and not terminal, which *sucks*). And everything work. But everything worked also a couple of updates ago.
claunia commented 2026-01-31 08:11:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 11, 2024):

On the version of Windows you are complaining about, there have been no changes to conhost (the tests commit does not contain conhost changes) since August 2023

Image

Whatever is happening on your Windows installation is outside the scope of Microsoft's control.

@DHowett commented on GitHub (Oct 11, 2024): On the version of Windows you are complaining about, there have been no changes to conhost (the tests commit does not contain conhost changes) since August 2023 ![Image](https://github.com/user-attachments/assets/754f0c28-77af-494a-bfd8-12823af2dfa7) Whatever is happening on your Windows installation is outside the scope of Microsoft's control.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22368
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?