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

Cannot create a second WSL profile #4600

New Issue
Open
opened 2026-01-30 23:51:38 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:51:38 +00:00
Owner
Copy Link

Originally created by @pottereric on GitHub (Oct 23, 2019).

I've added several profiles for various work scenarios. As long as I'm using cmd as the command line it works fine. But if I try to add a second profile using the WSL tools, it won't show up in the new terminal dropdown list.

I want to have 2 WSL profiles, one with the normal font for my standard work and one with a larger font for presentations. I copied the default profile, changed the GUID and the font size.

    {
      "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
      "hidden": false,
      "name": "Ubuntu",
      "source": "Windows.Terminal.Wsl", 
      "fontSize": 12
    },
     {
      "guid": "{e6dd8b9a-fbeb-430c-a3cb-3b95ed4cc707}",
      "hidden": false,
      "name": "UbuntuBig",
      "source": "Windows.Terminal.Wsl", 
      "fontSize": 24
    },

With this saved in my profiles.json, the "Ubuntu" option shows up in the dropdown list, but not "UbuntuBig".

Am I misunderstanding how the profile layer works? Is there something different I need to do in order to have a 2nd profile based on a dynamic profile? Is there some other way to create a profile that uses WSL?

Originally created by @pottereric on GitHub (Oct 23, 2019). I've added several profiles for various work scenarios. As long as I'm using cmd as the command line it works fine. But if I try to add a second profile using the WSL tools, it won't show up in the new terminal dropdown list. I want to have 2 WSL profiles, one with the normal font for my standard work and one with a larger font for presentations. I copied the default profile, changed the GUID and the font size. ``` { "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}", "hidden": false, "name": "Ubuntu", "source": "Windows.Terminal.Wsl", "fontSize": 12 }, { "guid": "{e6dd8b9a-fbeb-430c-a3cb-3b95ed4cc707}", "hidden": false, "name": "UbuntuBig", "source": "Windows.Terminal.Wsl", "fontSize": 24 }, ``` With this saved in my profiles.json, the "Ubuntu" option shows up in the dropdown list, but not "UbuntuBig". Am I misunderstanding how the profile layer works? Is there something different I need to do in order to have a 2nd profile based on a dynamic profile? Is there some other way to create a profile that uses WSL?
claunia added the Resolution-By-DesignNeeds-Tag-Fix labels 2026-01-30 23:51:38 +00:00
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 Needs-Tag-Fix 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#4600
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?