C++ Redistributes File for Install

xmicahxxmicahx Member Posts: 66 ✭✭
Currently the desktop install requires a specific 2015 version if the Microsoft Visual C++ Redistributable. I have at least 90 users, just in this office, running the 2017 version that I would have to roll back before installing Adept. I then have to re-update them to the 2017 version to avoid issues with other software.

I believe this is being addressed, but I need to confirm if will be fixed with the 2018 SP1 release or will it not be available until the 2019 Adept release. 

Has anyone else dealt with this issue? How did you handle it? Thank you!


  • xmicahxxmicahx Member Posts: 66 ✭✭

    With Adept 2018 UP1, I was able to install with C++ 2017 versions 14.12.25810, 14.14.26429 or 14.15.26706. 

    I found a machine that has C++ 2015 version 14.0.23026. This 2015 version was to old to let UP1 install. What is interesting is that from this old 2015 version, I installed 2017 version 14.16.27027 and Adept installed, completely skipping the required 2015 version. 

    I found another machine with an old 2015 version and updated it to the required 2015 version 14.0.24215. Before doing anything else I upgraded it again to the 2017 version 14.16.27027. I found that the 2017 version removed the 2015 version from the installed apps list, however, Adept did install.

    After downloading 2018.1, I have seen that it comes with C++ 2017 version 14.15.26706, so hopefully rolling back to the 2015 version isn't an issue anymore...
  • MattWMattW Member Posts: 1
    Hi All!

    Yes, Microsoft has changed the VC++ installations with VC++ 2017.  Previously, different versions could be installed side by side.  For example you could install VC++ 2008 and VC++2015 on the same machine and there would be two distinct entries in Add Remove Programs, etc.  With VC++ 2017, things have changed.  This is an actual Upgrade to the 2015 runtimes.  In this case, if VC++ 2015 is installed then 2017 is installed afterwards, the later replaces the former.

    What does that mean for UP1?  If you're target machines already have 2017 runtimes installed, the VC++ requirement for 2015 will be checked during install, the higher installed version will be detected, and 2015 installation will be skipped.  At this point the installation of the 2015 runtime would not be allowed.

    So if you have 2017 already installed and you are installing 2018 UP1, you should be fine.  If you do experience post build runtime issues, please contact Customer Support so the role of the runtime change can be determined.

    Not to confuse Microsoft matters any further, but they did release problematic versions of the 2017 runtimes.  The problem was that a registry key to determine installed version was removed during their installation process.  So, for example, let's say 2017 is installed, but it is one of their bad releases and the required registry information is not present.  Now, you install UP1 which requires VC++ 2015.  The registry will be checked to determine installed version, nothing will be found and the 2015 installation will proceed, AND will be problematic.

    The version of the 2017 VC++ runtime we are currently deploying is a fixed version.  Unfortunately, Microsoft broke things once or twice after this release.  I believe the latest version of the 2017 runtimes which can be downloaded from Microsoft are OK at this point.  Here is a link with more information on this and I believe the link to the latest is in there somewhere.


    I hope this helps explain things!

Sign In or Register to comment.