Completely understood and appreciated.Recommendations to use MP2 instead MP1 are a delicate subject. Please keep in mind that both products are independent developments. I can’t comment on MP 1.20’s needs.
That still leaves 1.2 with the legacy issue. I had originally attempted to install 2.1 and the blockage led to my original report for that version. It is unfortunate that the actual cause is opaque, has been caused by external libraries, and that there appears to be no easy workaround short of a patched release for 2.1. I guess it all comes down to the project release schedule and how much longer 2.1 will be supported?In any case the new 2.2 Final will install VC++ 2017 regardless of VC++ 2015 being present or not.