Demitrius Nelon

@awg43 Which version of the Windows Package Manager are you using? `winget -v` will display the version. Does this same thing happen on the latest [release candidate build](https://github.com/microsoft/winget-cli/releases/tag/v1.3.1741)?

We need to determine the PowerShell (approved nouns & verbs) syntax. @ryfu-msft is working on native PowerShell.

How about --ignore-archive-malware-scan ? I'd also like to know why we're thinking about enabling this behavior. Do we think there are false positives? Or is this just to be "more"...

Or maybe "bypass" as the other policy is written.

@lvzhenbo does this kind of workaround fix the issue you're encountering?

OK, I'll keep the bug open. Would you mind running the same commands as Anikund and share the logs?

You will see a ">" symbol when marketing versions are being used for packages. These are often used when the version reported in the registry and displayed via Windows Apps...

It looks like we need to add Microsoft.UI.Xaml.2.7 to https://github.com/microsoft/winget-cli#manually-update

We have now have a group policy to restrict the ability to use "local manifests". I'd like to keep this intent so it can be managed by policy and doesn't...

@ryfu-msft the origin of this came from winget-cli-restsource. Does this look like it's sufficient, or would more work be involved (test cases impacted)?