The installation flow does not have this fallback method as mentioned in the initial pr. If the user is already on 2.0, then they will get no applicable update found. But, the upgrade will actually install 2.0 since it is the latest version with an applicable installer. If a user is on v2.0 they will see 3.0 when they run an upgrade. Although, I don’t know that all the details were fully explained. If the installed version is the latest applicable or greater, then it terminates with no applicable seems to have a great understanding of what the issue I described above is, stating it in your initial pr. In the update flow, it falls back to the latest version with an applicable installer.

In the install flow, this terminates the command. Since it cannot find a version compatible with win10, it deems there to be no applicable installer. As shown by the No applicable update found. I originally thought the filter was broken, but I now belive I just misunderstood how it gets applied. Specifically, there are filter fields for architecture, installer type, and in this case, there is also one for MinOSVersion. The manifest comparator has various fields called “FilterFields” that narrow down which specific installers may be used. There is a section of the code called the ManifestComparator which, from my understanding, is used when the CLI is selecting which installer to use from a manifest. No, this was the issue I was referencing, and after digging into the code more it seems that I was partially mistaken.

Winget install windows terminal