Demitrius Nelon

We should also update the output from `winget upgrade" to include a table of pinned packages below the list of upgradable packages and the ones that update themselves.

You rock @jedieaston!

You may not be aware of `winget show`. Some of the metadata in the manifest (including the installer that would be selected based on the machine and settings). ```text PS...

The Windows Package Manager import file should be able to support a more complex schema including the install location, even if `winget export` doesn't (yet).

That's correct as you would be attempting to install "all" packages with that path which doesn't make sense in the context of import. We would need to support the location...

That will only work for packages where getting their install location is reliable. Since users can still make changes outside of WinGet, we need to make sure that we're not...

We had some CDN related issues impacting the cache. You may have been impacted by that issue. It's possible the PR to add the new hash succeeded, but the CDN...

Not at this point. We're still working through the "remote" interfaces for leveraging WinGet on a remote machine. Generally speaking, one is connecting to the remote machine with a "system"...

@Karl-WE we're looking into these. This is one of those areas where the matching is quite challenging. We're looking at an "UpgradeCode" that hopefully will help with these specific packages...

https://github.com/microsoft/winget-cli/issues/1073#issuecomment-921870634