WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
If a command value is specified in the manifest, then the symlink filename will be renamed to match the command value. If the rename argument is provided, then both the symlink filename and the portable exe filename will be renamed to match the rename argument value.
However, the portable exe is renamed even if the rename argument is absent.
In case the behavior is intended and only the documentation is misleading, I still request changing this behavior. Renaming the exe is confusing and seems unnecessary.
Steps to reproduce
Run winget install --exact --id Microsoft.Sysinternals.ProcessExplorer --version 17.05
Brief description of your issue
The Portable/Standalone applications documentation states:
However, the portable exe is renamed even if the rename argument is absent.
In case the behavior is intended and only the documentation is misleading, I still request changing this behavior. Renaming the exe is confusing and seems unnecessary.
Steps to reproduce
Run
winget install --exact --id Microsoft.Sysinternals.ProcessExplorer --version 17.05
Note that the manifest includes:
Expected behavior
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links
contains symlinkprocess-explorer.exe
.C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\
containsprocexp64.exe
.Actual behavior
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links
contains symlinkprocess-explorer.exe
.C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\
containsprocess-explorer.exe
.Environment