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

Terminal doesn't generate PowerShell 7 profile #12156

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

Originally created by @akefirad on GitHub (Jan 23, 2021).

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.4.3242.0

PowerShell: 7.1.1

Steps to reproduce

Note: probably this is specific to my system. I don't expect it to be easily reproducible. Please guide me on how to dig deeper.
At some point, I found that "PowerShell Core" profile is gone on Terminal (even though settings.json has the profile).
I uninstalled/reinstalled both Terminal and PowerShell, but it didn't solve the issue. As matter of fact, with new installation, Terminal doesn't have PowerShell Core profile (with source Windows.Terminal.PowershellCore).
I also tried to add it manually to settings.json, but it didn't help either. (I'm not quite sure if I understand guid field properly, is it some specific value or a random one that I can regenerate?):

{
  "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
  "name": "PowerShell Core",
  "source": "Windows.Terminal.PowershellCore",
  "hidden": false
}

For the record, everything in settings.json (e.g. hide profiles) works just fine.

Expected behavior

As the documentation say, Terminal should automatically generate PowerShell Core profile.

Actual behavior

Terminal doesn't generate PowerShell Core profile.

Originally created by @akefirad on GitHub (Jan 23, 2021). # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.4.3242.0 PowerShell: 7.1.1 ``` # Steps to reproduce Note: probably this is specific to my system. I don't expect it to be easily reproducible. Please guide me on how to dig deeper. At some point, I found that "PowerShell Core" profile is gone on Terminal (even though `settings.json` has the profile). I uninstalled/reinstalled both Terminal and PowerShell, but it didn't solve the issue. As matter of fact, with new installation, Terminal doesn't have `PowerShell Core` profile (with source `Windows.Terminal.PowershellCore`). I also tried to add it manually to `settings.json`, but it didn't help either. (I'm not quite sure if I understand `guid` field properly, is it some specific value or a random one that I can regenerate?): ```json { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "name": "PowerShell Core", "source": "Windows.Terminal.PowershellCore", "hidden": false } ``` For the record, everything in `settings.json` (e.g. hide profiles) works just fine. # Expected behavior As the documentation say, Terminal should automatically generate `PowerShell Core` profile. # Actual behavior Terminal doesn't generate `PowerShell Core` profile.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:07:38 +00:00
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 23, 2021):

Where did you install PowerShell?

@DHowett commented on GitHub (Jan 23, 2021): Where did you install PowerShell?
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 23, 2021):

(And with what installation method?)

@DHowett commented on GitHub (Jan 23, 2021): (And with what installation method?)
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@akefirad commented on GitHub (Jan 23, 2021):

Ah good point, forgot to mention. Due to problems with spaces in the default installation path, I installed it in C:\Programs\. I downloaded the msi installer ftom the release page.

@akefirad commented on GitHub (Jan 23, 2021): Ah good point, forgot to mention. Due to problems with spaces in the default installation path, I installed it in `C:\Programs\`. I downloaded the msi installer ftom the release page.
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 23, 2021):

Ah.

Terminal detects installations of powershell in the typical places. You can safely create your own profile for it, just set a commandline and omit the source (the presence of a “source” property means that you aren’t the creator of that profile, so Terminal will hide it if it can’t figure out what it is).

As an aside ... what problems did you have with spaces in the default path? I suspect that it’s the default because it works well for almost all use cases, so I’m somewhat surprised.

@DHowett commented on GitHub (Jan 23, 2021): Ah. Terminal detects installations of powershell in the typical places. You can safely create your own profile for it, just set a commandline and _omit the `source`_ (the presence of a “source” property means that you aren’t the creator of that profile, so Terminal will hide it if it can’t figure out what it is). As an aside ... what problems did you have with spaces in the default path? I suspect that it’s the default _because it works well for almost all use cases_, so I’m somewhat surprised.
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 23, 2021):

The guid can be made up or totally omitted at your leisure. We’re reducing the number of times you have to see it or care about it with every release.

@DHowett commented on GitHub (Jan 23, 2021): The guid can be made up or totally omitted at your leisure. We’re reducing the number of times you have to see it or care about it with every release.
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@akefirad commented on GitHub (Jan 23, 2021):

I see. Got it. Thanks. About the problem with spaces, I tried to setup ssh ProxyCommand and couldn't figure out how to do it with the default path which has spaces. The catch is OpenSSH requires the full path to the command (in this case pwsh.exe. Does that make sense?

@akefirad commented on GitHub (Jan 23, 2021): I see. Got it. Thanks. About the problem with spaces, I tried to setup ssh ProxyCommand and couldn't figure out how to do it with the default path which has spaces. The catch is OpenSSH requires the full path to the command (in this case `pwsh.exe`. Does that make sense?
claunia commented 2026-01-31 03:07:39 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Feb 1, 2021):

You have to use quotes around the file path, PSReadline will help you navigate with the tab button to get it to successfully quote it.

@WSLUser commented on GitHub (Feb 1, 2021): You have to use quotes around the file path, PSReadline will help you navigate with the tab button to get it to successfully quote it.
claunia commented 2026-01-31 03:07:40 +00:00
Author
Owner
Copy Link

@akefirad commented on GitHub (Feb 1, 2021):

I'm setting the path in .ssh/config file. And quotes didn't help, at least I couldn't get it working.

@akefirad commented on GitHub (Feb 1, 2021): I'm setting the path in `.ssh/config` file. And quotes didn't help, at least I couldn't get it working.
claunia commented 2026-01-31 03:07:40 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Feb 4, 2021):

https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_server_configuration should help you. Also C:\Program Files\OpenSSH\ is the default path for stand-alone installations (Chocolatey also honors this path during install.)

@WSLUser commented on GitHub (Feb 4, 2021): https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_server_configuration should help you. Also `C:\Program Files\OpenSSH\` is the default path for stand-alone installations (Chocolatey also honors this path during install.)
claunia commented 2026-01-31 03:07:40 +00:00
Author
Owner
Copy Link

@akefirad commented on GitHub (Feb 4, 2021):

ProxyCommand is a client configuration thing. I'm not sure what should I read from the link (it's about server configuration). What I was trying to do is to configure the ProxyCommand of my .ssh/config (client). Something like this:

ProxyCommand ssh proxyserver -W [%h]:%p

Apparently the above has a problem; ssh must be absolute path (whatever the path of ssh is). I learned that whatever command is used, the path must be absolute on Windows. And I wanted to use pwsh.exe and the default path contains some space. Now the question is what's the correct way to configure the ProxyCommand with a command that has space in its absolute path (I forgot the exact path, I'm not on my Windows machine atm):

ProxyCommand C:\\Program Files\\PowerShell\\7.0.0\pwsh.exe blah blah blah # this doesn't work!
@akefirad commented on GitHub (Feb 4, 2021): `ProxyCommand` is a client configuration thing. I'm not sure what should I read from the link (it's about server configuration). What I was trying to do is to configure the `ProxyCommand` of my `.ssh/config` (client). Something like this: ``` ProxyCommand ssh proxyserver -W [%h]:%p ``` Apparently the above has a problem; `ssh` must be absolute path (whatever the path of `ssh` is). I learned that whatever command is used, the path must be absolute on Windows. And I wanted to use `pwsh.exe` and the default path contains some space. Now the question is what's the correct way to configure the `ProxyCommand` with a command that has space in its absolute path (I forgot the exact path, I'm not on my Windows machine atm): ``` ProxyCommand C:\\Program Files\\PowerShell\\7.0.0\pwsh.exe blah blah blah # this doesn't work! ```
claunia commented 2026-01-31 03:07:40 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Feb 9, 2021):

the path must be absolute on Windows.

That sounds like you didn't set up the env var for ssh (though if adding the absolute path helps the config work, then keep it). You'd find that without the env var being set, you'd be unable to run ssh from any other directory except directly where the exe exists.

@WSLUser commented on GitHub (Feb 9, 2021): > the path must be absolute on Windows. That sounds like you didn't set up the env var for ssh (though if adding the absolute path helps the config work, then keep it). You'd find that without the env var being set, you'd be unable to run ssh from any other directory except directly where the exe exists.
claunia commented 2026-01-31 03:07:41 +00:00
Author
Owner
Copy Link

@akefirad commented on GitHub (Feb 15, 2021):

I don't quite remember. If I'm not mistaken it was an issue that could be solved only by using absolute paths. Anyway. Thanks for the support.

@akefirad commented on GitHub (Feb 15, 2021): I don't quite remember. If I'm not mistaken it was an issue that could be solved only by using absolute paths. Anyway. Thanks for the support.
claunia commented 2026-01-31 03:07:41 +00:00
Author
Owner
Copy Link

@wngtk commented on GitHub (Mar 30, 2023):

I have the same problem with you. but I fixed it through reset my settings.

delete your settings.json file

https://learn.microsoft.com/en-us/windows/terminal/troubleshooting#how-do-i-reset-my-settings-in-windows-terminal-back-to-the-default-settings

@wngtk commented on GitHub (Mar 30, 2023): I have the same problem with you. but I fixed it through reset my settings. > delete your [settings.json file](https://learn.microsoft.com/en-us/windows/terminal/install#settings-json-file) https://learn.microsoft.com/en-us/windows/terminal/troubleshooting#how-do-i-reset-my-settings-in-windows-terminal-back-to-the-default-settings
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-Attention Needs-Tag-Fix 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#12156
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?