microsoft / microsoft/terminal
[DefApp] Conhostv1 activation fails from runbox when Default Terminal is set
Open
Nobody has claimed this yet.
Area-DefApp
Issue-Bug
Priority-2
Product-Conhost
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
- Have Default Terminal set up
- Set legacy conhost (ForceV2 registry key off / the setting in the prop sheet) for conhostv1
- Run
conhost cmdfrom 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with Default Terminal enabled, legacy conhost configured through the ForceV2 registry setting or property sheet, and conhost cmd from the runbox. Trace the conhost activation entry point and compare handling of the -ForceV1 option with the Default Terminal configuration. Done means conhost cmd launches as expected in the legacy configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100