PortableCommandAlias reports alias added but does not create alias for ZIP portable package
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the portable package install path for ZIP installers and PortableCommandAlias, then inspect the link creation logic and its tests. Reproduce with the provided ARM64 system and x64 manifest, checking whether the executable path is accepted and whether a link is written to the user Links directory. Done means the alias invokes the extracted executable, or installation reports the link creation failure.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
winget install
Brief description of your issue
Installing a ZIP-based portable package with PortableCommandAlias: archy reports Command line alias added: "archy" and completes successfully, but no archy alias is actually created.
The package files are extracted correctly and the target x64 executable runs successfully when invoked directly. However, %LOCALAPPDATA%\Microsoft\WinGet\Links remains empty and archy cannot be resolved by where.exe, PowerShell Get-Command, or executed from the command line.
This is reproducible with a clean installation and from an elevated PowerShell session.
Steps to reproduce
- Create a multi-file WinGet manifest for
Genesys.Archyversion2.43.2. The relevant installer manifest is:
PackageIdentifier: Genesys.Archy
PackageVersion: 2.43.2
InstallerType: zip
NestedInstallerType: portable
NestedInstallerFiles:
- RelativeFilePath: archyBin\archy-win-2.43.2.exe
PortableCommandAlias: archy
Installers:
- Architecture: x64
InstallerUrl: https://sdk-cdn.mypurecloud.com/archy/2.43.2/archy-win.zip
InstallerSha256: 9D8D626E7D998EE7AC2FD753A1585674BB5C4B996806EDEC96D7D2DB5E725172
ManifestType: installer
ManifestVersion: 1.12.0
- Validate the manifest:
winget validate --manifest C:\Users\ascheble\manifests\g\Genesys\Archy\2.43.2
Result:
Manifest validation succeeded.
- Install the package:
winget install --manifest C:\Users\ascheble\manifests\g\Genesys\Archy\2.43.2
WinGet reports:
Found Archy [Genesys.Archy] Version 2.43.2
Downloading https://sdk-cdn.mypurecloud.com/archy/2.43.2/archy-win.zip
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Starting package install...
Command line alias added: "archy"
Successfully installed
- Verify that the package was extracted successfully:
Get-ChildItem "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Genesys.Archy__DefaultSource" -Recurse
The package contains:
Genesys.Archy__DefaultSource\
archy.bat
archyBin\
archy-win-2.43.2.exe
- Check the portable links directory:
Get-ChildItem "$env:LOCALAPPDATA\Microsoft\WinGet\Links" -Force
No archy alias/link is present.
- Close PowerShell and open a new PowerShell session, then check whether the reported alias is available:
where.exe archy
Result:
INFO: Could not find files for the given pattern(s).
PowerShell also cannot resolve the command:
Get-Command archy
Result:
The term 'archy' is not recognized as the name of a cmdlet, function, script file, or operable program.
Likewise:
archy version
fails because archy cannot be resolved.
The behavior is also reproducible when the installation is performed from an elevated PowerShell session. WinGet still reports:
Command line alias added: "archy"
but no corresponding alias is created.
Expected behavior
Given:
NestedInstallerFiles:
- RelativeFilePath: archyBin\archy-win-2.43.2.exe
PortableCommandAlias: archy
WinGet should create a usable archy command alias for the portable executable, such that:
archy version
invokes the installed archyBin\archy-win-2.43.2.exe.
If WinGet cannot create the requested alias, installation should report that failure rather than reporting:
Command line alias added: "archy"
Actual behavior
WinGet reports:
Command line alias added: "archy"
Successfully installed
but no alias is created.
%LOCALAPPDATA%\Microsoft\WinGet\Links remains empty, and:
where.exe archy
returns:
INFO: Could not find files for the given pattern(s).
The package itself is successfully downloaded and extracted to:
%LOCALAPPDATA%\Microsoft\WinGet\Packages\Genesys.Archy__DefaultSource
and the target executable exists at:
archyBin\archy-win-2.43.2.exe
Therefore the failure appears specific to creation of the requested PortableCommandAlias.
Environment
Windows Package Manager v1.29.380
Microsoft.DesktopAppInstaller v1.29.380.0
Windows: Windows.Desktop v10.0.26300.9711
System Architecture: Arm64
The package manifest specifies an x64 executable:
Architecture: x64
The x64 executable runs successfully on the ARM64 system using Windows Prism.
The issue was reproduced both normally and from an elevated PowerShell session.
Relevant `winget --info` paths:
Portable Links Directory (User)
%LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine)
C:\Program Files\WinGet\Links
Portable Package Root (User)
%LOCALAPPDATA%\Microsoft\WinGet\Packages
Local manifests are enabled:
LocalManifestFiles Enabled
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day