Extension does not pick up PowerShell LTS msix installation
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- tooling
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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'!
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.9k
- Forks
- 550
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de PowerShell/vscode-powershell
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
PowerShell/vscode-powershell#5656 ·
-
[aw] Agentic Issue Triage failedAbiertoagentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
PowerShell/vscode-powershell#5615 · 1 comentario ·
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
PowerShell/vscode-powershell#5607 ·
-
[aw] Agentic Issue Triage failedAbiertoagentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
PowerShell/vscode-powershell#5599 · 3 comentarios ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
PowerShell/vscode-powershell#5592 · 2 comentarios · 1 reacción ·
Todos los issues de PowerShell/vscode-powershell
Issues similares
-
area-templates triage:bot-seen triage:needs-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
microsoft/aspire#22356 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Archiving an agent that is not loaded keeps its old updatedAtPosiblemente ocupada @luoph la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
content triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
contributor: external needs review severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
expo/expo#53642 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
JSPrismarine/JSPrismarine#3214 ·
Los mantenedores suelen responder en 1 día