Block Visual C++ 2015-2019 when Visual Visual C++ 2015-2022 is selected

GeoSimos · September 27, 2022, 08:32:10 AM

Hello PMPC Team,

As always, thank you for your great product and support.

I have both runtimes selected (for both architectures) in the ConfigMgr apps list, their updates are also served, the issue I'm facing is that when Visual Visual C++ 2015-2022 runtime is installed and subsequently Visual C++ 2015-2019 update tries to install, it fails because the 2015-2022 version is newer and supersedes it.
I would like to propose the following:
1) The detection rules of 2015-2019 should detect the newer version(s) and skip the installation for a full app or an update.
2) In the PMPC GUI, there must be a blocking function that grays out and deselects (if selected) the older version if a newer is superseding it (for the 2015-xxxx ones). Also a message to remove the old application would be nice.

Do these proposals make sense to you?
Are the above feasible?

With regards,
George Simos

Andrew Jimenez (Patch My PC) · September 28, 2022, 03:43:55 PM

Hi George,.

Thank you for these suggestions, I honestly think the solution here will be to replace Visual C++ 2015-2019 with Visual C++ 2015-2022. I am going to do some research on this and see if that will be an acceptable solution.

GeoSimos · February 15, 2023, 02:50:43 PM

Hi Andrew,

Just checking if there is any development on this request.

Thank you!

Andrew Jimenez (Patch My PC) · February 22, 2023, 03:15:26 PM

I'll revisit this next week. I've blocked off some time to look deeper into this. Thanks for the reminder!

Andrew Jimenez (Patch My PC) · February 28, 2023, 01:11:05 PM

Our plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

GeoSimos · February 28, 2023, 02:14:25 PM

Thank you very much Andrew!
If you're going to MMS-MOA in May, it would be great to meet there and talk about the product.

Andrew Jimenez (Patch My PC) · March 02, 2023, 02:20:37 PM

Definitely, I will be at MMS!

GeoSimos · April 18, 2023, 03:59:59 AM

Quote from: Andrew Jimenez (Patch My PC) on February 28, 2023, 01:11:05 PMOur plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

I had a discussion with a SharePoint Admin colleague because I noticed that the installer installs the 2015-2019 redistributable, so AFAI understand, it will not be easy to get rid of it (I would love to have a clean environment with less versions to maintain).
Could you check with the SP PG if this is a hard requirement and if it can be covered by the 2015-2022 redistributable please?

Clock is ticking for MMS-MOA

GeoSimos · May 25, 2023, 04:40:56 AM

Hi Andrew,

I checked on Microsoft's SharePoint resources for the VC++ requirements and it seems that we can go with 2015-2022 for the versions of SharePoint 2016 and onwards.
Also checked our servers and discussed this with our SharePoint Admins and we reached to the conclusion of using that one and replacing the 2015-2019 were it is installed.
Did you do any research from your side?

Andrew Jimenez (Patch My PC) · May 25, 2023, 10:52:51 AM

This is perfect, everything I have seen shows 2015-2022 as a drop-in replacement for 2015-2019. We are planning on removing 2015-2019 and replacing it with 2015-2022 this month (with the next Publisher release).

GeoSimos · May 26, 2023, 03:23:42 AM

Great news, thank you Andrew!
I guess it will be stated in the notification emails right?

Andrew Jimenez (Patch My PC) · May 26, 2023, 09:57:13 AM

Yes, we will be sure to mention it in the notification emails, and I'll update this thread when we ship that change.

GeoSimos · May 26, 2023, 09:58:39 AM

Perfect!
Thank you and have a nice weekend!

GeoSimos · January 11, 2024, 03:51:41 PM

Quote from: Andrew Jimenez (Patch My PC) on February 28, 2023, 01:11:05 PMOur plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

Happy New Year Andrew!

Has this change shipped? I still see updates of 2015-2019 trying to install when we do imaging/reimaging of devices.
At least for the runtimes published as updates, wouldn't it make sense to set the 2015-2019 as superseded by 2015-2022?
This would make our lives easier as we can target the 2015-2022 to machines that have 2015-2019 and upgrade them, right now they are just clashing.