none
Deploy Visual C++ out of sequence RRS feed

  • Question

  • Hi

    I have an issue with automating the installation of Visual C++ redistributables from SCCM out of sequence. Some of our applications require earlier versions of the Visual C++ redistributable than are already installed on our devices, this causes an issue because they cannot be installed out of sequence so the only option we currently have is to manually uninstall any later versions from the device, run the install package and then manually reinstall the version we had to remove back on top. This would be fine with the odd device but I can be deploying on anything up to 12000 nodes globally. Does anyone have a solution or idea as to how we can automate this so we don't have to manually intervene.

    Thanks, Gary

    Tuesday, September 17, 2019 1:33 PM

Answers

  • Yep, that issue is about builds of the same version and not different versions. The fact that the vendor requires an older version though basically falls under the category of stupid vendor tricks.

    Your only option here is to uninstall the newer build and install the older.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Gary Head Wednesday, September 18, 2019 3:18 PM
    Wednesday, September 18, 2019 12:23 PM
    Moderator

All replies

  • Sorry, what do you mean in sequence? There are no dependencies between the different versions of VC++ runtimes and thus the order in which they are installed is irrelevant. What issue is being reported?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, September 17, 2019 2:32 PM
    Moderator
  • Hi Jason

    Thanks for getting back to me. You definitely cannot install earlier versions over later versions, you definitely need to uninstall the later version first, install the earlier version then reinstall the later version. as an example try installing 

    2015 14.0.24123 over

    2015 14.0.24212 and see what result you get, it will refuse to allow the install and believe me I have had several people working on this.

    Here is an article from Autodesk suffering the exact same issue too

    https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Error-when-trying-to-install-earlier-version-of-Microsoft-Visual-C-2010-Redistributable-package.html

    Tuesday, September 17, 2019 4:07 PM
  • OK, that's why I was seeking clarification here as the word "version" is potentially ambiguous here.

    Your sequencing is for different *builds* of the same version of a runtime and not a different version of a runtime. Versions include 2008, 2010, 2012, 2015, and 2017 and have zero dependencies between them. 

    Your example above is specifically for installing an older build the 2015 runtimes. Why would you need to install the earlier build? The builds are all backwards compatible within a version of the runtime.

    The article you linked to is about a version issue, but I think that's more of an issue with their installer and not the runtimes themselves. 

    Ultimately, if I'm off-base here though, the solution is to use a script that detects the current versions installed, removes those that are, and reinstalls all those that are required in the correct order. There's nothing built-in to handle this although I do believe, based on the very small amount of info I have on the scenario, that you may be interpreting things incorrectly.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, September 17, 2019 4:20 PM
    Moderator
  • Hi Jason The reason for this is we received an update from a software supplier that specifically required the 123 version and 212 was already installed. We did test the app with 212 and unfortunately it did not work so that is how we have come to be in this situation. I think you are correct in that the only solution is a script that uninstalls the 212 version first and then installs 123.
    Wednesday, September 18, 2019 7:43 AM
  • Hi Jason

    I have just checked with our project team who have carried out some more tests for me and they say irrespective of the year it also still does not install as in this error message

    Error log:

    [2218:2524][2019-09-18T11:22:23]e000: Error 0x80070666: Cannot install a product when a newer version is installed.

    It would appear from further information I have found that this is in fact an issue with the C++ install rather than a deliberate feature as indicated here.

    https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install-wininstalls/how-to-fix-error-0x8007066/6f94d4ef-b3e4-4c7e-a2fe-c0bdbea52fac

    Thanks for your help Jason

    Wednesday, September 18, 2019 10:43 AM
  • Yep, that issue is about builds of the same version and not different versions. The fact that the vendor requires an older version though basically falls under the category of stupid vendor tricks.

    Your only option here is to uninstall the newer build and install the older.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Gary Head Wednesday, September 18, 2019 3:18 PM
    Wednesday, September 18, 2019 12:23 PM
    Moderator