Extension does not pick up PowerShell LTS msix installation
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- tooling
调研方向
Start from the warning in the logs: the powerShellDefaultVersion setting pointing at a WindowsApps pwsh.exe path is reported as not found, and the extension falls back to Windows PowerShell 5.1. Find where the extension resolves that setting and enumerates installed PowerShell versions, then check whether it handles the MSIX/WindowsApps path and the per-user alias. Reproducing needs a Windows machine with PowerShell LTS 7.6.10 installed via winget. Done when the extension selects that install and the language status stops spinning.
由索引模型根据 Issue 内容生成。
描述
Prerequisites
- I have written a descriptive issue title.
- I have searched all open and closed issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
- If this is a security issue, I have read the security issue reporting guidance.
Summary
Neither the PowerShell extension nor the integrated terminal with a PowerShell shell picks up the PowerShell LTS msix installation. (7.6.10).
Instead of PowerShell 7, Windows PoweShell 5.1 was picked up.
Then setting the option
"powershell.powerShellDefaultVersion": "C:\\Program Files\\WindowsApps\\Microsoft.PowerShell-LTS_7.6.10.0_x64__8wekyb3d8bbwe\\pwsh.exe" generated the warning message:
2026-11-13 10:31:04.936 [warning] The 'powerShellDefaultVersion' setting was 'C:\Program Files\WindowsApps\Microsoft.PowerShell-LTS_7.6.10.0_x64__8wekyb3d8bbwe\pwsh.exe' but this was not found! Instead using first available installation 'Windows PowerShell (x64)' at 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe'!
Setting the option to the per-user alias resulted in the same warning.
The editor language status then keeps on spinning and the powershell extension never returns a prompt.
I checked both
& "$env:LOCALAPPDATA\Microsoft\WindowsApps\Microsoft.PowerShell-LTS_8wekyb3d8bbwe\pwsh.exe" -NoLogo -NoProfile -Command '$PSVersionTable.PSVersion' and
& "$env:ProgramFiles\WindowsApps\Microsoft.PowerShell-LTS_7.6.10.0_x64__8wekyb3d8bbwe\pwsh.exe" -NoLogo -NoProfile -Command '$PSVersionTable.PSVersion'
return the proper version from a terminal.
There seems to be a related problem with powershell profile discovery for Windows Terminal, see https://github.com/microsoft/terminal/issues/20028.
PowerShell Version
Name Value
---- -----
PSVersion 7.6.10
PSEdition Core
GitCommitId 7.6.10
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Name : ConsoleHost
Version : 7.6.10
InstanceId : 9d7b8d06-8e11-4757-b521-200e7f2677aa
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-GB
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
1.146.0
69047191fc427f2f92828279aae1d90d8eeda7ab
x64
Extension Version
[email protected]
Steps to Reproduce
PowerShell 7.6.9 was automatically updated to 7.7.0.
Uninstalled 7.7 via winget uninstall -- id Microsoft.PowerShell.
Reinstalled PowerShell 7.6.10 via winget install --id Microsoft.PowerShell --version 7.6.10.
This version is installed to $env:ProgramFiles\WindowsApps\Microsoft.PowerShell-LTS_7.6.10.0_x64__8wekyb3d8bbwe with a per-user alias in $env:LOCALAPPDATA\Microsoft\WindowsApps\Microsoft.PowerShell-LTS_8wekyb3d8bbwe.
Start vs code and open any PowerShell file.
Visuals
No response
Logs
2026-11-13 10:31:04.936 [warning] The 'powerShellDefaultVersion' setting was 'C:\Program Files\WindowsApps\Microsoft.PowerShell-LTS_7.6.10.0_x64__8wekyb3d8bbwe\pwsh.exe' but this was not found! Instead using first available installation 'Windows PowerShell (x64)' at 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe'!
- 主要语言
- TypeScript
- 星标
- 1.9k
- 派生
- 550
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
PowerShell/vscode-powershell 的其他 Issue
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 65/100
PowerShell/vscode-powershell#5656 ·
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 68/100
PowerShell/vscode-powershell#5615 · 1 条评论 ·
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 75/100
PowerShell/vscode-powershell#5607 ·
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 62/100
PowerShell/vscode-powershell#5599 · 3 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
PowerShell/vscode-powershell#5592 · 2 条评论 · 1 个 reaction ·
查看 PowerShell/vscode-powershell 的全部 Issue
相似的 Issue
-
area-templates triage:bot-seen triage:needs-human
难度 2/5 1-3 小时 新手友好度 75/100
microsoft/aspire#22356 · 1 条评论 ·
维护者通常 1 天内回复
-
Archiving an agent that is not loaded keeps its old updatedAt可能已有人在做 @luoph 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
content triage
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
contributor: external needs review severity: low
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
Enhancement
难度 2/5 1-3 小时 新手友好度 76/100
JSPrismarine/JSPrismarine#3214 ·
维护者通常 1 天内回复