Kaleb Luedtke

Interesting; When I use `winget list voidtools.everything` I see the same - that a newer version is available. But, when I try `winget upgrade`, it doesn't detect it for upgrade...

I think this might be a bigger issue, actually. I was testing a different bug for pkgs, and I noticed that Firefox wasn't being selected for upgrade, but when I...

> > I think this might be a bigger issue, actually. I was testing a different bug for pkgs, and I noticed that Firefox wasn't being selected for upgrade, but...

See #2412 regarding the error when removing the package. `Microsoft.winget.source_8wekyb3d8bbwe` is not the package which contains the executable for WinGet. What it actually is, is the data for the default...

> There is no way of knowing that DesktopAppInstaller is the actual package for winget When installing through the store, you install "App Installer", not "Winget". I can see where...

Try using a semicolon instead of & ``` winget upgrade --id Microsoft.VisualStudio.2019.Enterprise --accept-package-agreements --accept-source-agreements; winget upgrade --id Microsoft.VisualStudio.2022.Enterprise --accept-package-agreements --accept-source-agreements ```

This may actually be a bug with VisualStudio returning that the upgrade finished before it actually did, even though the `--wait` switch is included. @jedieaston might know more about it...

I was looking through the list of issues and found this one which could be a consideration for a 2.0 release or to be dropped - * https://github.com/microsoft/winget-cli/issues/429

> Thanks for the PR! Windows is the least-supported Pext platform so it's awesome to see someone give it some love :) > > AppVeyor seems to be unhappy parsing...

> I wonder if this should be enforced in a hypothetical schema 2.0. There aren't a ton of circumstances where putting `InstallerType` or others globally doesn't just turn into a...