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

Bring back old Windows ways of launching Cmd #11242

New Issue
Closed
opened 2026-01-31 02:42:22 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:42:22 +00:00
Owner
Copy Link

Originally created by @ck2510 on GitHub (Oct 30, 2020).

Description of the new feature/enhancement

In early versions of Windows10 it was still possible to launch Cmd from Windows Explorer context menu and also to place an icon into the Windows Explorer "QuickAccessToolbar". Then at some point it was decided to promote PowerShell and those possibilities where removed and strange registry hacks emerged to control the behavior of cmd vs. powershell involving keys like HideBasedOnVelocityId and ShowBasedOnVelocityId, see also [1].

Now there a strange hacks with questionable security to bring back the old UX or workarounds with less integration as shell commands.

[1]
https://superuser.com/questions/1201988/how-do-i-change-open-with-powershell-to-open-with-command-prompt-when-shift

Proposed technical implementation details (optional)

Encourage Windows to again give user the choice between PowerShell and Cmd and have both with equal level of integration in the system, as it is still the case for Win-X menu.

Edit: removed mistake of referring to command line, actually Windows Explorer context menu was meant
Edit2: fixed link

Originally created by @ck2510 on GitHub (Oct 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement In early versions of Windows10 it was still possible to launch Cmd from Windows Explorer context menu and also to place an icon into the Windows Explorer "QuickAccessToolbar". Then at some point it was decided to promote PowerShell and those possibilities where removed and strange registry hacks emerged to control the behavior of cmd vs. powershell involving keys like HideBasedOnVelocityId and ShowBasedOnVelocityId, see also [1]. Now there a strange hacks with questionable security to bring back the old UX or workarounds with less integration as shell commands. [1] https://superuser.com/questions/1201988/how-do-i-change-open-with-powershell-to-open-with-command-prompt-when-shift <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Encourage Windows to again give user the choice between PowerShell and Cmd and have both with equal level of integration in the system, as it is still the case for Win-X menu. <!-- A clear and concise description of what you want to happen. --> Edit: removed mistake of referring to command line, actually Windows Explorer context menu was meant Edit2: fixed link
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixResolution-Won't-Fix labels 2026-01-31 02:42:22 +00:00
claunia commented 2026-01-31 02:42:23 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Oct 30, 2020):

This will never happen. CMD is still available for use. When right click selection in Explorer is brought back for Windows Terminal, you'll get this behavior if you set CMD as your default (eventually a selection between profiles will also be added). CMD is not equal to Powershell and never will be. You are heavily encouraged to use Powershell, which continues to get support in the form of Powershell Core.

@WSLUser commented on GitHub (Oct 30, 2020): This will never happen. CMD is still available for use. When right click selection in Explorer is brought back for Windows Terminal, you'll get this behavior if you set CMD as your default (eventually a selection between profiles will also be added). CMD is not equal to Powershell and never will be. You are heavily encouraged to use Powershell, which continues to get support in the form of Powershell Core.
claunia commented 2026-01-31 02:42:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 30, 2020):

No. You can configure whatever you like on your own machine; we are not stopping you.

@DHowett commented on GitHub (Oct 30, 2020): No. You can configure whatever you like on your own machine; we are not stopping you.
claunia commented 2026-01-31 02:42:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 30, 2020):

You are free to put shortcuts to CMD anywhere on your system that you like. Put 100 of them on your taskbar, type cmd into the address bar, change the default profile of Terminal to CMD. We only control one of these surfaces.
I do not understand why you have cited this repository, the repository on which you filed this issue, as a hack?

@DHowett commented on GitHub (Oct 30, 2020): You are free to put shortcuts to CMD _anywhere on your system that you like_. Put 100 of them on your taskbar, type cmd into the address bar, change the default profile of Terminal to CMD. We only control one of these surfaces. I do not understand why you have cited this repository, _the repository on which you filed this issue_, as a hack?
claunia commented 2026-01-31 02:42:23 +00:00
Author
Owner
Copy Link

@ck2510 commented on GitHub (Oct 30, 2020):

Sorry my mistake with the link I can understand that the request is outside the scope of this project. Anyway I have a hard time to understand MS strategy here. This project promotes CMD/terminal, Windows tries to push it out from UX.

@ck2510 commented on GitHub (Oct 30, 2020): Sorry my mistake with the link I can understand that the request is outside the scope of this project. Anyway I have a hard time to understand MS strategy here. This project promotes CMD/terminal, Windows tries to push it out from UX.
claunia commented 2026-01-31 02:42:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 4, 2020):

I think there's a bit of a misunderstanding here - cmd != console.

cmd.exe is a shell, like powershell or bash.

These commandline clients can run attached to a console. Whenever you open cmd.exe, the window that you're actually seeing is conhost.exe, the Console. That's the window that serves all console application on Windows, including cmd and powershell.

This is the repo for both the Console and the Windows Terminal. Both their codebases live in this repo. The Console is getting occasional maintenance, and the Terminal is actively maintained and updated frequently. What we're not doing is actively promoting cmd. The official party line is "if you want a modern shell, that receives updates, use PowerShell".

@zadjii-msft commented on GitHub (Nov 4, 2020): I think there's a bit of a misunderstanding here - `cmd` != console. `cmd.exe` is a _shell_, like `powershell` or `bash`. These commandline clients can run attached to a console. Whenever you open `cmd.exe`, the window that you're actually seeing is `conhost.exe`, the _Console_. That's the window that serves all console application on Windows, including `cmd` _and_ `powershell`. This is the repo for both the Console and the Windows Terminal. Both their codebases live in this repo. The Console is getting occasional maintenance, and the Terminal is actively maintained and updated frequently. What we're _not_ doing is actively promoting `cmd`. The official party line is "if you want a modern shell, that receives updates, use PowerShell".
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 Needs-Triage Resolution-Won't-Fix
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#11242
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?