Inspiring

Answered

Premiere Pro could not find any capable video play modules. Please update your video display drivers

Forum|Forum|6 years ago
January 15, 2020
21 replies
14106 views

Yesterday, I was editing fine in Adobe 2020 without any issues. Now, when I try to launch the program, it says, "Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again." If I restart my computer, sometimes, the program will launch fine and I can edit. But most of the time, I get this error. And, it all started this morning without any recent updates that I'm aware of. And, when it closes out, my Mac OS says, "Adobe Premiere Pro" has crashed. Not sure what's happening. There was no change to my hardware.

Error or problem

This topic has been closed for replies.

Correct answer Mitch W

Hi Mitch, Can you please describe what the "winner" is? I have been having the issue of Premier, Encoder, and Audition 2020 not running on my new Mac Pro (I can run Premier 2019). I am running OS 10.15.2 and am using a Pegasus2 R6 and version 4.04.0000.37 of the Promise Utilty app. Based on this thread it is unclear whether the "winner " is to update the Utility to 39 or downgrade it to a lower version. What exactly should I do to implement the "winner" and address the issue? Thanks!

Hi Larry,

Yeah, I understand the confusion. The posts here are a bit out of order. Short answer is to uninstall the Pegasus Utility. If you can locate a copy of the Pegasus Utility version 4.04.0000.30 or earlier, you should be able to install and use it without hitting the problem. Otherwise, just leave the utility uninstalled. The Promise developers and the Adobe developers are both looking at the problem to try to understand what's occurring when the Pegasus Utility is installed that is thwarting our ability to check the GPU status. It'll take a little time to sort out but I expect that both companies will take steps to avoid something like this from happening again.

Show previous replies

Light_Slicer

Participant

Thank you for this! If been slogging through possible causes of the very same issue which seemingly arose out of nowhere. Hours on the phone with an Adobe rep, some time with Apple support and now finally someone has nailed it!

bigfatgraphics

Participating Frequently

Hi - Just to add that I am having the same issues, and I too have the 2012 trash can MacPro with a Promise Pegasus running version 4.04

johnpooley3

Inspiring

An Adobe staff member in the facebook group "Adobe Premiere Pro Editors on Facebook" has a workaround for this and will apply it if you post in that group.

A

arkalmed

Inspiring

Thanks for the heads-up!!

But I'm not on facebook. Don't intend to join either... now what?

johnpooley3

Inspiring

I have already raised this concern with the Adobe staff member in question and I did not receive a response.

R

Russell PondAuthor

Inspiring

Good news, and bad news. Good news is that I can back up one small version to 14.0, and the problem goes away. So, something in 14.0.1 is broken regarding this issue.

Bad news is that all of the projects I created in 14.0.1 (latest version) will not open in 14.0. I get the error saying, "Project was created in a newer version of Premiere.) It was 0.1! That's not a new version.

Anyways, something is seriously broken in 14.0.1. I'll try to stick with 14.0 for now. Hopefully, they'll figure it out soon.

M

mmoollllee

Participant

For me installing 14.0.0 again didn't make a change.

Macbook Pro 2019 16" with AMD Radeon Pro 5500M 8 GB
macOS Catalina 10.15.2

Mitch W

Participating Frequently

Try creating a Root User account and then logging into your system as Root - https://support.apple.com/en-us/HT204012
If you're able to work without errors in Root User mode, then the problem has something to do with user permissions. If you're getting the same error when logged in as Root, then it's not a permissions issue. Don't forget to disable Root User account after trying this test.

R

Russell PondAuthor

Inspiring

I enabled Root User and tried to launch the program, and it still gives me the display error. So, it's not a permissions issue.

djepsilon5

Participant

I've been having this same issue on my brand new 2019 Mac Pro as well. Super frustrating. I have found that if I reboot my machine and then open Premiere right away, it'll work. If I close up Premiere though and try to open, she'll stop working. Basically I have to reboot like 3 times a day. Another issue I've noticed is that occasionally Encoder will stop using the GPU to render (it greys out) and will use Software encoding instead...again, until you reboot. %^#$^!

Really hoping Adobe gets this sorted out for all of us.

R

Russell PondAuthor

Inspiring

Yes, that was also happening to me. I could reboot and immediatley launch Premiere. Then, when I would forget and quit, it wouldn't launch any more. Today, however, it will not start up at all any more. Just crashes on launch.

S

Stevie L

Inspiring

No problem. Just to add: on restart after PU removed completely (unsurprisingly) I can confirm that PP2020 and AE2020 and Prelude 2020 all launch fine (and very quickly too, I might add).

So to my mind, it's definitely the Promise Utility that is the issue.

R

Russell PondAuthor

Inspiring

Adobe support got it working for me. It was pretty exhaustive, though.

First, they ran this program to clean all the creative cloud programs: https://helpx.adobe.com/in/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

Then, they went through and literally deleted everything setting, preference, cache, file -- anytihng with the word "adobe". Then, reinstalled Creative Cloud and then Premire, and then it worked. I'd be curiosu if this solution works for everyone else.

Now, back to reinstalling all my CC apps and plug ins.

R

Russell PondAuthor

Inspiring

Well, forget that -- the problem is back. As of this morning, the same crash is happening again. Crap! I need this software to be working, and it's not.

A

arkalmed

Inspiring

Sorry to hear that Russel. I was holding back on all the steps you mentioned because I simply couldn't afford to jump through all these loops. This needs a fix ASAP.
Have you noticed the missing Metal GPU acceleration in AE too? See here: No Metal GPU acceleration available

R

Russell PondAuthor

Inspiring

Yesterday, I spent about 20 minute on a call with Adobe support. They took control of my computer, adjusted some permissions and user stuff, but it didn't fix the issue. Then, we tried plugging in a different monitor (from DP to HDMI), and still no luck. The guy then said he'll get back to me because they've had a few calls regarding this. So, at least they're looking into. He said he would call me back once they have a solution.

A

arkalmed

Inspiring

Thanks Russel for letting me know! I still haven't heard back after sending several crash reports.

R

Russell PondAuthor

Inspiring

Shoot! It's gone from bad to worse now. I just uninstalled Premiere, After Effects and Media Encoder, and then re-isntalled them. Before, when I got the error, I could restart my computer and at least get Premiere to launch once (to get my editing work done). But now, it crashes all the time. I can't get Premiere to launch at all. Frustrating!

A

arkalmed

Inspiring

I created a bug report here (please vote):
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/39465136-bug-report-crash-pr2020-14-0-and-14-0-1-pre