Repository navigation
Support environment variable expansion in --location paths #6404
Description
Maintainer test — verifying the new agentic Duplicate Surfacing workflow (tracking: #6399). This issue intentionally duplicates an existing request and will be closed shortly after the run completes.
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
It would be great if the --location argument supported environment variable expansion natively, without relying on the shell. For example, I keep a set of per-app install-location overrides in a frontend and want them to be portable across machines, where the same path resolves differently (different drive letters, user profiles, etc.).
Having winget expand environment variables in --location itself — independent of the calling shell or app — would make those overrides portable.
Proposed technical implementation details
Since / : * ? " < > | are illegal in folder names, a delimiter like <VAR> could denote an environment variable, e.g. --location "<SystemDrive>\Program Files\my-app" would expand <SystemDrive> to C:.
Activity
github-actions commentedon Jul 29, 2026
Possible duplicates (surfaced automatically for maintainer review — this issue has not been closed):
--location, same GUI-frontend portability use case, same proposed<>delimiter syntax.Maintainers: if one of these is the canonical issue, comment
Duplicate of #<number>to consolidate. Earlier/curated issues are preferred as canonical.Template: msftbot/duplicate/surfaced
denelon commentedon Jul 29, 2026
Closing — this was a maintainer verification of the new Duplicate Surfacing workflow (#6399). It correctly surfaced #6388. No further action needed.
Disable no-op run reporting for Duplicate Surfacing workflow (#6408)