Elements 2018: Core-Version: 16.0 (20170902.m.113423) unsupported visual c++ Runtimes

  • 1
  • Problem
  • Updated 7 days ago
  • (Edited)
Dear Adobe -Team,
We have created an offline package for Adobe Photoshop Elements 2018 using Creative Cloud Packager.
We have find out, the sorftware package contains Visual c++ runtimes 2005 and 2008.
These visual c++ Runtimes are not supportet any more and they are not compatible with Windows 10, see

and  so we cannot deploy the package.
We can remove these runtimes from the created package, but we don't know, what doen't work after this.
See https://helpx.adobe.com/enterprise/kb/choose-cpp-runtime-versions.html#Introduction
Please inform us which functions are affected, which functions will not run as required.
Please give us instructions as to how we should proceed. Otherwise, this software can not be used because it poses a security risk.

Best regards
Photo of cev A

cev A

  • 2 Posts
  • 0 Reply Likes

Posted 2 weeks ago

  • 1
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 110 Reply Likes

  The link you provide, https://support.microsoft.com/de-de/lifecycle/search/1117, is not a list of the Visual C++ Runtimes. It is a list of the Visual (Studio) developer kits. The difference being, the runtimes are OS updates and the developer kits are used write and compile code to create applications. Or, as Microsoft puts it, "Visual C++ Redistributable Packages install runtime components of Visual C++ Libraries on a computer that does not have Visual C++ installed. The libraries are required to run applications that are developed by using the corresponding version of Visual C++" (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads). 

  That is, if a component was created with a specific development kit the corresponding runtime library must be installed to use it. Adobe installers include these redistributable installers to install the necessary runtimes just in case your system doesn't already have them installed, though normal installation of Windows updates should address this. What the link you provide says is that if you are using an old developer kit to create applications, you should upgrade to a newer developer kit.

  There isn't really a reason to remove the VC++ updates from your package deployment, these runtimes are compatible with Windows 10. But you can follow the directions in the other documentation if you feel the need. This is not recommended though as it is the equivalent of deleting random DLL files from you system. Some things may continue to work fine, some features may not work outright, and others may have dependencies that are derived from multiple runtimes. Then again, the required runtimes may already be present on the machines and not including the redistributables will reduce the deployment overhead. 

  A more comprehensive look at this subject is available here: https://www.howtogeek.com/256245/why-are-there-so-many-microsoft-visual-c-redistributables-installed...

Photo of cev A

cev A

  • 2 Posts
  • 0 Reply Likes
Under these conditions, we may not use the software. Is there any notice from Adobe regarding this requirement, followed by a software update?