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

Terminal no longer auto-generates a profile for PowerShell 7 when installed via winget. #22973

New Issue
Closed
opened 2026-01-31 08:28:51 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 08:28:51 +00:00
Owner
Copy Link

Originally created by @ninbura on GitHub (Feb 24, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

Microsoft Windows NT 10.0.26100.0

Other Software

No response

Steps to reproduce

  1. install Windows 11
  2. open Windows Terminal
  3. install PowerShell 7 via winget 
    • winget install Microsoft.PowerShell
  4. restart Windows Terminal
  5. observe that PowerShell 7 profile was not created

Expected Behavior

When PowerShell 7 is installed via winget, Microsoft Terminal should automatically generate a profile for it.

Actual Behavior

When PowerShell 7 is installed via winget, Microsoft Terminal does not generate a profile for it.

Originally created by @ninbura on GitHub (Feb 24, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number Microsoft Windows NT 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce 1. install Windows 11 2. open Windows Terminal 3. install PowerShell 7 via winget - ```PowerShell winget install Microsoft.PowerShell ``` 4. restart Windows Terminal 5. observe that PowerShell 7 profile was not created ### Expected Behavior When PowerShell 7 is installed via winget, Microsoft Terminal should automatically generate a profile for it. ### Actual Behavior When PowerShell 7 is installed via winget, Microsoft Terminal does not generate a profile for it.
claunia added the Needs-TriageIssue-BugResolution-External labels 2026-01-31 08:28:51 +00:00
claunia commented 2026-01-31 08:28:53 +00:00
Author
Owner
Copy Link

@ninbura commented on GitHub (Feb 24, 2025):

Another user reported this issue on the PowerShell GitHub repository 2 days ago (https://github.com/PowerShell/PowerShell/issues/21289#issuecomment-2676006826). This was not an issue until recently, as it was working as expected only a few weeks ago.

@ninbura commented on GitHub (Feb 24, 2025): Another user reported this issue on the PowerShell GitHub repository 2 days ago (https://github.com/PowerShell/PowerShell/issues/21289#issuecomment-2676006826). This was not an issue until recently, as it was working as expected only a few weeks ago.
claunia commented 2026-01-31 08:28:53 +00:00
Author
Owner
Copy Link

@ninbura commented on GitHub (Feb 24, 2025):

When you Install PowerShell 7 via the releases section of the PowerShell repository a profile is generated.

The specific release I tested (PowerShell-7.5.0-win-x64.msi):
https://github.com/PowerShell/PowerShell/releases/tag/v7.5.0

@ninbura commented on GitHub (Feb 24, 2025): When you Install PowerShell 7 via the releases section of the PowerShell repository a profile is generated. The specific release I tested (`PowerShell-7.5.0-win-x64.msi`): https://github.com/PowerShell/PowerShell/releases/tag/v7.5.0
claunia commented 2026-01-31 08:28:54 +00:00
Author
Owner
Copy Link

@kastentop2005 commented on GitHub (Feb 24, 2025):

Hello. I reinstalled Windows and was surprised it doesn't do this anymore

@kastentop2005 commented on GitHub (Feb 24, 2025): Hello. I reinstalled Windows and was surprised it doesn't do this anymore
claunia commented 2026-01-31 08:28:54 +00:00
Author
Owner
Copy Link

@barndawgie commented on GitHub (Feb 25, 2025):

Same thing for me. Just did a clean Windows install, then installed PowerShell from an elevated cmd.exe prompt using winget. When I open Terminal there is no profile added.

@barndawgie commented on GitHub (Feb 25, 2025): Same thing for me. Just did a clean Windows install, then installed PowerShell from an elevated cmd.exe prompt using winget. When I open Terminal there is no profile added.
claunia commented 2026-01-31 08:28:54 +00:00
Author
Owner
Copy Link

@mbrzakala commented on GitHub (Feb 25, 2025):

I have the same problem — fresh Windows installation with PowerShell installed via winget.

There is a working workaround for this issue: you can simply add the following entry to your profiles list in settings.json:

{
    "commandline": "pwsh.exe",
    "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
    "hidden": false,
    "name": "PowerShell"
}

The issue with finding PowerShell might be related to the changed name of the PowerShell package in winget (it used to be called PowerShell Core).

I also tried using a profile from my other computer, but it didn’t work. The profile in settings.json was:

{
        "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
        "hidden": false,
        "name": "PowerShell",
        "source": "Windows.Terminal.PowershellCore"
}

It seems that Windows.Terminal.PowershellCore does not work for new installations of PowerShell using winget.

@mbrzakala commented on GitHub (Feb 25, 2025): I have the same problem — fresh Windows installation with PowerShell installed via winget. There is a working workaround for this issue: you can simply add the following entry to your profiles list in `settings.json`: ```json { "commandline": "pwsh.exe", "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell" } ``` --- The issue with finding PowerShell might be related to the changed name of the PowerShell package in winget (it used to be called PowerShell Core). I also tried using a profile from my other computer, but it didn’t work. The profile in `settings.json` was: ```json { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell", "source": "Windows.Terminal.PowershellCore" } ``` It seems that Windows.Terminal.PowershellCore does not work for new installations of PowerShell using winget.
claunia commented 2026-01-31 08:28:54 +00:00
Author
Owner
Copy Link

@StevenBucher98 commented on GitHub (Feb 25, 2025):

Related issue we are tracking in the PowerShell repo https://github.com/PowerShell/PowerShell/issues/25068

@StevenBucher98 commented on GitHub (Feb 25, 2025): Related issue we are tracking in the PowerShell repo https://github.com/PowerShell/PowerShell/issues/25068
claunia commented 2026-01-31 08:28:55 +00:00
Author
Owner
Copy Link

@StevenBucher98 commented on GitHub (Feb 25, 2025):

@mbrzakala we merged a potential fix 2 hours ago, can you try to uninstall and reinstall via winget again and see if that works?

@StevenBucher98 commented on GitHub (Feb 25, 2025): @mbrzakala we merged a potential fix 2 hours ago, can you try to uninstall and reinstall via winget again and see if that works?
claunia commented 2026-01-31 08:28:55 +00:00
Author
Owner
Copy Link

@ninbura commented on GitHub (Feb 25, 2025):

@mbrzakala we merged a potential fix 2 hours ago

Out of curiosity, was the fix to revert default installation via winget to the non-portable version?

@ninbura commented on GitHub (Feb 25, 2025): > @mbrzakala we merged a potential fix 2 hours ago Out of curiosity, was the fix to revert default installation via winget to the non-portable version?
claunia commented 2026-01-31 08:28:55 +00:00
Author
Owner
Copy Link

@mbrzakala commented on GitHub (Feb 25, 2025):

@StevenBucher98 After reinstalation everything works perfect. Thank you!

@mbrzakala commented on GitHub (Feb 25, 2025): @StevenBucher98 After reinstalation everything works perfect. Thank you!
claunia commented 2026-01-31 08:28:55 +00:00
Author
Owner
Copy Link

@mbrzakala commented on GitHub (Feb 25, 2025):

@ninbura I've reinstalled both PowerShell and Windows Terminal using the built-in terminal in Visual Studio Code. I used the standard winget packages: Microsoft.PowerShell and Microsoft.WindowsTerminal

@mbrzakala commented on GitHub (Feb 25, 2025): @ninbura I've reinstalled both PowerShell and Windows Terminal using the built-in terminal in Visual Studio Code. I used the standard winget packages: Microsoft.PowerShell and Microsoft.WindowsTerminal
claunia commented 2026-01-31 08:28:56 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 26, 2025):

@StevenBucher98 After reinstalation everything works perfect. Thank you!

@StevenBucher98 Thanks for looking into this! Closing as External!

@carlos-zamora commented on GitHub (Feb 26, 2025): > [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/20605456?u=96831a1a8e45636ef4e013f2c3df32dbc2d8c50f&amp;v=4&amp;size=80">@StevenBucher98](https://github.com/StevenBucher98?rgh-link-date=2025-02-25T20%3A53%3A08.000Z) After reinstalation everything works perfect. Thank you! @StevenBucher98 Thanks for looking into this! Closing as External!
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-Bug 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#22973
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?