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

Custom default profile not loaded correctly when terminal window opened via cmd #20878

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

Originally created by @flriancu on GitHub (Nov 23, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.22621.2715

Other Software

miniforge installed via winget install CondaForge.Miniforge3

Steps to reproduce

  • install miniforge via winget install CondaForge.Miniforge3
  • open the start menu, then a miniforge prompt, then run where python and make a note of the parent directory of the miniforge Python; in my case it's %localappdata%\miniforge3
  • open windows terminal's settings.json file, and add the following snippet at the beginning of profiles.list; if needed, change the location of Python depending on where it was installed by winget 
                {
                "commandline": "powershell -ExecutionPolicy ByPass -NoExit -Command \"& '%localappdata%\\miniforge3\\shell\\condabin\\conda-hook.ps1' ; conda activate '%localappdata%\\miniforge3'\"",
                "guid": "{ea174bc0-cf98-45f4-a70b-21fbff2bbfc6}",
                "hidden": false,
                "icon": "%localappdata%\\miniforge3\\Menu\\console_shortcut.ico",
                "name": "Miniforge PowerShell"
            },
            {
                "commandline": "cmd.exe /K %localappdata%\\miniforge3\\Scripts\\activate.bat %localappdata%\\miniforge3",
                "guid": "{f77912a4-f18f-4022-a6fe-a28e9c46da90}",
                "hidden": false,
                "icon": "%localappdata%\\miniforge3\\Menu\\console_shortcut.ico",
                "name": "Miniforge"
            },
  • save the settings.json file
  • go to settings -> startup -> default profile and choose Miniforge
  • go to settings -> startup -> default terminal application and choose Windows Terminal
  • close the terminal

Expected Behavior

  • expected and actual behavior: when opening a terminal window via wt, the default profile is loaded:
    image
  • expected behavior: when opening a terminal window via cmd, the default profile is loaded

Actual Behavior

  • when opening a terminal window via cmd, the following happens:
    image
    I'm not sure whether the default profile should be "Miniforge" or "Command Prompt" in this case.
Originally created by @flriancu on GitHub (Nov 23, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.22621.2715 ### Other Software miniforge installed via `winget install CondaForge.Miniforge3` ### Steps to reproduce - install miniforge via `winget install CondaForge.Miniforge3` - open the start menu, then a miniforge prompt, then run `where python` and make a note of the parent directory of the miniforge Python; in my case it's `%localappdata%\miniforge3` - open windows terminal's settings.json file, and add the following snippet at the beginning of `profiles.list`; if needed, change the location of Python depending on where it was installed by winget ```json { "commandline": "powershell -ExecutionPolicy ByPass -NoExit -Command \"& '%localappdata%\\miniforge3\\shell\\condabin\\conda-hook.ps1' ; conda activate '%localappdata%\\miniforge3'\"", "guid": "{ea174bc0-cf98-45f4-a70b-21fbff2bbfc6}", "hidden": false, "icon": "%localappdata%\\miniforge3\\Menu\\console_shortcut.ico", "name": "Miniforge PowerShell" }, { "commandline": "cmd.exe /K %localappdata%\\miniforge3\\Scripts\\activate.bat %localappdata%\\miniforge3", "guid": "{f77912a4-f18f-4022-a6fe-a28e9c46da90}", "hidden": false, "icon": "%localappdata%\\miniforge3\\Menu\\console_shortcut.ico", "name": "Miniforge" }, ``` - save the settings.json file - go to settings -> startup -> default profile and choose `Miniforge` - go to settings -> startup -> default terminal application and choose `Windows Terminal` - close the terminal ### Expected Behavior - expected and actual behavior: when opening a terminal window via `wt`, the default profile is loaded: ![image](https://github.com/microsoft/terminal/assets/8483893/f99607f5-99e5-49d9-9023-1d713c864d09) - expected behavior: when opening a terminal window via `cmd`, the default profile is loaded ### Actual Behavior - when opening a terminal window via `cmd`, the following happens: ![image](https://github.com/microsoft/terminal/assets/8483893/12a3b7ae-54e2-42f3-bb03-3128f979f6be) I'm not sure whether the default profile should be "Miniforge" or "Command Prompt" in this case.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:26:37 +00:00
claunia commented 2026-01-31 07:26:39 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 23, 2023):

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 (Nov 23, 2023): 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: - [Opening Windows Terminal by default doesn't pick the right profile (#10228)](https://github.com/microsoft/terminal/issues/10228), similarity score: 0.84 - [When default profile is set to Command Prompt, "Open in Windows Terminal" uses cmd.exe in current folder (#12126)](https://github.com/microsoft/terminal/issues/12126), similarity score: 0.82 - [Default profile should be powershell, rather than cmd (#431)](https://github.com/microsoft/terminal/issues/431), similarity score: 0.81 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:26:39 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 27, 2023):

Unless I misunderstood your issue description, I believe that this is intentional behavior. cmd is not an alias for wt and running cmd from Win+R executes exactly the given command. When Windows Terminal then opens to display the contents of your command it doesn't have any influence anymore over what that command does. Try running

cmd.exe /K %localappdata%\\miniforge3\\Scripts\\activate.bat %localappdata%\\miniforge3

from Win+R instead. That should match with your custom profile since the command lines match.

@lhecker commented on GitHub (Nov 27, 2023): Unless I misunderstood your issue description, I believe that this is intentional behavior. `cmd` is not an alias for `wt` and running `cmd` from Win+R executes exactly the given command. When Windows Terminal then opens to display the contents of your command it doesn't have any influence anymore over what that command does. Try running ``` cmd.exe /K %localappdata%\\miniforge3\\Scripts\\activate.bat %localappdata%\\miniforge3 ``` from Win+R instead. That should match with your custom profile since the command lines match.
claunia commented 2026-01-31 07:26:39 +00:00
Author
Owner
Copy Link

@flriancu commented on GitHub (Dec 3, 2023):

There was a major misunderstanding on my part. I was under the impression that the profile listed in bold font in the drop-down menu was the profile of the active tab. Of course, it actually refers to the default profile 😄 Thanks for your patience, I'll close the issue.

@flriancu commented on GitHub (Dec 3, 2023): There was a major misunderstanding on my part. I was under the impression that the profile listed in bold font in the drop-down menu was the profile of the active tab. Of course, it actually refers to the default profile 😄 Thanks for your patience, I'll close the issue.
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-Attention Needs-Triage
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#20878
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?