Win11 26H2: user PATH (~3.6k) not applied to new processes — winget missing in cmd/PS 5.1/pwsh
Maintainer antworten meist innerhalb von 2 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Bug
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- cpp, powershell
- Bereich
- cli, operating-systems
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- C++
- Sterne
- 26.6k
- Forks
- 1.8k
- Ø Merge
- 3 T. 10 Std.
- Gemergte PRs (30 T.)
- 41
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoft/winget-cli
-
Issue-Docs Needs-Triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
microsoft/winget-cli#6692 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Issue-Docs Possible-Duplicate
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
microsoft/winget-cli#6493 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Issue-Feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
microsoft/winget-cli#6427 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Issue-Docs msstore
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
microsoft/winget-cli#6331 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Command-Source Issue-Bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
microsoft/winget-cli#6148 ·
Maintainer antworten meist innerhalb von 2 Tagen
Alle Issues in microsoft/winget-cli
Ähnliche Issues
-
feat
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
stratum-mining/sv2-tp#167 ·
Maintainer antworten meist innerhalb von 1 Tag
-
better error message bug low priority semantics strings
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversOffenauth bug ui/ux
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
MerginMaps/mobile#4795 ·
Maintainer antworten meist innerhalb von 2 Tagen