Winget highlights update errors with the Visual C++ Studio 2015-2022 Redistributable (x64) as well as outdated content in the associated Microsoft Learn article. A guest post by Jo Arnold
Replacing the sometimes countless installed redistributable version numbers that come with various software on the computer with an installation of the latest version from 2005, 2008, 2010, 2012 and 2015-2022 ultimately uncovered an error in connection with Microsoft Visual C++ Studio 2015-2022 Redistributable (x64) with winget and the outdated information not only about the Microsoft Visual C++ 2008 Redistributable under Microoft Learn. An experience report. Left at the bottom of the page.
Microsoft Learn
There is actually a very useful page under Microsoft Learn (link at the bottom of the page) that provides an overview of the (supposedly) latest error-free updates and downloads for all versions. From version 2005 to 2022, I installed the latest versions for (x64) and (x86) as a test. ARM64 has not been tested.
Using the Microsoft Learn downloads actually completely replaces the various sub-variants of the same Visual Studio versions. This can be seen for (x64) and (x86) in the lists of CPL programs and features as well as in the stripped-down and not particularly practical presentation of the apps and features. The tests carried out after the update on previously installed software, each of which had its own redistributable subversion numbers, all ran without errors. If I then installed another piece of software that I knew had always installed an outdated redistributable subversion number, this no longer happened. Everything is going as expected and desired.
Downloads and information on Microsoft Learn are not up to date
Microsoft Learn states that for VC++ Visual Studio 2008, 9.0.30729.5677 (x64) + (x86) is the most current version. After the installation, Winget immediately displayed version 9.0.30729.6161 as an update (links at the bottom of the page). Update via winget then runs without errors. This has also been affecting the 2015-2022 version of Microsoft Learn for some time now. Conclusion: Microsoft Learn has not been updated here.
Update error with Visual Studio 2015-2022 Redistributable (x64)
I also installed the redistributable version 2015-2022 in the variants (x64) and (x86), which appear in Programs and Features as well as under Apps and Features with the expected version number and information about (x64) and (x86). Winget list also listed the Microsoft Visual C++ 2015-2022 Redist… twice in the output. So far correct and I didn't pay any further attention to the details in winget until a few weeks ago.
For some time now, winget has been offering an update from 14.38 to v.14.40.33617.1 for the two 2015-2022 redistributables. After a while I first made a comparison with Microsoft Learn, but it still describes – let's say – the old version 14.38 and the download there only brings the old installation files. The signature of the 14.40 installer has a timestamp of February 18, 2024. ARM64 has not been tested. Conclusion: Microsoft Learn has not been updated here.
The new download link is displayed with “winget show Microsoft.VCRedist.2015+.x64″ and Microsoft.VCRedist.2015+.x86” (link at the bottom of the page). I installed the latest v.14.40 first via winget and later via manual download. Why this happened several times now follows.
After the update, v.14.40 was correctly listed under Programs and Features as well as Apps and Features with (x64) and (x86). But with winget things look completely different. Regardless of whether the old (x64) v.14.38 from Microsoft Learn or the new (x64) is installed via the download link from winget: winget only sees both (x64) “partially” as (x86).
As you can see, this is easy to overlook. Only when you update the (x64) with winget. So winget carries out the update, but pulls the update for the (x86) and then the software in winget is still thirsty for the new version, you may notice that something is wrong here.
Installed manually are (x64) + (x86) v.14.38.33135.0 (source: Microsoft Learn)
- winget list
- Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.38.33135.0
- Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.38.33135.0
- Both uninstalled, then just reinstalled (x64).
- winget list
- Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.38.33135.0
In both variants, winget displays the variant (x86) as the ID for (x64).
Installed manually are (x64) + (x86) v.14.40.33617.1 (source: winget Links)
- winget list
- Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.40.33617.1
-Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.40.33617.1
Both uninstalled, then just reinstalled (x64).
- winget list
- Microsoft Visual C++ 2015-2022 Microsoft.VCRedist.2015+.x86 14.40.33617.1
In both variants, winget displays the variant (x86) as the ID for (x64).
If you make the cmd window wider, the columns are also wider and the result becomes more obvious:
- winget list
- Microsoft Visual C++ 2015-2022 Redistributable (x64) Microsoft.VCRedist.2015+.x86 14.40.33617.1
The name of the (x64) is assigned the Microsoft.VCRedist.2015+.x86 as the package ID.
Impact:
If you install the displayed update from 14.38 to 14.40 with winget for the (x64), then the setup in winget somehow runs successfully, but it installs the update for the (x86), if the (x86) is next to the (x64) at all is available. Therefore, after updating the incorrectly displayed (x86) ID, the software with the name of (x64) is of course not up to date.
- The problem has existed at least since version 14.38.33135.0 and even before v.14.40 was available via winget.
- The query based on the name shows the correct assignment to (x64) with winget:
- winget show “Microsoft Visual C++ 2015-2022 Redistributable (x64)
As I understand it so far, the updates run via the ID without any further action, which is why the updated update is ineffective due to the incorrectly assigned ID. So if you want to verifiably update a (x64) from before v.14.40, you can do the update manually in winget, for example, using the modified ID Microsoft.VCRedist.2015+.x64 and that will work.
- winget update Microsoft.VCRedist.2015+.x64
winget show Microsoft.VCRedist.2015+.x64 displays the current download link. A manual download can then be initiated via browser. Practical because you then also have the source for other computers. But neither method solves the problem that the (x64) v.14.40 is again assigned to the wrong ID with Microsoft.VCRedist.2015+.x86. This will cause the same error in future updates.
I've been dealing with this topic for some time now. There is already at least one reported issue on the topic on Github. It seems that winget is pushing the responsibility here onto Microsoft. But it also gives the impression that winget has not checked this and therefore cannot prove that the incorrect ID assignment was not created by winget.
Maybe this article will help the unfortunate problem finally be heard and eliminated.