Query the user's default shell when creating the default profiles #1025

Closed
opened 2026-01-30 22:14:09 +00:00 by claunia · 1 comment
Owner

Originally created by @zadjii-msft on GitHub (May 13, 2019).

We may also want to follow the Windows Shell option that dictates what shell lives in your WIN+X menu.

The registry key set by taskbar settings is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\DontUsePowerShellOnWinX
The default is 0 to use powershell I believe.

If that regkey is 1, let's use cmd.exe as the default profile when creating the default profiles.

Originally created by @zadjii-msft on GitHub (May 13, 2019). > We may also want to follow the Windows Shell option that dictates what shell lives in your `WIN+X` menu. > The registry key set by taskbar settings is: > `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\DontUsePowerShellOnWinX` > The default is 0 to use powershell I believe. If that regkey is 1, let's use `cmd.exe` as the default profile when creating the default profiles.
claunia added the Help WantedArea-SettingsIssue-TaskNeeds-Tag-FixProduct-Terminal labels 2026-01-30 22:14:09 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 22, 2021):

You know, we've been using pwsh > powershell as the default for a couple years now, without any major complaints. Plus, they got rid of the "default shell" setting entirely in Windows 11, so I think it's safe to cut this one.

@zadjii-msft commented on GitHub (Nov 22, 2021): You know, we've been using `pwsh` > `powershell` as the default for a couple years now, without any major complaints. Plus, they got rid of the "default shell" setting entirely in Windows 11, so I think it's safe to cut this one.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1025