Logitech Gaming Hub [Logitech.LGH] - Installer hash does not match

[hexadezi]

Create issues related to the winget.exe client here

Brief description of your issue

When installing, I get "Installer hash does not match error".

Steps to reproduce

winget install -e --id Logitech.LGH

Expected behavior

A successful install.

Actual behavior

Gefunden Logitech Gaming Hub [Logitech.LGH]
Diese Anwendung wird von ihrem Besitzer an Sie lizenziert.
Microsoft ist nicht verantwortlich und erteilt keine Lizenzen für Pakete von Drittanbietern.
Downloading https://download01.logi.com/web/ftp/pub/techsupport/gaming/lghub_installer.exe
██████████████████████████████ 39.4 MB / 39.4 MB
Installer-Hash stimmt nicht überein; zum Aufheben der Überprüfung --force

Environment

[winget --info]
Windows Package Manager v0.2.10191 Vorschau
Windows: Windows.Desktop v10.0.19042.870
Paket: Microsoft.DesktopAppInstaller v1.11.10191.0

Any other software?

[denelon]

@labo89 it looks like the publisher changed the installer. Our automation generally runs daily and should catch this and create a PR with the correct hash. It may not run depending on where we are with manifest conversation. Optionally, someone may download the installer, calculate the hash winget hash lghub_installer.exe, update the manifest and submit a PR.

[jedieaston]

The problem is that the Logitech Gaming Hub won't install silently anymore, so we can't update it in the repo. Maybe it should be removed.

See #7901 (among others if you do a search)

[denelon]

@jedieaston, thanks for sharing your knowledge on this. You may be right. If there isn't a silent installer available, we may be blocked here. The new manifest specification includes the ability to identify that a package only supports an interactive installer. We're looking at adding a feature to identify packages that can't install silently and filter those from search with some kind of arguments. Some community feedback on this might help prioritize that work. What are your thoughts on the subject? I'll create a discussion item, and link it.

[denelon]

#9190
Should the catalog allow "non-silent" installers?

[ghost]

I think we should keep the non-silent installers for the simple reason that even if it doesn't install completely automatically it's still a lot handier than going to their website and downloading the installer.

[Teraskull]

Another example is FreeFileSync. The silent install is only available with donation edition, but it is still possible to install the software in interactive mode with Winget.

[denelon]

microsoft/winget-cli#910

[Trenly]

I think this can be closed because of @ItzLevvie's PR #15917, which removed the package since it couldn't be updated