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

Use legacy console option prevents Terminal from launching ConPTYs correctly #2587

New Issue
Closed
opened 2026-01-30 22:59:00 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:59:00 +00:00
Owner
Copy Link

Originally created by @miniksa on GitHub (Jul 5, 2019).

I got this issue and after uncheck Use legacy console option, my terminal show up

image

Originally posted by @oclockvn in https://github.com/microsoft/terminal/issues/1364#issuecomment-508796240

This represents double-checking that the startup routines in entrypoints.cpp are ignoring the v1/v2 status when identifying a ConPTY-style connection and always doing v2.

Originally created by @miniksa on GitHub (Jul 5, 2019). I got this issue and after uncheck `Use legacy console` option, my terminal show up ![image](https://user-images.githubusercontent.com/3783976/60732611-b6003380-9f74-11e9-8fa6-63caa802b4b2.png) _Originally posted by @oclockvn in https://github.com/microsoft/terminal/issues/1364#issuecomment-508796240_ This represents double-checking that the startup routines in `entrypoints.cpp` are ignoring the v1/v2 status when identifying a ConPTY-style connection and always doing v2.
claunia commented 2026-01-30 22:59:03 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 9, 2019):

Confirming: we check the ForceV1 key and fail out if the user has ForceV1 and is requesting commandline launch. To make legacy console not interfere with CreatePseudoConsole (which doesn't use commandline launch), we need to detect that the server handle being passed in is for pseudoconsole work.
We could key off the presence of --signal in both cases.

@DHowett-MSFT commented on GitHub (Jul 9, 2019): Confirming: we check the ForceV1 key and fail out if the user has ForceV1 and is requesting commandline launch. To make legacy console not interfere with CreatePseudoConsole (which doesn't use commandline launch), we need to detect that the server handle being passed in is for pseudoconsole work. We could key off the presence of `--signal` in both cases.
claunia commented 2026-01-30 22:59:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 9, 2019):

(Confirmed this is broken in the windows image as well. pwincon refuses to launch because it bombs out in CreatePseudoConsole :))

@DHowett-MSFT commented on GitHub (Jul 9, 2019): (Confirmed this is broken in the windows image as well. pwincon refuses to launch because it bombs out in CreatePseudoConsole :))
claunia commented 2026-01-30 22:59:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 3, 2019):

:tada:This issue was addressed in #1935, which has now been successfully released as Windows Terminal Preview v0.3.2142.0.🎉

Handy links:

@ghost commented on GitHub (Aug 3, 2019): :tada:This issue was addressed in #1935, which has now been successfully released as `Windows Terminal Preview v0.3.2142.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.3.2142.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-Server Help Wanted Issue-Bug Needs-Tag-Fix Product-Conhost Product-Terminal Resolution-Fix-Committed
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#2587
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?