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

未關閉
#6,606 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
cpp, powershell

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
C++
星號
26.6k
分支
1.8k
平均合併
3 天 10 小時
30 天內合併 PR
41

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoft/winget-cli 的其他 Issue

查看 microsoft/winget-cli 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。