Skip to main content
scottnorrisphotography
scottnorrisphotography
Participant
July 8, 2021
Answered

MSVCR110.dll is missing - After Effects will not start

  • July 8, 2021
  • 5 replies
  • 20167 views

I am getting these messages:  "The code execution cannot proceed because MSVCP110.dll was not found. Reinstalling the program may fix this problem."
"The code execution cannot proceed because MSVCR110.dll was not found. Reinstalling the program may fix this problem."

After Effects will not start (2019, 2020, 2021), but PS, AI, LR, etc will.  I have reinstalled AE 2021 and also reinstalled Microsoft Visual C++ Redistributable with no luck.  Any thoughts?

    Correct answer scottnorrisphotography

    I think I found the solution.  I uninstalled and reinstalled Visual C++ Redistributable for Visual Studio 2012 Update 4 https://www.microsoft.com/en-us/download/details.aspx?id=30679&tduid=%28df9556b3dcc63111a51acc05582ba116%29%28256380%29%282459594%29%28TnL5HPStwNw-Nt10fD_ZWXvC_Wh.N3Cm9A%29%28%29

    and that seemed to fix it.

     

    5 replies

    J
    jasonb39199225
    Participant
    June 15, 2022

    Something that worked for me.  I took Melonika's advice and uninstalled VC ++, deleted all my Adobe Products (including After Effects) and then Adobe Creative Suite.  I then reinstalled Adobe Creative Suite and After Effects but still got the same Msvcr110.ll error.  Then when I searched for VC ++ under Windows Explorer I realized I had 12 more VC ++ files from different years.  I deleted all the VC ++ files, uninstalled Adobe Creative Suite and After Effects and restarted the computer.  I reinstalled Adobe Creative Suite and After Effects and finally after 5 hour I was able to successfully open After Effects!

    A
    Andrew23250744nzwf
    Participant
    February 20, 2022

    Nothing was working, not even the most recent redistributables, but this solved it! I wonder why specifically the 2012 version made it better...

      melonika
      melonika
      Participant
      January 15, 2022

      I had same issue in January of 2022, Windows 10 - 64bit, with premier pro.

      For me, doesnt work any solution what I found but finally I fixed it. 

      In this case need to reinstall the VC++ Runtime Libary in windows system but in other way.

       

      When you make a Premier Pro clean install, the installation process will detect IF you don't have any VC++ package in the system and will install the correct package automatically.

       

      So uninstall the all VC++ package and uninstall the Premier Pro (or other app what is showing similar error). After install again the Premier Pro.

      The Premier Pro install process will install the correct VC++ Runtime Libary in the background automatically.

       

      When I tried to remove and reinstall the VC++ package manually, I got same error.

      But In this way the problem has been solved.

      G
      gregg86099622
      Participant
      November 28, 2021

      This worked for me.  Thank you!

        scottnorrisphotography
        scottnorrisphotographyAuthorCorrect answer
        Participant
        July 8, 2021

        I think I found the solution.  I uninstalled and reinstalled Visual C++ Redistributable for Visual Studio 2012 Update 4 https://www.microsoft.com/en-us/download/details.aspx?id=30679&tduid=%28df9556b3dcc63111a51acc05582ba116%29%28256380%29%282459594%29%28TnL5HPStwNw-Nt10fD_ZWXvC_Wh.N3Cm9A%29%28%29

        and that seemed to fix it.

         

          CorySouthpaw
          CorySouthpaw
          Participating Frequently
          July 24, 2021

          @scottnorrisphotography thank you for providing a direct link! Feel like it can get confusing with the # of windows installers.  To add some info was getting the error upon opening 17.5, tried updating to 17.7 hoping that would fix the issue but then started reading about the Visual studio fix. 

           

          Saw the same answer listed here but the links were all dead..  Installed both vcredist_x64.exe and vcredist_x86.exe, did not seem to need the 3rd file.  After that did a quick "restart" for good measure and now AE opened!  Just wish I didn't bother updating AE.

            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices