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 will not honor to seperate PowerShell 7.2 preview x86 or x64 in UI / JSON #12565

New Issue
Closed
opened 2026-01-31 03:18:56 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:18:56 +00:00
Owner
Copy Link

Originally created by @Karl-WE on GitHub (Feb 13, 2021).

Originally assigned to: @DHowett on GitHub.

Environment

Windows build number: Windows 10 b21131
Windows Terminal version (if applicable): Terminal / Terminal preview (as current at 13 Feb. 2021)
Terminal: 1.5.1411.0
Terminal Preview: 1.6.10412.0

Any other software?
PowerShell Preview 7.2 Preview 2 x86 MSI
PowerShell Preview 7.2 Preview 3 x64 MSI

Does not affect Powershell 7.1 release x86 / x64

Steps to reproduce

Have Terminal / Terminal Preview and PowerShell 7.2 preview 2 x86 installed via MSI.
Install PowerShell 7.2 preview 3 x64 installed via MSI.

Expected behavior

Terminal should detect 2 instances of PowerShell 7.2 Preview and implement it in new shell dropdown with the specific architecture like PowerShell 7.2 Preview 2 (x86) and PowerShell 7.2 Preview 3 x64

Actual behavior

It will only detect the first Powershell 7.2

Proposal for technical implementation:

you can check the version in get-childitem version string, when generating / updating the json
you can check the programfiles path of the pwsh.exe to determine the architecture and add it to the caption.

Originally created by @Karl-WE on GitHub (Feb 13, 2021). Originally assigned to: @DHowett on GitHub. # Environment ```none Windows build number: Windows 10 b21131 Windows Terminal version (if applicable): Terminal / Terminal preview (as current at 13 Feb. 2021) Terminal: 1.5.1411.0 Terminal Preview: 1.6.10412.0 ``` Any other software? [PowerShell Preview 7.2 Preview 2 x86 MSI](https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.3/PowerShell-7.2.0-preview.2-win-x86.msi) [PowerShell Preview 7.2 Preview 3 x64 MSI](https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.3/PowerShell-7.2.0-preview.3-win-x64.msi) Does not affect Powershell 7.1 release x86 / x64 # Steps to reproduce Have Terminal / Terminal Preview and PowerShell 7.2 preview 2 x86 installed via MSI. Install PowerShell 7.2 preview 3 x64 installed via MSI. # Expected behavior Terminal should detect 2 instances of PowerShell 7.2 Preview and implement it in new shell dropdown with the specific architecture like PowerShell 7.2 Preview 2 (x86) and PowerShell 7.2 Preview 3 x64 # Actual behavior It will only detect the first Powershell 7.2 # Proposal for technical implementation: you can check the version in get-childitem version string, when generating / updating the json you can check the programfiles path of the pwsh.exe to determine the architecture and add it to the caption.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:18:56 +00:00
claunia commented 2026-01-31 03:18:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 14, 2021):

Curious! We do actually enumerate the instances in the Program Files (x86) directory and assign them separate names.

Can you share your settings.json? It should contain a couple generated profile snippets.

My menu looks like this after I install the cross-architecture x86 version alongside preview and stable:

image

            {
                "guid": "{a3a2e83a-884a-5379-baa8-16f193a13b21}",
                "hidden": false,
                "name": "PowerShell 7 Preview",
                "source": "Windows.Terminal.PowershellCore"
            },
            {
                "guid": "{d6ebd50a-738a-58da-95a8-41e7782f6f7e}",
                "hidden": false,
                "name": "PowerShell 7 Preview (x86)",
                "source": "Windows.Terminal.PowershellCore"
            },
            {
                "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "name": "PowerShell",
                "source": "Windows.Terminal.PowershellCore"
            },

(commandlines are, of course, autogenerated.)

PS> gci \program` files,\program` files` `(x86`)  -filter pwsh.exe -recu | select -exp fullname
C:\Program Files\PowerShell\7\pwsh.exe
C:\Program Files\PowerShell\7-preview\pwsh.exe
C:\Program Files (x86)\PowerShell\7-preview\pwsh.exe
@DHowett commented on GitHub (Feb 14, 2021): Curious! We do actually enumerate the instances in the `Program Files (x86)` directory and assign them separate names. Can you share your settings.json? It should contain a couple generated profile snippets. My menu looks like this after I install the cross-architecture x86 version alongside preview and stable: ![image](https://user-images.githubusercontent.com/189190/107866122-18443a00-6e22-11eb-87ea-f882b815d64d.png) ``` { "guid": "{a3a2e83a-884a-5379-baa8-16f193a13b21}", "hidden": false, "name": "PowerShell 7 Preview", "source": "Windows.Terminal.PowershellCore" }, { "guid": "{d6ebd50a-738a-58da-95a8-41e7782f6f7e}", "hidden": false, "name": "PowerShell 7 Preview (x86)", "source": "Windows.Terminal.PowershellCore" }, { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "name": "PowerShell", "source": "Windows.Terminal.PowershellCore" }, ``` (commandlines are, of course, autogenerated.) ``` PS> gci \program` files,\program` files` `(x86`) -filter pwsh.exe -recu | select -exp fullname C:\Program Files\PowerShell\7\pwsh.exe C:\Program Files\PowerShell\7-preview\pwsh.exe C:\Program Files (x86)\PowerShell\7-preview\pwsh.exe ```
claunia commented 2026-01-31 03:18:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 18, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 18, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 03:18:57 +00:00
Author
Owner
Copy Link

@Karl-WE commented on GitHub (Feb 18, 2021):

I have to review this.

@Karl-WE commented on GitHub (Feb 18, 2021): I have to review this.
claunia commented 2026-01-31 03:18:57 +00:00
Author
Owner
Copy Link

@Karl-WE commented on GitHub (Feb 19, 2021):

Hi @DHowett I have tested it again with same PShell versions installed preview and release in x64 and x86

Cannot repro in
Windows Terminal v1.5.10411.0
Windows Terminal Preview v1.6.10412.0

image

@Karl-WE commented on GitHub (Feb 19, 2021): Hi @DHowett I have tested it again with same PShell versions installed preview and release in x64 and x86 Cannot repro in Windows Terminal v1.5.10411.0 Windows Terminal Preview v1.6.10412.0 ![image](https://user-images.githubusercontent.com/45657752/108487169-3df89580-729f-11eb-951f-ae36b88e5d18.png)
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#12565
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?