Kaleb Luedtke

It seems the pipeline isn't liking them though - ``` 2022-03-01 15:35:33.762 [CLI ] WinGet invoked with arguments: 'install' '--manifest' 'D:\TRANSFER\3b34ff1b-b899-ec11-9501-000d3a9ede8b\Manifest.yaml' '--accept-package-agreements' 2022-03-01 15:35:33.762 [CLI ] Found subcommand: install 2022-03-01...

Doubtful. I restarted the one that failed and it seems to have made it further this time, so maybe it was just a fluke. I'll keep an eye on it

@Jaifroid - Can you try running the install now to see if the issue is resolved?

Interesting. Since the update to appx installer type, I'm not able to reproduce the bug anymore on either the latest release or the prerelease version of the client - ```raw...

> OK, maybe I tried it too soon before servers had fully updated? Will try again when I get back to PC later and report back. Maybe, but it did...

I downloaded the merged manifest created by the Validation pipelines, and I got this error - ``` --> Installing WinGet Tip: you can type 'Update-EnvironmentVariables' to update your environment variables,...

> @Trenly didn't you create a issue? 😬 > Would you mind explaining your findings? No, this was the issue I was referencing, and after digging into the code more...

> The newest release of windows terminal includes a windows 10 and windows 11 version. It seems that winget has the windows 11 version. > > https://github.com/microsoft/terminal/releases/tag/v1.12.10982.0 Winget has both...

> The improved searching is still questionable in my mind; I would want to know that Foo exists, is in the repository of packages, but is not available for my...

> (and even then, should `winget show foo --versions` list inapplicable version with an *?) I would say Yes > We could output N/A or similar as the version to...