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

Allow conhost to be replaced with OpenConsole #22391

New Issue
Open
opened 2026-01-31 08:11:55 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:11:55 +00:00
Owner
Copy Link

Originally created by @lhecker on GitHub (Oct 14, 2024).

Description of the new feature/enhancement

conhost can lack behind OpenConsole by several (if not many) years. This brings 2 problems:

  • People preferring conhost's look and feel cannot get updates for many years.
  • We (the maintainers) cannot test new features and changes for many years.

In other words, not being able to replace conhost is a lose-lose situation.

Proposed technical implementation details (optional)

  • Ship a conhost package in the store that replaces the system conhost, just like how notepad does it.
  • Consider doing the same for the Windows Terminal Canary package so that we can get a slightly better usage coverage.
Originally created by @lhecker on GitHub (Oct 14, 2024). # Description of the new feature/enhancement conhost can lack behind OpenConsole by several (if not many) years. This brings 2 problems: * People preferring conhost's look and feel cannot get updates for many years. * We (the maintainers) cannot test new features and changes for many years. In other words, not being able to replace conhost is a lose-lose situation. # Proposed technical implementation details (optional) * Ship a conhost package in the store that replaces the system conhost, just like how notepad does it. * Consider doing the same for the Windows Terminal Canary package so that we can get a slightly better usage coverage.
claunia added the Issue-FeatureProduct-ConhostNeeds-Tag-Fix labels 2026-01-31 08:11:55 +00:00
claunia commented 2026-01-31 08:11:56 +00:00
Author
Owner
Copy Link

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

So you are planning to use App Execution Alias for conhost.exe?

I tried that adding a registry entry:
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\conhost.exe]
@="I:\OpenConsole.exe"
"Path"="I:\"

but I think there is something else needed to test it properly (without overwriting the original conhost.exe)

@lhecker
any clue so I can test it?

The registry entry works if I call conhost.exe bash.exe from start/run,
But it does not if in start/run I just type: bash.exe

I also tried:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

But I get the same behaviour.

@0wwafa commented on GitHub (Oct 17, 2024): So you are planning to use App Execution Alias for conhost.exe? I tried that adding a registry entry: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\conhost.exe] @="I:\\OpenConsole.exe" "Path"="I:\\" but I think there is something else needed to test it properly (without overwriting the original conhost.exe) @lhecker any clue so I can test it? The registry entry works if I call conhost.exe bash.exe from start/run, But it does not if in start/run I just type: bash.exe I also tried: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths But I get the same behaviour.
claunia commented 2026-01-31 08:11:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 17, 2024):

C O N H O S T
C O A S T
T O
C O A S T

@zadjii-msft commented on GitHub (Oct 17, 2024): C O N H O S T C O A S T T O C O A S T
claunia commented 2026-01-31 08:11:56 +00:00
Author
Owner
Copy Link

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

So you are planning to use App Execution Alias for conhost.exe?

That was the initial idea, but if it turns out to not work due to some platform limitation, then we'll have to modify the OS or use some other way to deploy it. The fact that it doesn't work for you seems to indicate that. I've also tried it, and it doesn't work for me either.

Edit: The solution is that we need to expose the name from a package. Modifying the registry like that only sets an alias for the shell / ShellExecute, e.g. like the Run dialog.

@lhecker commented on GitHub (Oct 18, 2024): > So you are planning to use App Execution Alias for conhost.exe? That was the initial idea, but if it turns out to not work due to some platform limitation, then we'll have to modify the OS or use some other way to deploy it. The fact that it doesn't work for you seems to indicate that. I've also tried it, and it doesn't work for me either. Edit: The solution is that we need to expose the name from a package. Modifying the registry like that only sets an alias for the shell / `ShellExecute`, e.g. like the Run dialog.
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 Issue-Feature Needs-Tag-Fix Product-Conhost
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#22391
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?