Win11 26H2: user PATH (~3.6k) not applied to new processes — winget missing in cmd/PS 5.1/pwsh

Offen
#6,606 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

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

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

Issue-Bug

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.exe at %LOCALAPPDATA%\Microsoft\WindowsApps\winget.exe runs when invoked by full path (winget --version → v1.29.380)
  • User PATH in registry (HKCU Environment\Path): ~3,632 characters, includes %LOCALAPPDATA%\Microsoft\WindowsApps and 13 ...\Microsoft\WinGet\Packages\... entries (typical winget portable install pattern without Developer Mode / admin Links layout)

Steps to reproduce

  1. Accumulate a large user PATH (common with multiple winget portable/zip packages that each append a long WinGet\Packages\... segment).
  2. Upgrade to Windows 11 26H2 (or open a new cmd / PowerShell 5.1 / pwsh session after upgrade).
  3. Run where winget in cmd or Get-Command winget in PowerShell 5.1 or pwsh.
  4. Compare [Environment]::GetEnvironmentVariable('Path','User') (registry) vs $env:Path in the same process.

Expected

  • User PATH from HKCU is merged into every new interactive shell (cmd, PowerShell 5.1, pwsh).
  • winget resolves via the App Execution Alias under WindowsApps when App Installer is installed.
  • If a platform limit applies, Windows should surface a clear error or warning when user PATH cannot be applied — not silently drop the entire user block.

Actual

  • Registry user PATH length ~3632; process PATH length ~1326 (matches machine PATH only — user PATH not applied at all).
  • where winget in cmd: not found.
  • Get-Command winget in PowerShell 5.1 and pwsh: not found.
  • Direct invocation still works: & "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget.exe" --version.
  • PowerShell profile import of Microsoft.WinGet.CommandNotFound fails at startup because ValidateOS.psm1 requires Get-Command winget to 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\WindowsApps in PATH (docs)

Ask

  1. OS: Fix or document behavior when user PATH exceeds legacy limits — do not silently omit the entire user PATH from new processes.
  2. 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.
  3. Visibility: A high-signal diagnostic (e.g. winget doctor or Settings) when App Execution Aliases exist but PATH was not applied.

Workaround (local)

  • Shorten HKCU PATH (dedupe, remove per-package WinGet paths, keep WinGet\Links + WindowsApps) and sign out / reboot.
  • turso config set autoupdate off-style: winget only 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

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/winget-cli

Alle Issues in microsoft/winget-cli

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.