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

Using different GUIDs for profiles that use "source" cause them to not be found by Terminal. #7578

New Issue
Open
opened 2026-01-31 01:07:45 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:07:45 +00:00
Owner
Copy Link

Originally created by @TechPreacher on GitHub (Apr 23, 2020).

Environment

Windows build number: Version 10.0.18363.778
Windows Terminal version: 0.11
Any other software? No

Steps to reproduce

  • Open Terminal, let it create a new, default configuration file (settings.json).
  • Make the PowerShell Core the default profile: {574e775e-4f2a-5b96-ac1e-a2962a402336}
    • This will work, Terminal will now launch with PowerShell Core as default profile.
  • Go to profiles section, change any value in the PowerShell Core profile's GUID and make this new GUID the default profile.
    • This will cause the PowerShell Core profile with the changed GUID to be ignored, causing:
      • A new PowerShell Core profile with the original GUID being added to the end of the profiles list
      • The default profile (changed PowerShell Core GUID) to be invalid as Terminal can now no longer read the old PowerShell Core profile.
      • The old profile with the changed GUID no longer appears in the list of profiles.

This is only true for all the profiles using a "source" instead of a "commandline" parameter to start the shell.

Expected behavior

Terminal accepts any vaild GUID for any type of profile and starts or lists it in the list of profiles OR clearly documents that profiles need to have a specific GUID.

Actual behavior

  • This will cause the PowerShell Core profile with the changed GUID to be ignored, causing:
    • A new PowerShell Core profile with the original GUID being added to the end of the profiles list
    • The default profile (changed PowerShell Core GUID) to be invalid as Terminal can now no longer read the old PowerShell Core profile.
Originally created by @TechPreacher on GitHub (Apr 23, 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Version 10.0.18363.778 Windows Terminal version: 0.11 Any other software? No ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> - Open Terminal, let it create a new, default configuration file (settings.json). - Make the PowerShell Core the default profile: {574e775e-4f2a-5b96-ac1e-a2962a402336} - This will work, Terminal will now launch with PowerShell Core as default profile. - Go to profiles section, change any value in the PowerShell Core profile's GUID and make this new GUID the default profile. - This will cause the PowerShell Core profile with the changed GUID to be ignored, causing: - A new PowerShell Core profile with the original GUID being added to the end of the profiles list - The default profile (changed PowerShell Core GUID) to be invalid as Terminal can now no longer read the old PowerShell Core profile. - The old profile with the changed GUID no longer appears in the list of profiles. This is only true for all the profiles using a "source" instead of a "commandline" parameter to start the shell. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Terminal accepts any vaild GUID for any type of profile and starts or lists it in the list of profiles OR clearly documents that profiles need to have a specific GUID. # Actual behavior <!-- What's actually happening? --> - This will cause the PowerShell Core profile with the changed GUID to be ignored, causing: - A new PowerShell Core profile with the original GUID being added to the end of the profiles list - The default profile (changed PowerShell Core GUID) to be invalid as Terminal can now no longer read the old PowerShell Core profile.
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-Question Product-Terminal Resolution-Answered 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#7578
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?