Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Winget -e incorrectly matches items #2142

Open
Swiftnc opened this issue May 6, 2022 · 1 comment
Open

Winget -e incorrectly matches items #2142

Swiftnc opened this issue May 6, 2022 · 1 comment
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@Swiftnc
Copy link

Swiftnc commented May 6, 2022

Brief description of your issue

Winget is incorrectly matching items when using the -e switch.

Steps to reproduce

Install a package (Such as Visual C++ 2013 x86) using the following command:
winget install -e --id Microsoft.VC++2013Redist-x64 --scope machine --accept-source-agreements --accept-package-agreements

Verify it is installed by running
winget list c++

Winget will correctly list that it is installed by showing this:
Name Id Version Source

Microsoft Visual C++ 2013 Redistributable (x64) Microsoft.VC++2013Redist-x64 12.0.40664.0 winget
(note, only the x64 version is installed)

Then check if the X86 version is installed explicitly with this command
winget list -e --id "Microsoft.VC++2013Redist-x86" --accept-source-agreements

Winget will incorrectly now state that the x86 version is installed
Name Id Version Source

Microsoft Visual C++ 2013 Redistributable (x86) Microsoft.VC++2013Redist-x86 12.0.40664.0 winget

Expected behavior

Winget should NOT detect the x86 version when it is not installed when running with the -e --id command lines

Actual behavior

Winget will incorrectly now state that the x86 version is installed
Name Id Version Source

Microsoft Visual C++ 2013 Redistributable (x86) Microsoft.VC++2013Redist-x86 12.0.40664.0 winget

Environment

Windows Package Manager v1.2.10271

This happens with many versions of the C++ software but may also affect other applications as well.
@ghost ghost added the Needs-Triage Issue need to be triaged label May 6, 2022
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels May 6, 2022
@denelon
Copy link
Contributor

denelon commented May 6, 2022

This is essentially the same as:

We are currently working on improving the matching heuristics and adding support in the client to leverage the "AppsAndFeatures" portion of the manifest schema.

@denelon denelon added this to the v1.4-Client milestone Jun 2, 2022
@denelon denelon modified the milestones: v1.4-Client, v1.5-Client Dec 28, 2022
@denelon denelon added the Area-Matching Issue related to correlation between installed package and manifest label Feb 22, 2023
@denelon denelon modified the milestones: v1.5-Client, v.Next-Client Jun 6, 2023
@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

2 participants