Skip to main content
f_yoel
f_yoel
Participant
November 5, 2019
解決済み

After update to Premiere 2020 - software won't open and crash

  • November 5, 2019
  • 返信数 15.
  • 28706 ビュー

After update to Premiere 2020 - software won't open and crash

 

Same happens with After Effects - crashes after updating today.

 

Please help:

 

Process: Adobe Premiere Pro 2020 [853]
Path: /Applications/Adobe Premiere Pro 2020/Adobe Premiere Pro 2020.app/Contents/MacOS/Adobe Premiere Pro 2020
Identifier: com.adobe.PremierePro.14
Version: 14.0 (14.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Adobe Premiere Pro 2020 [853]
User ID: 501

Date/Time: 2019-11-05 15:55:29.563 +0200
OS Version: Mac OS X 10.14.6 (18G87)
Report Version: 12
Anonymous UUID: 18133263-D2D0-A303-ECF1-2E7FB1A7AAC7


Time Awake Since Boot: 1100 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x000000014de43000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x2

 

    このトピックへの返信は締め切られました。
    解決に役立った回答 f_yoel

    Issue resolved 

     

    I got assistance from the Adobe online support team. The problem was a plugin that was causing the crash.

    So I removed it and now its all good.   

     

    Try to get online assistance from the Adobe team: https://helpx.adobe.com/support/premiere-pro.html?guid=6d38fd90-7ff9-4829-9111-154e4cb5df19&location=PDP&product=Creative%20Cloud%20Desktop&product-version=5.0.0.354&mv=product&mv2=accc#    

     

    click on the "contact us" for online chat with help desk

    返信数 15

    D
    DONE220496388agg
    Participant
    December 2, 2021
    1.  
    tombkn
    tombkn
    Participant
    November 7, 2020

    Hey, 

     

    What was the plugin causing the crash? I have the exact same issues. I can't open premier after the latest update 😞

     

    Please help !

    Thanks

    D
    Design-Kink
    Participating Frequently
    November 8, 2020

    I don't know what the plugin was, probably an old version of Titler Pro or Boris in my case...

    I just followed instructions above and removed everything, started from scratch, working now

    Reuben@Blueprint
    Reuben@Blueprint
    Participating Frequently
    October 7, 2020

    Tried the mediacore folder plug ins, tried re naming Premiere Pro folder - nothing has worked. Don't have a solution but a workaround. I'm running Catalina 10.15.7 and Premiere Pro 14.4.0 and I could get to the first screen with previous projects but couldn't get Premiere to open any previous projects. So If i create a new project named untitled all opens up and then from there I can open previous projects. Not great but if you need to get thiongs done this works for me.

    D
    Doug Nagel
    Participant
    October 9, 2020

    I've had similar issues lately and no amount of pref trashing and Premiere re-installing brought success. I discoved that for me the smoking gun was the "Enable Mercury Transmit" option under Prefs/Playback. If this is checked, then existing projects will crash on load (although only after PP has been quit and re-opened.) So my workaround has been to make sure "Enable Mercury Transmit" is unchecked before I load any existing projects. Annoying proceedure, but it has been working consistantly.

    R
    rlowers
    Participant
    July 7, 2020

    I am happy the solution of thrashing whatever plug-ins worked for you but that did not work for me nor did, trashing/resetting preferences, trashing cache files, trashing MediaCore files. What DID WORK was uninstalling the updated version of Premiere Pro (14.3) and reinstalling the previous version (14.2). There is a problem with Catalina and Adobe Premiere & After Effects. The same problem (PP files crashed/quit PP) occurred when I upgraded to Catalina 15.15.5. I was using Premiere Pro 14.2 and my videos crashed/quit PP. After hours of doing everything(!) I had to uninstall Catalina 15.15.5 and reinstall Catalina 15.15.4. All was well. ALL my files worked. Once again when I updated Premiere Pro 14.3 my old video files would not open. They crashed/quit PP. And the ONLY thing that was different was the update. SO uninstall the update.

    Hope this helps!

    mmm2020
    mmm2020
    Participant
    May 26, 2020

    you are so stupid why dont you say the solution? every bodey knows how to chat with adobe 

    D
    DonnaDunlap
    Participant
    March 28, 2020

    I'm not getting much help on Chat. Do answer in over an hour. I have the same problem. What plugin was causing the problem for you?

    Ann Bens
    Community Expert
    Ann BensCommunity Expert
    Community Expert
    March 28, 2020

    How about deleting them all and adding them one by one.

    H
    Hoff Haus
    Participant
    December 20, 2019

    For Windows machines, I think the .dll file you need to remove is called rthdasio64.dll

    This is the file that the Adobe support agent told me about.  So if you're on Windows, search for that .dll file in the search bar, try to remove it, then open premiere pro. 

    It worked for me!  hope it works for you!

    D
    DonnaDunlap
    Participant
    March 28, 2020

    Nope didn't work for me 😞

     

    byjono
    byjono
    Inspiring
    March 28, 2020

    Have you tried finding your "Mediacore" folder and removing all the plugins? You can add them back in and eliminate the one giving you a problem that way...

    Concept-Production
    Concept-Production
    Inspiring
    November 29, 2019

    Hi f_yoel, what plugin was causing the problem? because I’m facing exactly the same issue.


    Erns R.
    R
    rolfHellmeier
    Participating Frequently
    November 29, 2019

    Path of the enemy "Insta360Proimporter.bundle" is : (common)Library/Applikation Support/Adobe/Common/Plug-ins/7.0/Mediacore/

     

    in the case you use a Mac...;-)

     

    Rolf Hellmeier, Dipl.Des.

    Concept-Production
    Concept-Production
    Inspiring
    November 29, 2019

    You are absolutely the guide to my solution and this is what I did

    From my mac:

     

    I went to my Mac HD> Library> Application Support> Adobe> Common> Plug-ins> 7.0> MediaCore

     

    And remove all the existing plug-ins to my Desktop , except the folder call <Public> and <dummy.text> file.

     

    I launch my Adobe and it works fine, and then I added one by one all the folders containing my plug-ins to find out the one that was causing the problem and I delete it completely.
    Now everything works fine.    


    Erns R.
    NewHope_David
    NewHope_David
    Participant
    November 24, 2019

    After talking to support, i found out that the plugin for Insta360 cameras was my culprit.  Its labeld as insv.bundle in my plugins->mediacore folder

      R
      rolfHellmeier
      Participating Frequently
      November 25, 2019

      Thanks very much..... that solved my problem, Premiere Pro started.

      Path of the enemy "Insta360Proimporter.bundle" is : (common)Library/Applikation Support/Adobe/Common/Plug-ins/7.0/Mediacore/

       

      kind Regards 

      Rolf Hellmeier

        L
        Leeuw_1974
        Participant
        March 29, 2020

        Thanks a lot David and Rolf,

         

        Problem solved after removing "Insta360Proimporter.bundle"!!!!

         

        Best regards,

        Patrick

          T
          Terene Johnson
          Participant
          November 20, 2019

          Tech Support helped me with this issue. I had to rename the Premiere Pro folder to "Premiere Pro old" and that fixed it. Keep in mind that this was not the folder in the Applications folder, but the one in your "Adobe" folder. This may be in your Documents folder by default.

            Kevin-Monahan
            Community Manager
            Kevin-MonahanCommunity Manager
            Community Manager
            November 20, 2019

            Thanks for the report Terene. This issue happens frequently to the Adobe folder when updating macOS. Please make a note of it as the next update with macOS could cause the same issue. If you need to maintain the file paths of your current Documents folder, you can simply change R Only permissions to R/W. See this article.

             

            Thank You,
            Kevin

            Kevin Monahan - Sr. Community &amp; Engagement Strategist – Pro Video and Audio
            さらに返信を表示
            契約条件Accessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices