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

Newly installed PowerShell version did not automatically become default profile #21572

New Issue
Closed
opened 2026-01-31 07:48:28 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:48:28 +00:00
Owner
Copy Link

Originally created by @carlos-zamora on GitHub (Apr 24, 2024).

Windows Terminal version

1.21.1094.0

Windows build number

No response

Other Software

PowerShell 7

Steps to reproduce

  1. Have a fresh machine (or similar config)
  2. Install WT Canary
  3. Notice that you have the standard profiles of Windows PowerShell, CMD, and ACS
  4. Install PowerShell 7 via winget
  5. Close and reopen WT Canary

Expected Behavior

We have code to automatically select PowerShell 7 as your default profile if it was just installed. That should happen.

Actual Behavior

PowerShell 7 is not the default profile. Windows PowerShell continues to be the default.

Originally created by @carlos-zamora on GitHub (Apr 24, 2024). ### Windows Terminal version 1.21.1094.0 ### Windows build number _No response_ ### Other Software PowerShell 7 ### Steps to reproduce 1. Have a fresh machine (or similar config) 2. Install WT Canary 3. Notice that you have the standard profiles of Windows PowerShell, CMD, and ACS 4. Install PowerShell 7 via winget 5. Close and reopen WT Canary ### Expected Behavior We have code to automatically select PowerShell 7 as your default profile if it was just installed. That should happen. ### Actual Behavior PowerShell 7 is not the default profile. Windows PowerShell continues to be the default.
claunia commented 2026-01-31 07:48:30 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 24, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Apr 24, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [--profile parameter not opens "Powershell 7" (#16059)](https://github.com/microsoft/terminal/issues/16059), similarity score: 0.77 - [Windows Terminal Preview Version: 1.17.1023 does not automatically create a profile for PowerShell 7.4.0-preview.3 (#15341)](https://github.com/microsoft/terminal/issues/15341), similarity score: 0.75 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:48:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 24, 2024):

FWIW, we never change the user's default profile once they've installed Terminal. Why would we?

@DHowett commented on GitHub (Apr 24, 2024): FWIW, we _never_ change the user's default profile once they've installed Terminal. Why would we?
claunia commented 2026-01-31 07:48:31 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 24, 2024):

Oh. I thought we had code in the PowerShell dynamic profile generator to figure out which PowerShell profile we wanted the user to have and make that the default.

@carlos-zamora commented on GitHub (Apr 24, 2024): Oh. I thought we had code in the PowerShell dynamic profile generator to figure out which PowerShell profile we wanted the user to have and make that the default.
claunia commented 2026-01-31 07:48:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 24, 2024):

This only applies if pwsh is present at the time of first launch

@DHowett commented on GitHub (Apr 24, 2024): This only applies if pwsh is present at the time of first launch
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-Settings Issue-Bug Needs-Triage Product-Terminal Resolution-By-Design
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#21572
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?