starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Multiple Windows.Terminal.PowershellCore profiles not possible #5838

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

Originally created by @bormm on GitHub (Jan 9, 2020).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): Windows Terminal Preview v0.7.3451.0
Powershell: 7.0.0-rc.1

Steps to reproduce

Create a second entry with
source": "Windows.Terminal.PowershellCore"
and a different GUID.

Expected behavior

  • It is possible to have one or endless more powershell core profiles in the configuration
  • They show up in the GUI
  • they can be selected as defaultProfile

Actual behavior

  • After starting the terminal, no second entry will show up.
  • Using the GUI of the second entry shows the message, that the GUID is not found.

Additional information

  • Modifying the first entry, like changing the name, is correctly reflected within the GUI.
  • Duplicating the powershell.exe (old one) profile is possible and works as expected
  • Creating a profile that calls pwsh.exe directly is also possible and works as expected

profiles.zip

Originally created by @bormm on GitHub (Jan 9, 2020). # Environment Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): Windows Terminal Preview v0.7.3451.0 Powershell: 7.0.0-rc.1 # Steps to reproduce Create a second entry with `source": "Windows.Terminal.PowershellCore"` and a different GUID. # Expected behavior - It is possible to have one or endless more powershell core profiles in the configuration - They show up in the GUI - they can be selected as defaultProfile # Actual behavior - After starting the terminal, no second entry will show up. - Using the GUI of the second entry shows the message, that the GUID is not found. # Additional information - Modifying the first entry, like changing the name, is correctly reflected within the GUI. - Duplicating the powershell.exe (old one) profile is possible and works as expected - Creating a profile that calls pwsh.exe directly is also possible and works as expected [profiles.zip](https://github.com/microsoft/terminal/files/4039650/profiles.zip)
claunia added the Area-SettingsResolution-DuplicateProduct-Terminal labels 2026-01-31 00:23:07 +00:00
claunia commented 2026-01-31 00:23:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 9, 2020):

Yeah, this one's a bit thorny. Sorry about that. Profiles with source metadata are built by "dynamic profile generators", which run on startup to detect the things you might have on your system. I believe you'll be better served by /dup #3818, which will let you create a new profile that applies customizations on top of existing profiles.

@DHowett-MSFT commented on GitHub (Jan 9, 2020): Yeah, this one's a bit thorny. Sorry about that. Profiles with `source` metadata are built by "dynamic profile generators", which run on startup to detect the things you might have on your system. I believe you'll be better served by /dup #3818, which will let you create a new profile that applies customizations _on top of_ existing profiles.
claunia commented 2026-01-31 00:23:08 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 9, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 9, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 00:23:08 +00:00
Author
Owner
Copy Link

@bormm commented on GitHub (Jan 13, 2020):

@DHowett-MSFT
Thank you for the hint for the alternative solution, even its open, but I have still some comments on this:

Yeah, this one's a bit thorny. Sorry about that. Profiles with source metadata are built by "dynamic profile generators", which run on startup to detect the things you might have on your system.

  1. If the profile is created dynamicaly and not a really a profile, why its still called profile? Why its not an additional section called "profileSources"?
    That would clearly separate the generators from the profiles. That would also allow to prevent setting all the values like id and so one just via the json schema.

  2. In case you would not accept that argument, why is setting the name on a profile source is allowed, but the id is not? Why is setting the id not throwing some error at startup time? Why is no error thrown at all, if at the end the profile was not processed?

@bormm commented on GitHub (Jan 13, 2020): @DHowett-MSFT Thank you for the hint for the alternative solution, even its open, but I have still some comments on this: > Yeah, this one's a bit thorny. Sorry about that. Profiles with `source` metadata are built by "dynamic profile generators", which run on startup to detect the things you might have on your system. 1. If the profile is created dynamicaly and not a really a profile, why its still called profile? Why its not an additional section called "profileSources"? That would clearly separate the generators from the profiles. That would also allow to prevent setting all the values like id and so one just via the json schema. 2. In case you would not accept that argument, why is setting the name on a profile source is allowed, but the id is not? Why is setting the id not throwing some error at startup time? Why is no error thrown at all, if at the end the profile was not processed?
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 Product-Terminal Resolution-Duplicate
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#5838
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?