How to handle subscription / paid only commercial software? (WinGet is used as a spam/marketing platform now?)

[Adrian (R-Adrian)]

I thought WinGet was supposed to be used for installing / updating free / opensource software that has no other easy way to be updated ...

in discussion #16341 from 2021 ThioJoe asked about paid major version upgrades... but lately i have seen quite some activity where companies are trying to use the WinGet manifest repository for software that is either subscription-only or has a short trial and then is subscription-only.

More importantly, those softwares already have their own built-in updaters .... thus the only point of using WinGet is as a spam / marketing platform to get new installs / customers.

Since WinGet accepts multiple source repositories, those companies could very well set up their own separate repository to deploy installs/updates via WinGet but still they choose to stuff them in the main public repository here on GitHub... and then ask for money for using their software.

Even if that is allowed, maybe Microsoft should consider imposing some sort of fee structure for such commercial-only packages when present in the main public repository, to limit the influx of such?
And mark them distinctly in the manifest repository as being paid-only software so we can filter them out.

e.g. today, someone opened #258829 for ESET
and ESET already has other paid-only products in the WinGet repository even though their stuff also has built-in updaters...

https://github.com/microsoft/winget-pkgs/tree/master/manifests/e/ESET/
EndpointSecurity, EndpointAntivirus
edit: NOD32 is also there /edit

Since these are subscription-only softwares that already have their own built-in updaters, my opinion is that their presence in the public manifests means these are spam / marketing slop via WinGet.

[Charlie Chen (SpecterShell)]

installing / updating free / opensource software

I couldn't remember if anyone from the WinGet team has claimed this before.. Actually, there is a field called PurchaseUrl in the manifest.

[Kirill638849776]

This is indeed an interesting question. I understand your concern about commercial software in the WinGet repository.

In fact, WinGet was originally conceived as a universal tool for installing programs, not just for Open Source. The manifest even includes a special PurchaseUrl field, which clearly indicates that the developers provided for the possibility of adding paid software.

The main reason why companies add their paid products to WinGet is: 1. It simplifies installation for corporate users (especially via scripts and automation).
2. WinGet is a standardized distribution method that many administrators are already using.

As for embedded updates, this is not prohibited. Many programs have their own updaters, but WinGet offers a single interface for managing all applications.

Regarding spam, there are several points:

• All packages are checked through wingetvalidator before being added.
• If a package violates the rules, it can be deleted via Issues.
• The PurchaseUrl field helps users understand that the software is paid.

If you believe that a certain package violates the rules, you can always open an Issue with an explanation. The Microsoft team closely monitors the quality of the repository.

It is also worth noting that commercial software in WinGet is not a new feature. Products such as ESET have been present in the repository for a long time, and this is not considered a violation.

[Adrian (R-Adrian)]

Thank you for reminding me about this question i asked last year.

Since then there have also been cases where software that used to be free is now subscription-only and WinGet "upgrading" it results in the user being asked to pay up or GTFO.

e.g. RealVNC Viewer v7 was "upgraded" to v8: #391842