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

[DefApp] Conhostv1 activation fails from runbox when Default Terminal is set #15764

New Issue
Open
opened 2026-01-31 04:47:48 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:47:48 +00:00
Owner
Copy Link

Originally created by @miniksa on GitHub (Nov 2, 2021).

  1. Have Default Terminal set up
  2. Set legacy conhost (ForceV2 registry key off / the setting in the prop sheet) for conhostv1
  3. Run conhost cmd from the runbox which should launch it

Expected: it launches
Actual: nothing happens

Bonus points.... conhost cmd -ForceV1 doesn't seem to do what I want either

Originally created by @miniksa on GitHub (Nov 2, 2021). 1. Have Default Terminal set up 2. Set legacy conhost (ForceV2 registry key off / the setting in the prop sheet) for conhostv1 3. Run `conhost cmd` from the runbox which should launch it Expected: it launches Actual: nothing happens Bonus points.... `conhost cmd -ForceV1` doesn't seem to do what I want either
claunia added the Product-ConhostIssue-BugPriority-2Area-DefApp labels 2026-01-31 04:47:48 +00:00
claunia commented 2026-01-31 04:47:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 8, 2022):

@miniksa I'm pretty sure this isn't a regression.

f217f6dc33/src/host/exe/exemain.cpp (L298-L313)

But even before defterm: (harder to find since the file moved and git considered it rewritten):
d09fdd61cb/src/host/exemain.cpp (L178-L192)

Pretty sure conhost cmd goes down the ShouldCreateServerHandle path, and _createServerHandle is only set to false when it actually gets the 0x4 on the commandline.

So,

  • not a defterm regression
  • conhost cmd -ForceV1 may still be busted, but I doubt it ever worked
  • punt from 1.14? Close?
@zadjii-msft commented on GitHub (Mar 8, 2022): @miniksa I'm pretty sure this isn't a regression. https://github.com/microsoft/terminal/blob/f217f6dc331559f57301dfb84ce3898d20c944d6/src/host/exe/exemain.cpp#L298-L313 But even before defterm: (harder to find since the file moved and git considered it rewritten): https://github.com/microsoft/terminal/blob/d09fdd61cbb11b7ef2ccdd4820349ffe898ad583/src/host/exemain.cpp#L178-L192 Pretty sure `conhost cmd` goes down the `ShouldCreateServerHandle` path, and `_createServerHandle` is only set to `false` when it actually gets the `0x4` on the commandline. So, * not a defterm regression * `conhost cmd -ForceV1` may still be busted, but I doubt it ever worked * punt from 1.14? Close?
claunia commented 2026-01-31 04:47:49 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Mar 10, 2022):

Icebox it I guess.

@miniksa commented on GitHub (Mar 10, 2022): Icebox it I guess.
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 Area-DefApp Issue-Bug Priority-2 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#15764
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?