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

Bug Report - linking powershell 6.2.1 and 7.0.0 to Terminal side by side is not possible #2238

New Issue
Closed
opened 2026-01-30 22:50:19 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:50:19 +00:00
Owner
Copy Link

Originally created by @Karl-WE on GitHub (Jun 25, 2019).

Due to a technical limitation in Windows and limitation in profiles.json as described in #1617 it is not possible to use Terminal with 2 Powershell core versions side by side

Environment

Windows build number: 18362.x (1903)
Windows Terminal version (if applicable): 0.2.1715.0

Any other software?
Powershell 6.2.1 Core -
Installpath: C:\Program Files\PowerShell\6-preview
Executable: pwsh.exe

Powershell 7.0.0 Core preview -
Installpath C:\Program Files\PowerShell\7-preview
Executable: pwsh.exe

Steps to reproduce

Install PoSh 6.2.1
in PoSh 6.2.1 run update-module (eventually set-executionpolicy remotesigned

Install PoSh 7.0.0 preview
iex "& { $(irm https://aka.ms/install-powershell.ps1) } -UseMSI -preview"

references:
https://www.thomasmaurer.ch/2019/03/how-to-install-and-update-powershell-6/
https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-windows?view=powershell-6

Add a new block in section "profiles" to profiles.json

   {
        "acrylicOpacity" : 0.75,
        "closeOnExit" : true,
        "colorScheme" : "Solarized Dark",
        "commandline" : "pwsh.exe",
        "cursorColor" : "#FFFFFF",
        "cursorShape" : "bar",
        "fontFace" : "Consolas",
        "fontSize" : 12,
        "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
        "historySize" : 9001,
        "icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png",
        "name" : "Windows PowerShell 6.2.1 Core",
        "padding" : "5, 5, 5, 5",
        "snapOnInput" : true,
        "startingDirectory" : "%USERPROFILE%",
        "useAcrylic" : true
    },

   {
        "acrylicOpacity" : 0.75,
        "closeOnExit" : true,
        "colorScheme" : "Solarized Light",
        "commandline" : "pwsh.exe",
        "cursorColor" : "#FFFFFF",
        "cursorShape" : "bar",
        "fontFace" : "Consolas",
        "fontSize" : 12,
        "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
        "historySize" : 9001,
        "icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png",
        "name" : "Windows PowerShell 7.0.0 Core Preview",
        "padding" : "5, 5, 5, 5",
        "snapOnInput" : true,
        "startingDirectory" : "%USERPROFILE%",
        "useAcrylic" : true
    },

Expected behavior

Terminal cannot - technically correct - distinguish between both pwsh.exe when both are added to Windows $env:path

Actual behavior

Terminal will not open PoSh 7.x due to this limitation

Originally created by @Karl-WE on GitHub (Jun 25, 2019). Due to a **technical** limitation in Windows and limitation in profiles.json as described in #1617 it is not possible to use Terminal with 2 Powershell core versions side by side # Environment Windows build number: 18362.x (1903) Windows Terminal version (if applicable): 0.2.1715.0 Any other software? Powershell 6.2.1 Core - Installpath: C:\Program Files\PowerShell\6-preview Executable: pwsh.exe Powershell 7.0.0 Core preview - Installpath C:\Program Files\PowerShell\7-preview Executable: pwsh.exe # Steps to reproduce Install PoSh 6.2.1 in PoSh 6.2.1 run update-module (eventually set-executionpolicy remotesigned Install PoSh 7.0.0 preview iex "& { $(irm https://aka.ms/install-powershell.ps1) } -UseMSI -preview" references: https://www.thomasmaurer.ch/2019/03/how-to-install-and-update-powershell-6/ https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-windows?view=powershell-6 Add a new block in section "profiles" to profiles.json { "acrylicOpacity" : 0.75, "closeOnExit" : true, "colorScheme" : "Solarized Dark", "commandline" : "pwsh.exe", "cursorColor" : "#FFFFFF", "cursorShape" : "bar", "fontFace" : "Consolas", "fontSize" : 12, "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "historySize" : 9001, "icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png", "name" : "Windows PowerShell 6.2.1 Core", "padding" : "5, 5, 5, 5", "snapOnInput" : true, "startingDirectory" : "%USERPROFILE%", "useAcrylic" : true }, { "acrylicOpacity" : 0.75, "closeOnExit" : true, "colorScheme" : "Solarized Light", "commandline" : "pwsh.exe", "cursorColor" : "#FFFFFF", "cursorShape" : "bar", "fontFace" : "Consolas", "fontSize" : 12, "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "historySize" : 9001, "icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png", "name" : "Windows PowerShell 7.0.0 Core Preview", "padding" : "5, 5, 5, 5", "snapOnInput" : true, "startingDirectory" : "%USERPROFILE%", "useAcrylic" : true }, # Expected behavior Terminal cannot - technically correct - distinguish between both pwsh.exe when both are added to Windows $env:path # Actual behavior Terminal will not open PoSh 7.x due to this limitation
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-30 22:50:20 +00:00
claunia commented 2026-01-30 22:50:20 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 25, 2019):

Did you try changing the guid? change a few letters of any, just don't keep them the same?

@Shorotshishir commented on GitHub (Jun 25, 2019): Did you try changing the `guid`? change a few letters of any, just don't keep them the same?
claunia commented 2026-01-30 22:50:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 25, 2019):

Just change the guid. Also, just set the commandline to the actual path to pwsh.exe? I don't get it. Just set the path to C:\program files . . ., but escaped properly for JSON.

@DHowett-MSFT commented on GitHub (Jun 25, 2019): Just change the guid. Also, just set the commandline to the actual path to pwsh.exe? I don't get it. Just set the path to `C:\program files . . .`, but escaped properly for JSON.
claunia commented 2026-01-30 22:50:21 +00:00
Author
Owner
Copy Link

@Karl-WE commented on GitHub (Jun 27, 2019):

I did try to name the exes differently. Did not work for me. probably due the same ID

@Shorotshishir

For the GUID, can it be anything or where do I get it from?

For the path thanks for clarifing this in #1617 JSON is not something I usually see / do.

@Karl-WE commented on GitHub (Jun 27, 2019): I did try to name the exes differently. Did not work for me. probably due the same ID @Shorotshishir For the GUID, can it be anything or where do I get it from? For the path thanks for clarifing this in #1617 JSON is not something I usually see / do.
claunia commented 2026-01-30 22:50:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

from powershell, type new-guid .. or run "guidgen", or just change one of the hex digits in the guid to another one

@DHowett-MSFT commented on GitHub (Jun 27, 2019): from powershell, type `new-guid` .. or run "guidgen", or just change one of the hex digits in the guid to another one
claunia commented 2026-01-30 22:50:22 +00:00
Author
Owner
Copy Link

@Karl-WE commented on GitHub (Jun 27, 2019):

Thank you!

@Karl-WE commented on GitHub (Jun 27, 2019): Thank you!
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
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#2238
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?