Patch My PC Ideas & Feedback
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
In many cases VC++ 2015-2019 is not enough. Please add the older version. This can be automated with VCredist.
A module for lifecycle management of the Microsoft Visual C++ Redistributables. VcRedist downloads the supported (and unsupported) Redistributables, for local install, main image deployment or importing as applications into the Microsoft Deployment Toolkit or Microsoft Endpoint Configuration Manager. Supports passive and silent installs and uninstalls of the Visual C+
We included these legacy, end-of-life Microsoft Visual C++ Redistributables because they remain critical prerequisites for numerous applications. Given the number of customers who rely on these components, the benefits of inclusion outweigh the drawbacks of maintaining EOL software in our catalog.
Good News! Microsoft Visual C++ 2008, 2010, 2012, and 2013 Redistributables have been added to the catalog as of yesterday - https://patchmypc.com/catalog-release-history/
@Adam
Some installers have some very old Microsoft Visual C++ Redistributables embedded in them, it would be nice to update them at least to the lastest available version
I agree, but e.g. VC++ 2010 (x86/x64) and Visual Studio 2010 Tools for Office Runtime (x64) is a requirement for SAP HANA ;-) Your win is expanding your catalog with very little work and make your customers even more happy. Maybe someday a zero day exploit appears, which would force MS to patch, even unsupported.
I'll start the discussion internally but the older versions are unsupported by Microsoft and we generally do not keep unsupported products in our catalogue.
Also, because they're unsupported, I'm curious what the value add is if we did add them to the catalogue? Unsupported software isn't updated so the versions remain static. In this scenario, creating a manual package is generally a one-time effort on the customers' part. I can appreciate the desire to create a software update, application or Intune package with all the consistent metadata made by the Publisher if that's the train of thought.
this should be simple, already in evergreen