Unable to disambiguate package Microsoft.VC++2013Redist-x64 #1413

alkampfergit · 2021-08-30T10:31:56Z

Brief description of your issue

I'm trying to update package Microsoft.VC++2013Redist-x64 because it cannot disambiguate between the package and a weird package with a guid

Steps to reproduce

Install an old version Microsoft.VC++2013Redist-x64 I'm not aware of the exact sequence of package to install.

Expected behavior

I want to be able to choose the exact package with the --id or --exact.

Actual behavior

I'm not able to update package Microsoft.VC++2013Redist-x64 because it continues to tells me that it is ambiguous with another package identified by a weird guid, as for the previous image.

Environment

Windows Package Manager v0.4.11391 Preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19043.1165
Package: Microsoft.DesktopAppInstaller v1.11.11391.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
--------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget

The text was updated successfully, but these errors were encountered:

alkampfergit · 2021-08-30T10:34:07Z

IF you specify the GUID to upgrade package, the situation become worse, it updates the package and then I have even more conflict

zmira · 2021-09-03T22:34:29Z

I was able to update by running, for example, winget upgrade --name "Microsoft Visual C++ 2013 Redistributable (x64)", but all it did was install the new version (12.0.40664) without uninstalling the previous one (12.0.30501), which I then had to manually uninstall via Settings > Apps & features > Uninstall.

MagicFirefly · 2021-09-12T07:26:57Z

I also have this issue with the c++ 2015-2019 Redistributable (x64). I have tried --name, -e --name, --id, and -e --id but always get the multiple installed packages message with one being x64 and the other x86. I find no ability to refine further.

Attempt upgrade --name example:

The initial upgrades found window:

jdhitsolutions · 2021-09-13T14:19:41Z

This is more than a feature request. I'm having the same issue with multiple packages. Here's one example.

I'm on Windows 11 build 22000

ffes · 2021-10-22T07:42:38Z

I don't see why @denelon has marked this as feature and not as a bug. The option --id is broken, if you ask me.

C:\Windows\system32>winget upgrade
Naam                                                 Id                                Versie        Beschikbaar   Bron
-------------------------------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2015-2019 Redistributable (x64) Microsoft.VC++2015-2019Redist-x64 14.29.30133.0 14.29.30135.0 winget
Microsoft Visual C++ 2015-2019 Redistributable (x86) Microsoft.VC++2015-2019Redist-x86 14.29.30133.0 14.29.30135.0 winget
Microsoft Teams                                      Microsoft.Teams                   1.4.0.7174    1.4.00.26376  winget
3 beschikbare upgrades.

C:\Windows\system32>winget upgrade --id Microsoft.VC++2015-2019Redist-x86
Er zijn meerdere geïnstalleerde pakketten gevonden die overeenkomen met de invoer criteria. Verfijn de invoer.
Naam                                                               Id
---------------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2015-2019 Redistributable (x86)               Microsoft.VC++2015-2019Redist-x86
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.29.30133 {295d1583-fdb9-414b-a4c8-da539362a26b}

When I enter --id with an exact id, the upgrade should know what package to upgrade. It should just do a (non case senstive) string compare and no "intelligent" things. I enter --id for a reason!

And note that the package with the GUID isn't even mentioned in winget upgrade, so apparently it is not upgradable. Why is it even considered for upgrading?

denelon · 2021-10-22T16:05:44Z

I misunderstood the original report. This is probably a duplicate of another Issue, but I will keep this open for now until we have a chance to triage all open bugs again to confirm. We already have support in the 1.1 schema for this scenario, but the client side implementation is still in progress.

ffes · 2021-10-29T11:48:47Z

Here another example why I think there is definitely something wrong with --id and/or --exact.

Note that PowerToys is detected as an upgrade but none of the 5(!) winget upgrade commands I tried were able to find the package.

@denelon Could you consider changing the title of this issue and make it more general? It is not just for VC++ runtime libraries.

C:\Windows\system32>winget upgrade
Naam                                               Id                                Versie        Beschikbaar   Bron
-----------------------------------------------------------------------------------------------------------------------
PDF-XChange Editor                                 TrackerSoftware.PDF-XChangeEditor 9.2.357.0     9.2.358.0     winget
Microsoft Visual C++ 2015-2019 Redistributable (x… Microsoft.VC++2015-2019Redist-x64 14.29.30133.0 14.29.30135.0 winget
Microsoft Visual C++ 2015-2019 Redistributable (x… Microsoft.VC++2015-2019Redist-x86 14.29.30133.0 14.29.30135.0 winget
Microsoft Teams                                    Microsoft.Teams                   1.4.0.7174    1.4.00.26376  winget
PowerToys (Preview)                                Microsoft.PowerToys               0.47.1        0.49.0        winget
5 beschikbare upgrades.

C:\Windows\system32>winget upgrade powertoys
Er is geen toepasselijke update gevonden.

C:\Windows\system32>winget upgrade microsoft.powertoys
Er is geen toepasselijke update gevonden.

C:\Windows\system32>winget upgrade --id microsoft.powertoys
Er is geen toepasselijke update gevonden.

C:\Windows\system32>winget upgrade --id Microsoft.PowerToys
Er is geen toepasselijke update gevonden.

C:\Windows\system32>winget upgrade --exact Microsoft.PowerToys
Er is geen toepasselijke update gevonden.

C:\Windows\system32>winget --version
v1.1.12653

denelon · 2021-10-29T22:20:55Z

@ffes PowerToys is a known issue. The installer is an MSI inside of an EXE. When we see the manifest telling us the installer is EXE, we stop trying to upgrade an MSI. We've already made changes to the schema to support this specific kind of a scenario, it's just a matter of finishing the work on the client and validating before we get that feature out in a preview build.

For some context, "--exact" is looking for a case sensitive match where the other default behaviors are looking for a case insensitive substring match.

jamesmyatt · 2021-11-11T10:37:06Z

I have the same issue with R. Is there any workaround?

>winget upgrade --exact --id RProject.R
Multiple installed packages found matching input criteria. Please refine the input.
Name                Id
-------------------------------------------
R for Windows       RProject.R
R for Windows 4.1.2 R for Windows 4.1.2_is1

denelon · 2022-01-05T19:00:19Z

We met with the VC++ redistributable team. We're working together to help alleviate the confusion here. There are a few scenarios we need to consider.

Between 2005 and 2013 Visual Studio editions, a different version is installed "side by side".
Starting with the 2015 editions, the version is truly upgraded.

One of the things we need to do is check to see if a "newer" version is installed when multiple installed versions are present, so we don't try to perform an upgrade on the "older" version (when it is a "side by side" install).

Another area we're looking at is the product code for the installers that is currently the same across architectures.

rcdailey · 2022-01-07T00:08:02Z

Worth pointing out this happens with Microsoft.dotnet as well; #1829 was marked as a duplicate of this issue but I see no mention of this specific package here. Instead I see specific issues with vcredist that I am not sure relates to this package.

When I do a package list:

PS C:\Windows\System32> winget list | findstr -i dotnet
Microsoft .NET SDK                           Microsoft.dotnet                             5.2.921.52710         winget
Microsoft Windows Desktop Runtime - 3 (x64)  Microsoft.dotnetRuntime.3-x64                3.1.22.30721          winget
Microsoft .NET SDK                           Microsoft.dotnet                             6.1.121.56904         winget

There are two versions of dotnet here, I'm not sure why. The only one I want is v6. OR, if both should be present, it shouldn't appear when I do winget upgrade as it does now:

PS C:\Windows\System32> winget upgrade
Name                 Id                Version       Available     Source
-------------------------------------------------------------------------
Microsoft .NET SDK   Microsoft.dotnet  5.2.921.52710 6.1.121.56904 winget
Oracle VM VirtualBox Oracle.VirtualBox 6.1.26        6.1.30        winget
2 upgrades available.

And when doing winget upgrade --all, stuff happens and then this list stays the same. I'm running Winget version v1.2.3411-preview.

denelon · 2022-01-07T04:29:10Z

@rcdailey the VC++ issue was the first report for the problem(s). We're looking for a solution to the class of problems pointed out here. This seems to happen when the Windows Package Manager is unable to disambiguate more than one entry in Apps & Features as they correlate to different architectures (and possibly other properties). There are some other scenarios that manifest the same way in terms of ambiguity. Since this was the first report, we're trying to capture the impact by marking others as a duplicate of this one to increase the 👍 count to help prioritize.

sba923 · 2022-03-11T09:50:20Z

I presume this belongs here too?

PS❯  winget upgrade | ConvertFrom-WingetStdout.ps1 | ? { $_.id -in @('Microsoft.VC++2008Redist-x86','Python.Python.2','Microsoft.dotnet') } | % { ("`n`n`nUpgrading '{0}' (id='{1}') using 'winget upgrade --id {1} --exact'" -f $_.Name, $_.Id); winget upgrade --id $_.Id --exact }





Upgrading 'Microsoft Visual C++ 2008 Redistributable - x86' (id='Microsoft.VC++2008Redist-x86') using 'winget upgrade --id Microsoft.VC++2008Redist-x86 --exact'
Multiple installed packages found matching input criteria. Please refine the input.
Name                                                           Id
-----------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2008 Redistributable - x86                Microsoft.VC++2008Redist-x86
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 {9BE518E6-ECC6-35A9-88E4-87755C07200F}
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022      {350AA351-21FA-3270-8B7A-835434E766AD}
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161 {5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17   {8220EEFE-38CD-377E-8595-13398D740ACE}
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17   {9A25302D-30C0-39D9-BD6F-21E6EC160475}
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022      {FF66E9F6-83E7-3A3E-AF14-8DE9A809A6A4}



Upgrading 'Python 2' (id='Python.Python.2') using 'winget upgrade --id Python.Python.2 --exact'
Multiple installed packages found matching input criteria. Please refine the input.
Name                   Id
-------------------------------------------------------------
Python 2               Python.Python.2
Python 2.7.16 (64-bit) {DCD5B320-89D9-4C7C-9E8B-84496588744e}



Upgrading 'Microsoft .NET SDK' (id='Microsoft.dotnet') using 'winget upgrade --id Microsoft.dotnet --exact'
Multiple installed packages found matching input criteria. Please refine the input.
Name                             Id
-----------------------------------------------------------------------
Microsoft .NET SDK               Microsoft.dotnet
Microsoft .NET SDK 5.0.303 (x64) {b447173e-28f0-40ae-b0c8-15b9c0a1ad4b}

Sgt-Nukem · 2022-03-13T11:31:52Z

I have the opposite problem: There are NO installed packages found when trying to upgrade despite an update for it being found in the first place.
I found bug microsoft/winget-pkgs#47041 (comment) and wanted to comment there, but this got closed as duplicate and linked to here.

I am not sure these are the same bugs.

winget --version
v1.2.10271

winget upgrade
Name                                        Id                                          Version         Available       Source
------------------------------------------------------------------------------------------------------------------------------
<stuff before>
Microsoft Visual C++ 2008 Redistributable … Microsoft.VC++2008Redist-x86                9.0.30729.4148  9.0.30729.6161  winget
<stuff after>
52 upgrades available.

winget upgrade "Microsoft.VC++2008Redist-x86"
No installed package found matching input criteria.

winget upgrade --id "Microsoft.VC++2008Redist-x86"
No installed package found matching input criteria.

winget upgrade --name "Microsoft Visual C++ 2008 Redistributable - x86"
No installed package found matching input criteria.

winget upgrade --exact --id "Microsoft.VC++2008Redist-x86"
No installed package found matching input criteria.

winget upgrade --exact --name "Microsoft Visual C++ 2008 Redistributable - x86"
No installed package found matching input criteria.

niStee · 2022-03-28T16:04:44Z

I assume this is the error mentioned above:

PS C:\Users\username> winget upgrade --all
Found Microsoft Visual C++ 2015-2022 Redistributable (x86) [Microsoft.VC++2015-2022Redist-x86] Version 14.32.31302.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download.visualstudio.microsoft.com/download/pr/79465679-7995-4f6c-984b-33de61668fe4/37E08B5D6EDC325ACD805AD35CEE6506ADAF88ACCC7086BE2E771E69400AADE8/VC_redist.x86.exe
  ██████████████████████████████  13.0 MB / 13.0 MB
Successfully verified installer hash
Starting package install...
Successfully installed


PS C:\Users\username> winget upgrade
Name                                         Id                                Version          Available        Source
-----------------------------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2015-2022 Redistributa… Microsoft.VC++2015-2022Redist-x86 14.31.31103.0    14.32.31302.0    winget
1 upgrade available.

PudottaPommin · 2022-04-13T12:17:11Z

For me the resolution was to go into Control & Panel -> Programs and uninstall every version of problematic 'Microsoft Visual C++ YYYY Redistributable' package ... I had 4 versions and 3 seemed like broken references to non-existing installations. After cleaning that mess, upgrade works.

sba923 · 2022-04-13T19:03:36Z

For me the resolution was to go into Control & Panel -> Programs and uninstall every version of problematic 'Microsoft Visual C++ YYYY Redistributable' package ... I had 4 versions and 3 seemed like broken references to non-existing installations. After cleaning that mess, upgrade works.

Indeed, the mess can be impressive:

I've cleaned that up on all my PCs, now will monitor if further upgrades will work as expected.

denelon · 2023-01-24T00:21:47Z

@alkampfergit this issue is quite old and was full of different classes of errors. I believe the original issue you reported was due to the situation identified by @PudottaPommin.

@sba923 Have you encountered any more trouble after removing the "extra" entries?

We've made several improvements in WinGet 1.4 related to matching and the upgrade scenario with packages that are installed side-by-side.

ghost · 2023-01-31T01:02:28Z

@alkampfergit this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

alrasni1 · 2023-02-15T02:10:56Z

Brief description of your issue

I'm trying to update package Microsoft.VC++2013Redist-x64 because it cannot disambiguate between the package and a weird package with a guid

Steps to reproduce

Install an old version Microsoft.VC++2013Redist-x64 I'm not aware of the exact sequence of package to install.

Expected behavior

I want to be able to choose the exact package with the --id or --exact.

Actual behavior

I'm not able to update package Microsoft.VC++2013Redist-x64 because it continues to tells me that it is ambiguous with another package identified by a weird guid, as for the previous image.

Environment
Windows Package Manager v0.4.11391 Preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19043.1165
Package: Microsoft.DesktopAppInstaller v1.11.11391.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
--------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget

To solve the problem, you can use an install on behalf of the upgrade, thus solving your problem
Use command
winget install --id Microsoft.VC++2013Redist-x64

instead of it
winget upgrade --id Microsoft.VC++2013Redist-x64

Baardi · 2024-02-14T20:56:01Z

This is still happening as of 2024

ghost added the Needs-Triage Issue need to be triaged label Aug 30, 2021

denelon added Issue-Feature This is a feature request for the Windows Package Manager client. and removed Needs-Triage Issue need to be triaged labels Aug 30, 2021

denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Issue-Feature This is a feature request for the Windows Package Manager client. labels Oct 22, 2021

denelon added this to the v1.2-Client milestone Oct 22, 2021

denelon mentioned this issue Oct 29, 2021

winget upgrade by id and by name not working for Microsoft Visual C++ 2015-2019 Redistributable #1658

Closed

This was referenced Nov 11, 2021

Winget sees a package to update even the new version is installed side-by-ide #1693

Closed

upgrade using --id does not filter the right match #1696

Closed

The id and name options does not participate the filter as expected. #1715

Closed

denelon mentioned this issue Dec 8, 2021

Multiple installed packages found matching input criteria. Please refine the input #1784

Closed

icy-comet mentioned this issue Dec 23, 2021

Microsoft.VC++2015Redist-x86 Cannot Upgrade #1820

Closed

This was referenced Dec 28, 2021

Microsoft.VC++2008Redist-x86/x64 Cannot Upgrade #1823

Closed

Upgrading package by id error #1829

Closed

denelon modified the milestones: v1.2-Client, v1.3-Client Jan 8, 2022

This was referenced Mar 9, 2022

Reportedly available upgrade to Microsoft.VC++2008Redist-x86 cannot be installed #2010

Closed

Upgrading Microsoft.dotnet fails when multiple major versions are installed side-by-side #2011

Closed

denelon mentioned this issue Apr 1, 2022

Some packages will not listed by winget upgrade, even upgrade packages are available in winget repository #1093

Closed

denelon pinned this issue Apr 5, 2022

This was referenced Apr 20, 2022

winget always tries to update packages that are already up to date #2111

Closed

Uninstall before VC++2015-2022 before upgrading microsoft/winget-pkgs#58746

Closed

denelon mentioned this issue May 6, 2022

Winget -e incorrectly matches items #2142

Open

ryfu-msft unpinned this issue May 19, 2022

denelon modified the milestones: v1.3-Client, v1.4-Client May 31, 2022

Trenly mentioned this issue Jul 7, 2022

WinGet keeps reinstalling same updates that were marked as successful #2313

Closed

denelon mentioned this issue Jul 19, 2022

winget tries to upgrade .NET 5 Runtime over and over #2345

Open

Trenly mentioned this issue Jul 21, 2022

winget upgrade does not regognize installed updates #2349

Closed

alisonatwork mentioned this issue Aug 7, 2022

try to upgrade vc redist and desktop runtime x86, upgrades x64 instead #2427

Open

denelon modified the milestones: v1.4-Client, v1.5-Client Dec 28, 2022

denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Jan 24, 2023

ghost added the No-Recent-Activity Issue has no recent activity label Jan 31, 2023

denelon closed this as completed Feb 14, 2023

microsoft-github-policy-service bot removed the No-Recent-Activity Issue has no recent activity label Feb 15, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to disambiguate package Microsoft.VC++2013Redist-x64 #1413

Unable to disambiguate package Microsoft.VC++2013Redist-x64 #1413

alkampfergit commented Aug 30, 2021

alkampfergit commented Aug 30, 2021

zmira commented Sep 3, 2021

MagicFirefly commented Sep 12, 2021

jdhitsolutions commented Sep 13, 2021

ffes commented Oct 22, 2021

denelon commented Oct 22, 2021

ffes commented Oct 29, 2021

denelon commented Oct 29, 2021

jamesmyatt commented Nov 11, 2021 •

edited

Loading

denelon commented Jan 5, 2022

rcdailey commented Jan 7, 2022

denelon commented Jan 7, 2022

sba923 commented Mar 11, 2022

Sgt-Nukem commented Mar 13, 2022

niStee commented Mar 28, 2022 •

edited

Loading

PudottaPommin commented Apr 13, 2022

sba923 commented Apr 13, 2022

denelon commented Jan 24, 2023

ghost commented Jan 31, 2023

alrasni1 commented Feb 15, 2023

Brief description of your issue

Steps to reproduce

Expected behavior

Actual behavior

Environment

Baardi commented Feb 14, 2024

Unable to disambiguate package Microsoft.VC++2013Redist-x64 #1413

Unable to disambiguate package Microsoft.VC++2013Redist-x64 #1413

Comments

alkampfergit commented Aug 30, 2021

Brief description of your issue

Steps to reproduce

Expected behavior

Actual behavior

Environment

alkampfergit commented Aug 30, 2021

zmira commented Sep 3, 2021

MagicFirefly commented Sep 12, 2021

jdhitsolutions commented Sep 13, 2021

ffes commented Oct 22, 2021

denelon commented Oct 22, 2021

ffes commented Oct 29, 2021

denelon commented Oct 29, 2021

jamesmyatt commented Nov 11, 2021 • edited Loading

denelon commented Jan 5, 2022

rcdailey commented Jan 7, 2022

denelon commented Jan 7, 2022

sba923 commented Mar 11, 2022

Sgt-Nukem commented Mar 13, 2022

niStee commented Mar 28, 2022 • edited Loading

PudottaPommin commented Apr 13, 2022

sba923 commented Apr 13, 2022

denelon commented Jan 24, 2023

ghost commented Jan 31, 2023

alrasni1 commented Feb 15, 2023

Brief description of your issue

Steps to reproduce

Expected behavior

Actual behavior

Environment

Baardi commented Feb 14, 2024

jamesmyatt commented Nov 11, 2021 •

edited

Loading

niStee commented Mar 28, 2022 •

edited

Loading