MSVCP120.dll STILL missing after Visual C++ reinstalls

[Cnoctem]

I've just reinstalled Photoshop Elements 2023, after a fresh Win10 reinstall.  Photo editor will not launch, and is giving me the "missing MSVCP120.dll" error.

Every discussion I've read about this error has the same solution:  uninstall and reinstall newest Visual C++ package.
I've done that, including both the x64 and x86 versions, with restarts between every step.  Still getting the same error.
What are the next steps when this solution doesn't work?
Thanks.

[davescm]

Hi , I've moved your post from the Photoshop forum to the Photoshop Elements forum where you are more likely to get help relevant to your issue.

Dave

[Peru Bob]

Just a longshot (no harm in trying):

Try installing and updating the Creative Cloud application before installing Photoshop Elements:
https://helpx.adobe.com/download-install/kb/creative-cloud-desktop-app-download.html

[Cnoctem]

Thanks, I tried that, it made no difference.  The odd thing is, it loaded with no problem just a few weeks ago, on the same version of Windows (different install).  Is there a way to load Photoshop Elements directly, without going through the Adobe loader screen?

[Peru Bob]

Open it from the exe file in Program Files.

Make a shortcut for it.

[Cnoctem]

Same error. 

Here's a possible clue:  Elements is installed on a secondary drive rather than C drive.  Is Elements known to have problems when being installed/run on a non-C drive?

[Brenda22828709dlmo]

I am having EXACTLY the same problem with a brand new Dell Laptop with Windows 11. I AM able to install Photoshop Elements 2024 and it seems to work but am getting the dreaded missing file message when installing Premiere 2023. I have tried to install the missing VIsual C++ library as directed and it make no difference at all. I have even tried placing a copy of the missing file in several directories in an attempt to aid the process. That did not work either. HELP!!!

[walkabouter]

I have had the same problem too and I have not had any luck but much to my surprise I happened to double click on a JPEG image to open it with something and Photoshop elements 2023 showed up as an option and it seemed to work but I have not used it a lot yet.  It is not on the start menu so it looks like the install failed before it did that.   The Orginizer application is in the programs files too but it seems to have lots of problem.  At least it looks like the editor is there which is mainly what I use.  Be aware that if you give up and "buy" Photoshop Elements 2025 it is only a three year subscription now.  

[Steerpike58 · Accepted solution]

I had the exact same problem on a brand new Win 11 Home laptop.  PE 2023 was working fine on my slightly older Win 11 Home laptop, so I compared (control panel / programs and features) the two sets of Microsoft Visual C++ entries.  Both laptops had the latest MS VC's - "2015-2022 Redistributable" (x86 and x64 versions).  Both had the 2012 versions. But only the working laptop had the 2013 versions, so I found a place to download all the various MS VC components in one go - Latest Visual C++ Redistributable Runtimes All-in-One Nov 2024 Download | TechPowerUp

The recommendation is to install ALL of them, to prevent future issues with other programs, but I installed just the 2013 x86 and x64 versions, and now, PE 2023 runs fine.  Amazing that Adobe does not include this required component in their installation package.  It took me several hours to troubleshoot and solve this. 

Non-working (new) laptop: 

Older, working laptop: 

Fixed new laptop: 

[博谦25663974l3oo]

Thank you. The 2013 version solves this problem, very good found!

[tony_7181]

worked for me too

[Astonished_Fountain0632]

Fantastic, many thanks Steerpike58 - great to have found this, problem sorted instantly by your post (ending hours of frustration looking at totally unhelpful microsoft pages)

[mlepitt]

This still did not work for me after installing the 2013 x64 package.  I had to install the x86 package as well for this to work.  I also installed 2012 to match this answer just in case, but it was most likely the x86 version of the 2013 package that fixed it.

[Steerpike58]

In my 'accepted solution' post, I installed both x86 and x64 versions of the 2013 package, and PE worked.  You said you installed ONLY the x64 version at first, and it did not solve it; then you installed x86 version and it worked.  It would be interesting if the next person who tries this first installs ONLY the x86 version, and tests.  It could be (as you suggest) that the x86 version is the only one needed, but it could also be that both versions are needed.  

Upon further checking, I see that PE 2023 is a 32 bit program! it resides in the Program Files (x86) folder.  So it's quite likely that all you need is the x86 version of the DLL. 

[Glenn 8675309]

Many of you are thinking "Why a 2013 version"?  It's works just fine, many program writers use it becouase it works for their purpose.   That's why it is still around.

here is an AI response:

MSVCP120.dll is part of the Microsoft Visual C++ 2013 Redistributable package, which contains essential functions used by many applications developed with Visual C++. Even though newer versions of Visual C++ exist, some software still relies on older versions for compatibility reasons. If you're encountering a missing MSVCP120.dll error, reinstalling the Microsoft Visual C++ 2013 Redistributable might resolve the issue.

Since you're working with Photoshop Elements, this error has been reported by other users when launching the software, even after reinstalling Visual C++. If reinstalling doesn't work, you might try installing Adobe Creative Cloud before Photoshop Elements, or running the program directly from its executable file. Let me know if you need help troubleshooting!

[Glenn 8675309]

The Microsoft Visual C++ 2013 Redistributable is still used because many applications, including those built with older versions of Visual Studio, still rely on it. While it officially reached end-of-life support in 2024, it's not always feasible to immediately upgrade software to use newer versions of the redistributable. 

Here's a more detailed explanation:

• Application Dependency:

  Some applications, especially those developed using earlier versions of Visual Studio, were compiled with the 2013 redistributable. These applications still require the 2013 redistributable to function properly. 
• Backward Compatibility:

  Even though newer versions exist, applications may not be designed to automatically switch to a newer version. They might require the specific 2013 version to run, leading to incompatibilities if a newer version is installed. 
• End-of-Life:

  While Microsoft officially discontinued support for the 2013 redistributable on April 9, 2024, many applications and programs are still using it. The support for the 2013 version was officially ended, but many older applications still rely on the redistributable. 
• Migration Costs:

  Upgrading software to use newer redistributables can be a time-consuming and complex process, especially for older applications. This can involve significant testing and code changes. 
• Software Versioning:

  Some software versions are tied to specific redistributable versions. For example, Moldflow 2019 uses the 2010 and 2012 redistributables, while Moldflow 2021 uses 2012 and 2019, according to Autodesk. 

[Steerpike58]

I'm not surprised by the dependency on a 2013 package; what I AM surprised by is the fact that Adobe don't realize this; or if they do realize it, they don't do anything about it! 

Adobe is not some amateur home coder putting together a free utility; they are a major corporation charging serious money for their applications, so you would think they would be smart enough to look for the 2013 package during the install, and if it's not already installed, then install it.   The fact that we users are forced to figure this out for ourselves is pretty shameful, really!