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

How does the PowerShell Core function get the path of PowerShell Core? #949

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

Originally created by @hbjydev on GitHub (May 10, 2019).

The function in question is in Terminal/TerminalApp/CascadiaSettings.cpp (line 328). I wondered... Does it check for an environment variable called PowerShell, or is it looking for that in PATH?
I'm asking because I want to try and detect installed WSL environments to script in an automatic profile creation function for WSL distros.

Originally created by @hbjydev on GitHub (May 10, 2019). The function in question is in Terminal/TerminalApp/CascadiaSettings.cpp (line 328). I wondered... Does it check for an environment variable called `PowerShell`, or is it looking for that in PATH? I'm asking because I want to try and detect installed WSL environments to script in an automatic profile creation function for WSL distros.
claunia added the Issue-Question label 2026-01-30 22:12:12 +00:00
claunia commented 2026-01-30 22:12:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2019):

I believe what's happening in CascadiaSettings::_IsPowerShellCoreInstalled is we're trying to expand any environment variables that are in the path in programFileEnv, then appending "Powershell" to that path, and checking if pwsh.exe exists underneath that path.

I don't believe there's a %Powershell% we're checking for. We're actually just looking in either "%ProgramFiles%" or "%ProgramFiles(x86)%"

@zadjii-msft commented on GitHub (May 10, 2019): I believe what's happening in `CascadiaSettings::_IsPowerShellCoreInstalled` is we're trying to expand any environment variables that are in the path in `programFileEnv`, then appending "Powershell" to that path, and checking if `pwsh.exe` exists underneath that path. I don't believe there's a `%Powershell%` we're checking for. We're actually just looking in either `"%ProgramFiles%"` or `"%ProgramFiles(x86)%"`
claunia commented 2026-01-30 22:12:13 +00:00
Author
Owner
Copy Link

@hbjydev commented on GitHub (May 10, 2019):

Ah, so could I do something similar but look for %Windows\System32% and then ubuntu, wsl, debian, etc.?

@hbjydev commented on GitHub (May 10, 2019): Ah, so could I do something similar but look for `%Windows\System32%` and then `ubuntu`, `wsl`, `debian`, etc.?
claunia commented 2026-01-30 22:12:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2019):

Ah see, that's not where those actually live. The wsl exe's are actually App Execution Aliases, and they live in %localappdata%\Microsoft\WindowsApps\. Note that all app execution aliases live there, not just the WSL distros.

@zadjii-msft commented on GitHub (May 10, 2019): Ah see, that's not where those actually live. The wsl exe's are actually App Execution Aliases, and they live in `%localappdata%\Microsoft\WindowsApps\`. Note that _all_ app execution aliases live there, not just the WSL distros.
claunia commented 2026-01-30 22:12:13 +00:00
Author
Owner
Copy Link

@hbjydev commented on GitHub (May 10, 2019):

Right. So going straight to the WSL exe's would be a bad idea then? 😅

@hbjydev commented on GitHub (May 10, 2019): Right. So going straight to the WSL exe's would be a bad idea then? 😅
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
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#949
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?