Skip to content
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]: NASM.NASM #207041

Open
2 tasks done
shssoichiro opened this issue Jan 4, 2025 · 1 comment
Open
2 tasks done

[Package Issue]: NASM.NASM #207041

shssoichiro opened this issue Jan 4, 2025 · 1 comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Package-Metadata

Comments

@shssoichiro
Copy link

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Installation of the NASM.NASM package does not succeed if winget is not running with administrative privileges. winget shows a message as if the installation succeeded, but no files are actually installed.

Steps to reproduce

  1. Run winget install --id NASM.NASM from a console without administrative privileges.

Actual behavior

The package appears to install, but no files are installed.

Expected behavior

The installer should run and install files.

Environment

Windows Package Manager v1.9.25200
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.4602
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.24.25200.0

Screenshots and Logs

No response

@shssoichiro shssoichiro added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jan 4, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 4, 2025
@Dragon1573
Copy link
Contributor

Unable to reproduce. 😕

I'm using machine-owned \Administrator account. My device has entered a self-hosted Azure Directory domain. The -l or --location switch seems being ignored and the default installation path is %LOCALAPPDATA%\bin\NASM\.

Is it only happen when installing in a machine scope?

20:50:49 D:\...\winget-pkgs  [master ≡] 1ms pwsh$ winget install -e NASM.NASM -l D:\Applications\NASM\NASM\
已找到 NASM [NASM.NASM] 版本 2.16.03
此应用程序由其所有者授权给你。
Microsoft 对第三方程序包概不负责,也不向第三方程序包授予任何许可证。
正在下载 https://www.nasm.us/pub/nasm/releasebuilds/2.16.03/win64/nasm-2.16.03-installer-x64.exe
  ██████████████████████████████  1.04 MB / 1.04 MB
已成功验证安装程序哈希
正在启动程序包安装...
已成功安装

Image

@stephengillie stephengillie added Package-Metadata and removed Needs-Triage This work item needs to be triaged by a member of the core team. labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Package-Metadata
Projects
None yet
Development

No branches or pull requests

3 participants