PortableCommandAlias reports alias added but does not create alias for ZIP portable package

未关闭
#6,604 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
cpp
领域
cli, devtools

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

Command-Install Issue-Bug Portable
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
  1. Create a multi-file WinGet manifest for Genesys.Archy version 2.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
  1. Validate the manifest:
winget validate --manifest C:\Users\ascheble\manifests\g\Genesys\Archy\2.43.2

Result:

Manifest validation succeeded.
  1. 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
  1. 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
  1. Check the portable links directory:
Get-ChildItem "$env:LOCALAPPDATA\Microsoft\WinGet\Links" -Force

No archy alias/link is present.

  1. 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
主要语言
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 摘要。