winget-cli icon indicating copy to clipboard operation
winget-cli copied to clipboard

NASM is not detected after installation

Open Stadly opened this issue 3 years ago • 3 comments

Brief description of your issue

After installing NASM, it is not detected by winget list, and cannot be uninstalled by winget uninstall.

Steps to reproduce

  1. winget install -e --id NASM.NASM
  2. winget list -e --id NASM.NASM
  3. winget uninstall -e --id NASM.NASM

Expected behavior

  1. NASM is installed
  2. NASM is detected
  3. NASM is uninstalled

Actual behavior

  1. NASM is installed
  2. No installed package found matching input criteria.
  3. No installed package found matching input criteria.

Environment

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

Windows: Windows.Desktop v10.0.22000.795
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Stadly avatar Aug 16 '22 09:08 Stadly

This is actually an issue with NASM itself. When the publishers created the installer for NASM, they are not setting any Registry Entries in the Add & Remove Programs table. In other words, the NASM installer isn't registering that it has installed NASM. This isn't something that winget can do, since it is up to the publishers to register the components they install as part of their program.

I would recommend filing a bug report with the publishers of NASM and asking them to set the DisplayName, DisplayVersion, and Publisher registry keys when they install NASM. It should be very simple for them to do as they are using Nullsoft Installer System to compile their installer

Trenly avatar Aug 17 '22 16:08 Trenly

Thanks for the detailed explanation! How can I contact the publishers? On the Chocolatey page they have a link to "Contact Maintainers", but I couldn't find such a thing on the winget page.

Stadly avatar Aug 18 '22 08:08 Stadly

I'm not a Chocolatey expert, but I believe the maintainers would be the maintainers of the Chocolatey package which might not be the publisher. The WinGet community repository has a slightly different model where there aren't specific maintainers for the manifests. You may be able to use the package metadata to find a website which could lead to a contact page.

winget show nasm displays https://www.nasm.us/

denelon avatar Aug 22 '22 15:08 denelon