starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Azure Cloud Shell" and "Windows PowerShell" cannot be removed from list of profiles #8298

New Issue
Closed
opened 2026-01-31 01:25:54 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:25:54 +00:00
Owner
Copy Link

Originally created by @davkean on GitHub (May 20, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.836]
Windows Terminal version: 1.0.1401.0

Steps to reproduce

  1. Open Settings
  2. Delete Windows Power Shelll and Azure Cloud Shell from the list of profiles and save
  3. Go back to Terminal

Expected behavior

No Windows Power Shell or Azure Cloud Shell in the profiles

Actual behavior

Both are still listed. If I open up settings again, Azure Cloud Shell has been added back:

,
      {
          "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
          "hidden": false,
          "name": "Azure Cloud Shell",
          "source": "Windows.Terminal.Azure"
      }

Powershell isn't listed, but still exists in the profile list.

Originally created by @davkean on GitHub (May 20, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.836] Windows Terminal version: 1.0.1401.0 ``` # Steps to reproduce 1. Open Settings 2. Delete Windows Power Shelll and Azure Cloud Shell from the list of profiles and save 3. Go back to Terminal # Expected behavior No Windows Power Shell or Azure Cloud Shell in the profiles # Actual behavior Both are still listed. If I open up settings again, Azure Cloud Shell has been added back: ``` , { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ``` Powershell isn't listed, but still exists in the profile list.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:25:54 +00:00
claunia commented 2026-01-31 01:25:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2020):

So, we have a bit of documentation on this;

https://docs.microsoft.com/en-us/windows/terminal/dynamic-profiles#prevent-a-profile-from-being-generated

https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#hide-a-profile-from-the-dropdown

Right now, the Windows PowerShell profile is being inherited from the default settings file. Your settings apply as overrides to the defaults. We’ll try to make this clearer in the documentation.

@DHowett commented on GitHub (May 20, 2020): So, we have a bit of documentation on this; https://docs.microsoft.com/en-us/windows/terminal/dynamic-profiles#prevent-a-profile-from-being-generated https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#hide-a-profile-from-the-dropdown Right now, the Windows PowerShell profile is being _inherited_ from the default settings file. Your settings apply as overrides to the defaults. We’ll try to make this clearer in the documentation.
claunia commented 2026-01-31 01:25:56 +00:00
Author
Owner
Copy Link

@davkean commented on GitHub (May 20, 2020):

Is this supposed to cause the PowerShell terminal to be hidden?

"disabledProfileSources": [ "Windows.Terminal.Wsl", "Windows.Terminal.Azure", "Windows.Terminal.PowershellCore" ],

Because while it works for the Azure one, the PowerShell one continues to show.

(By the way, do you own own search for the Terminal docs? It returns zero results regardless of search term)

@davkean commented on GitHub (May 20, 2020): Is this supposed to cause the PowerShell terminal to be hidden? ``` "disabledProfileSources": [ "Windows.Terminal.Wsl", "Windows.Terminal.Azure", "Windows.Terminal.PowershellCore" ], ``` Because while it works for the Azure one, the PowerShell one continues to show. (By the way, do you own own search for the Terminal docs? It returns zero results regardless of search term)
claunia commented 2026-01-31 01:25:56 +00:00
Author
Owner
Copy Link

@davkean commented on GitHub (May 20, 2020):

Filed https://github.com/MicrosoftDocs/terminal/issues/19 for the doc issue.

@davkean commented on GitHub (May 20, 2020): Filed https://github.com/MicrosoftDocs/terminal/issues/19 for the doc issue.
claunia commented 2026-01-31 01:25:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2020):

I believe that’s because they only recently went up. If not, I’ll have to take it up with the docs team... we don’t own that bit of infrastructure :/

Right now, the Windows PowerShell profile is being inherited from the default settings file. Your settings apply as overrides to the defaults. You’ll need to add a block that sets hidden to true for that profile. We originally tried to explain that by slapping down a comment that said “TO HIDE THIS PROFILE SET THE FOLLOWING BOOLEAN TO TRUE”, but we realized that people weren’t reading it.

@DHowett commented on GitHub (May 20, 2020): I believe that’s because they only recently went up. If not, I’ll have to take it up with the docs team... we don’t own that bit of infrastructure :/ Right now, the Windows PowerShell profile is being inherited from the default settings file. Your settings apply as overrides to the defaults. You’ll need to add a block that sets `hidden` to `true` for that profile. We originally tried to explain that by slapping down a comment that said “TO HIDE THIS PROFILE SET THE FOLLOWING BOOLEAN TO TRUE”, but we realized that people weren’t reading it.
claunia commented 2026-01-31 01:25:56 +00:00
Author
Owner
Copy Link

@davkean commented on GitHub (May 20, 2020):

I suppose what's confusing me at this point, was that the Azure Cloud one keeps getting added back to my personal settings. The PowerShell shell one isn't, So at this point its very unobvious how to hide the PowerShell without getting Terminal to recreate the settings.

@davkean commented on GitHub (May 20, 2020): I suppose what's confusing me at this point, was that the Azure Cloud one keeps getting added back to my personal settings. The PowerShell shell one isn't, So at this point its very unobvious how to hide the PowerShell without getting Terminal to recreate the settings.
claunia commented 2026-01-31 01:25:57 +00:00
Author
Owner
Copy Link

@davkean commented on GitHub (May 20, 2020):

To resolve this situation for those that hit this:

  • Held down ALT and Click Settings. This opens the default settings file.
  • Copied the PowerShell entry from it and into my personal settings
  • Marked it as hidden.

The Azure Cloud Shell just kept getting recreated in my personal settings so that was as easy as marking it has hidden.

@davkean commented on GitHub (May 20, 2020): To resolve this situation for those that hit this: - Held down ALT and Click Settings. This opens the default settings file. - Copied the PowerShell entry from it and into my personal settings - Marked it as hidden. The Azure Cloud Shell just kept getting recreated in my personal settings so that was as easy as marking it has hidden.
claunia commented 2026-01-31 01:25:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2020):

That's fair feedback.

Add this:

{                                                     
    /* Windows PowerShell - hidden */                 
    "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", 
    "hidden": true                                    
},

We're tracking making this a dynamic (and therefore detectable and supressable) generator in #5482.

I've got it on my personal backlog to make Terminal remember which ones it generated so if you actively delete one it just won't come back. We were a bit averse to doing this before we had a settings UI because it would've been totally undiscoverable, but ... a blob getting written back into your json every time is ironically less discoverable.

@DHowett commented on GitHub (May 20, 2020): That's fair feedback. Add this: ```json { /* Windows PowerShell - hidden */ "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "hidden": true }, ``` We're tracking making this a dynamic (and therefore detectable and supressable) generator in #5482. I've got it on my personal backlog to make Terminal _remember which ones it generated_ so if you actively delete one it just won't come back. We were a bit averse to doing this before we had a settings UI because it would've been totally undiscoverable, but ... a blob getting written back into your json every time is ironically _less_ discoverable.
claunia commented 2026-01-31 01:25:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2020):

Whoops, you beat me to it. Sorry.

@DHowett commented on GitHub (May 20, 2020): Whoops, you beat me to it. Sorry.
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#8298
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?