Skip to main content
ismaelviento
ismaelviento
Participant
April 5, 2018
Answered

Premiere Pro CC 2018. The application was unable to start correctly (0xc0000005)

  • April 5, 2018
  • 52 replies
  • 58985 views

Since i have updated the last version of Adobe Premiere Pro CC 2018 on my laptop last week, I'm no able to start anymore the application as the following notification window error pops-up:

THE APPLICATION WAS UNABLE TO START CORRECTLY (0xc0000005). CLICK OK TO CLOSE THE APPLICATION

I am kindly asking help to solved this issue because I've been searching this issue on the web and you tube with no possible solution till now

I thank you in advance

Best regards

Logan

    This topic has been closed for replies.
    Correct answer Vidya Sagar

    Hi All,

    Sorry for the inconvenience. A bug is filed and the issue is under investigation.

    Currently, the known workarounds are:

    1. If the system is configured with Nvidia card, disable it.

         Steps: Go to Device Manager > Display Adapters.

                     Right click on Nvidia and disable it.

                     Once done, try to launch Premiere Pro.

    2. Revert back to previous version of Premiere Pro.

         Steps: Install previous version of your Creative Cloud app

    Thanks,

    Vidya

    52 replies

    Show previous replies
    N
    neumannfx
    Participating Frequently
    May 3, 2018

    Not really an answer. This is a work around. At this point I am unable to share projects from our macs/windows 10 boxes with our windows 7 laptops unless I downgrade all the software on the macs/windows 10 boxes. Seriously.

      garethd85468754
      garethd85468754
      Participating Frequently
      April 26, 2018

      In this topic Adobe suggested using an older version of Premiere Pro for some reason they neglected to mention that they have removed older versions from the portal due to Dolby encoding issues.

      https://helpx.adobe.com/x-productkb/multi/dolby-end-of-support.html

      Dmitri Graf
      Adobe Employee
      Dmitri Graf
      Adobe Employee
      April 24, 2018

      Thank you. We are looking into the issue.

      Int the meantime, I recommend you disable NVIDIA GPU or revert back to previous version.

      C
      ck_pixels
      Known Participant
      April 25, 2018

      https://forums.adobe.com/people/Dima+Tikhonov  wrote

      Thank you. We are looking into the issue.

      Int the meantime, I recommend you disable NVIDIA GPU or revert back to previous version.

      Really? Really?

      If you were reading this thread with any attention to detail you'd see I'm the guy who posted the working rollback solution all of two posts higher.

      And, even better, suggesting disabling of the GPU to professional users paying $600/yr for allegedly professional-grade creative software is beyond infuriating and no solution whatsoever. The products are professionally unusable without GPU acceleration. You know it. Adobe knows it.

      Let me point out again: The version specific rollback solution was found on Twitter. It took me, a paying customer, to pass it along here. Nobody cashing Adobe paychecks said to themselves, "Hey, this may help out the folks in the forum... I'll take the initiative and spread the word." Grrrrrrrr.

        C
        ck_pixels
        Known Participant
        April 24, 2018

        This is perhaps a more specific fix (work around really) than the one marked as correct... it provides actual version numbers!

        While they have failed to respond in the forums with concrete solutions, there was a resolution posted to Twitter by Adobe support that worked for me and I will leave here to help others:

        "...the bug is filed for Premiere Pro 12.1 & After Effects 15.1 versions. You can install Premiere Pro 12.0.1 and After Effects 15.0.1. Also, install the same version of Media Encoder for compatibility."

        So fellow sufferers, give that a try! You would have thought they'd have sent someone in here to spread the word but of course they didn't.

        Dmitri Graf
        Adobe Employee
        Dmitri Graf
        Adobe Employee
        April 24, 2018

        Thanks for reporting this here.

        Can somebody help troubleshoot this issue before they apply solution from NVIDIA Control Panel which removes CUDA renderer?

        Please open Command Prompt and type:

          "C:\Program Files\Adobe\Adobe Media Encoder CC 2018\GPUSniffer.exe"

           Press Enter

        Please paste the output as a reply here and let me know if you got a crash dialog. Thanks.

        D
        dandill
        Inspiring
        April 24, 2018

        PS C:\Program Files\Adobe\Adobe Media Encoder CC 2018> .

        GPUSniffer testing 254

        --- OpenGL Info ---

        Vendor: NVIDIA Corporation

        Renderer: Quadro 2000M/PCIe/SSE2

        OpenGL Version: 2.1.2 1005.2.622.2011

        GLSL Version: 1.20 NVIDIA via Cg compiler

        Monitors: 2

        Monitor 0 properties -

           Size: (0, 0, 1920, 1080)

           Max texture size: 16384

           Supports non-power of two: 1

           Shaders 444: 1

           Shaders 422: 1

           Shaders 420: 1

        Monitor 1 properties -

           Size: (1920, 0, 1680, 1050)

           Max texture size: 16384

           Supports non-power of two: 1

           Shaders 444: 1

           Shaders 422: 1

           Shaders 420: 1

        --- GPU Computation Info ---

        Found 1 devices supporting GPU computation.

        CUDA Device 0 -

           Name: Quadro 2000M

           Vendor: NVIDIA

           Capability: 2.1

           Driver: 5

           Total Video Memory: 2048MB

           * Not chosen because of old driver.

        PS C:\Program Files\Adobe\Adobe Media Encoder CC 2018>

        D
        dandill
        Inspiring
        April 21, 2018

        Same problem here. Failure to start Premier Pro means I cannot get INFO from it. However, here is a snip from the INFO reported by Lightroom:

        Check OpenGL support: Passed

        Vendor: NVIDIA Corporation

        Version: 3.3.0 NVIDIA 388.75

        Renderer: Quadro M2000M/PCIe/SSE2

        LanguageVersion: 3.30 NVIDIA via Cg compiler

        Total Video Memory: 4096 MB

        C
        ck_pixels
        Known Participant
        April 21, 2018

        ReeFiz posted instructions on how to get all the system info Adobe needs:

        To do this, search "System Information" from your Start Menu. Select System Information. This will bring up a System Information window. Select FILE, SAVE and save the NFO file. Because you cannot attach a file to these replies you need to upload it to Dropbox or similar and provide the link to Vinay. Ensure you ZIP the NFO file first.

        C
        ck_pixels
        Known Participant
        April 21, 2018

        This thread has no replies from an Adobe staffer the entire business day? Shameful.

        RogerDD
        RogerDD
        Participant
        April 17, 2018

        Same issues with Premiere Pro and Encoder so I went back to the previous versions for both

        I have:

        Dell Laptop, Precision m3800

        Windows 7, 64 Bit

        Processor Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz, 2301 Mhz, 4 Core(s), 8 Logical Processor(s)

        Installed Physical Memory: 16 GB

        Two graphics systems: I use the NVIDIA Quadro K1100M because it has the GPU acceleration for the Mercury playback engine, makes editing workable compared to the onboard Intel HD Graphics 4600! Disabling the Nvidia card for PP and encoder is not an option.

        Thanks

        M
        Motoed-Hidden
        Known Participant
        April 16, 2018

        This is not helpful if you already had to upgrade your project to work in 12.0.1 and it is not "backwards compatible" with 12.0.0.  I have a video I'm trying to complete for Tuesday and was going to work on over the weekend and unable to open what I've done previously. Now I'm in panic mode!

          M
          Motoed-Hidden
          Known Participant
          April 16, 2018

          I'm going to make this even stranger. When I was in the office today, I was able to open and use Adobe Premiere Pro 12.0.1. Now that I'm working remotely at home, I get this error. What would be causing this?  Is there something maybe with the corporate privileges for our office?  That seems strange to me!

          S
          Silicasea
          Participating Frequently
          April 15, 2018

          The question has been marked as answered, but its only a work around solution and has not solved the issue. Does this mean Adobe Staff will ignore this thread?

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