Win11 26H2: user PATH (~3.6k) not applied to new processes — winget missing in cmd/PS 5.1/pwsh
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- cpp, powershell
- Área
- cli, operating-systems
Línea de trabajo
The report points to Windows environment handling and the winget PATH behavior, but names no source files, tests, or specific component that owns the missing user PATH merge. Start by checking whether this is an operating system behavior outside winget-cli's control, then trace how winget appends package paths. Done would require an agreed scope and a reproducible fix or documentation change covering the reported PATH limit.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
After a recent Windows 11 26H2 upgrade, new shells stop loading the user PATH from the registry, so winget and other user-scoped tools vanish from cmd, PowerShell 5.1, and PowerShell 7 even though App Installer and winget.exe are still installed.
Environment
- OS: Windows 11 26H2 (build 10.0.26300)
- App Installer / winget: Microsoft.DesktopAppInstaller 1.29.380 (package status OK)
winget.exeat%LOCALAPPDATA%\Microsoft\WindowsApps\winget.exeruns when invoked by full path (winget --version→ v1.29.380)- User
PATHin registry (HKCUEnvironment\Path): ~3,632 characters, includes%LOCALAPPDATA%\Microsoft\WindowsAppsand 13...\Microsoft\WinGet\Packages\...entries (typical winget portable install pattern without Developer Mode / admin Links layout)
Steps to reproduce
- Accumulate a large user
PATH(common with multiple winget portable/zip packages that each append a longWinGet\Packages\...segment). - Upgrade to Windows 11 26H2 (or open a new cmd / PowerShell 5.1 / pwsh session after upgrade).
- Run
where wingetin cmd orGet-Command wingetin PowerShell 5.1 or pwsh. - Compare
[Environment]::GetEnvironmentVariable('Path','User')(registry) vs$env:Pathin the same process.
Expected
- User
PATHfrom HKCU is merged into every new interactive shell (cmd, PowerShell 5.1, pwsh). wingetresolves via the App Execution Alias underWindowsAppswhen App Installer is installed.- If a platform limit applies, Windows should surface a clear error or warning when user
PATHcannot be applied — not silently drop the entire user block.
Actual
- Registry user
PATHlength ~3632; processPATHlength ~1326 (matches machine PATH only — user PATH not applied at all). where wingetin cmd: not found.Get-Command wingetin PowerShell 5.1 and pwsh: not found.- Direct invocation still works:
& "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget.exe" --version. - PowerShell profile import of
Microsoft.WinGet.CommandNotFoundfails at startup becauseValidateOS.psm1requiresGet-Command wingetto succeed.
Related
- winget-cli #3601 — PATH bloat from portable installs
- winget-cli #5557 — repeated WinGet package PATH entries vs 2047 limit
- winget troubleshooting: missing
%LOCALAPPDATA%\Microsoft\WindowsAppsin PATH (docs)
Ask
- OS: Fix or document behavior when user
PATHexceeds legacy limits — do not silently omit the entire user PATH from new processes. - winget: Default to Links/symlink layout where possible; warn when appending another
Packages\...segment would exceed safe PATH size; offer cleanup for duplicate or stale entries. - Visibility: A high-signal diagnostic (e.g.
winget doctoror Settings) when App Execution Aliases exist but PATH was not applied.
Workaround (local)
- Shorten HKCU
PATH(dedupe, remove per-package WinGet paths, keepWinGet\Links+WindowsApps) and sign out / reboot. turso config set autoupdate off-style:wingetonly via full path until PATH is repaired.
- Lenguaje dominante
- C++
- Estrellas
- 26.6k
- Forks
- 1.8k
- Merge medio
- 3 d 10 h
- PR fusionados (30 d)
- 41
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 microsoft/winget-cli
-
Issue-Docs Needs-Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
microsoft/winget-cli#6692 ·
Los mantenedores suelen responder en 2 días
-
Issue-Docs Possible-Duplicate
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
microsoft/winget-cli#6493 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
WinGetSourceCreator: PackWithMappingFile should verify makeappx.exe exists before invoking itAbiertoIssue-Feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/winget-cli#6427 ·
Los mantenedores suelen responder en 2 días
-
Issue-Docs msstore
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
microsoft/winget-cli#6331 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Command-Source Issue-Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/winget-cli#6148 ·
Los mantenedores suelen responder en 2 días
Todos los issues de microsoft/winget-cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
stratum-mining/sv2-tp#167 ·
Los mantenedores suelen responder en 1 día
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversAbiertoauth bug ui/ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
MerginMaps/mobile#4795 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
HarperFast/rocksdb-js#1118 ·
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
26.04 bug dark-mode Easy Hack impress symptom: visual
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CollaboraOnline/online#16421 · 1 comentario ·