Demitrius Nelon

@giggio we can't trust that the application hasn't been updated independently from winget. That means if the version isn't being reported correctly, we can't reason about what is installed. We...

@ev-dev be sure to add your 👍 to the issue. We often sort by most 👍 to find high priority / high value features. We have a large number of...

@JohnMcPMS do you know what might be driving the order of the output for `winget list`?

@Stadly unless NASM.NASM is a portable package, the installer would be responsible for adding the package to the path. If it is adding it to the path, restarting the terminal...

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...

The current behavior in the install flow is that we launch another process to execute the "installer". In this case, and in general with Squirrel installers, they launch another process...

`winget upgrade` will show packages with "known" versions available for upgrade. `winget upgrade --include-unknown` will show packages with both "known" and "unknown" versions. `winget upgrade --all` will upgrade packages with...

I'd call that a "bug", and it could be related to the installers not writing the correct entries into Apps & Features (via the registry) or dealing with "side by...

We do want to bring the Windows Package Manager to as many SKUs as reasonably possible. I don't have any timelines, but we have started discussions. It's unlikely we will...

Docker/Container related issues: * #669 * #438