-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Package Issue]: sharkdp.bat #106463
Comments
Does this occurr when using the latest preview release of winget (v1.5.1081-preview)? There was a known CLI issue that should be patched in the preview - |
This issue occurs for a few more packages (for me at least): (I don't exactly know how the winget manifests work and all that, but the three packages seem to all specify the correct files in the Using:
|
Please upgrade to WinGet v1.5.1081-preview where this issue has been resolved |
@helpimnotdrowning - Do you see the same issue if you use version 1.5.1081-preview from the releases page? |
@Trenly I forgot to remove the package using v1.4.10173 and when I tried to do it using v1.5.1361-preview the command line froze at this step: Edit: I reinstalled v1.4.10173 and was able to remove the package. Then, I upgraded to v1.5.1361-preview and installed the package again. The bat.exe was added correctly to the path this time. |
Great! Glad to hear this is resolved in the upcoming version of the client. |
Please confirm these before moving forward
Category of the issue
Installation issue.
Brief description of your issue
The environment variable added for the package is wrong. The installer adds to the PATH the folder
%LOCALAPPDATA%\Microsoft\WinGet\Packages\sharkdp.bat_Microsoft.Winget.Source_8wekyb3d8bbwe
, but the bat.exe is in%LOCALAPPDATA%\Microsoft\WinGet\Packages\sharkdp.bat_Microsoft.Winget.Source_8wekyb3d8bbwe\bat-v0.23.0-x86_64-pc-windows-msvc
.Steps to reproduce
bat
Actual behavior
bat: The term 'bat' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Expected behavior
The .exe file to be in the user path.
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: