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

Visual Studio 2022 uses cmd instead of windows terminal #17415

New Issue
Open
opened 2026-01-31 05:41:50 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:41:50 +00:00
Owner
Copy Link

Originally created by @suntsu42 on GitHub (May 6, 2022).

Windows Terminal version

1.13.10984.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

I've configured windows terminal to be the default terminal:
image

I've created a simple .net 6 console application in Visual Studio Professional 2022
image

When i debug this console application, its started in a cmd shell rather than in the windows terminal
image

When i run cmd via "Windows-R", it does actually start the terminal (as expected). This means the windows terminal is set as default terminal for windows.

Is there a specific settings in visual studio in order to force the use of the windows terminal?

Expected Behavior

Visual studio starts the windows terminal when debugging a console application

Actual Behavior

Visual studio starts the cmd terminal

Originally created by @suntsu42 on GitHub (May 6, 2022). ### Windows Terminal version 1.13.10984.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce I've configured windows terminal to be the default terminal: ![image](https://user-images.githubusercontent.com/1768336/167101141-1090f46b-6c60-448a-b4f9-34d93df2e978.png) I've created a simple .net 6 console application in Visual Studio Professional 2022 ![image](https://user-images.githubusercontent.com/1768336/167101187-e05ed0fb-a8c2-49e8-a140-3ff5779446cb.png) When i debug this console application, its started in a cmd shell rather than in the windows terminal ![image](https://user-images.githubusercontent.com/1768336/167101313-5982a9f4-9968-4ae0-8152-d5e8f98abf83.png) When i run **cmd** via "Windows-R", it does actually start the terminal (as expected). This means the windows terminal is set as default terminal for windows. Is there a specific settings in visual studio in order to force the use of the windows terminal? ### Expected Behavior Visual studio starts the windows terminal when debugging a console application ### Actual Behavior Visual studio starts the cmd terminal
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 Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-External
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#17415
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?