
And guess what, it started! So it meant that something in my own user account was broken. Also, I did not find it worked unless I was doing an uninstall back to the base (no cloud desktop) and reinstall from there.įirst, in order to test things, I created a new local administrator user account, signed into it and tried to open Premiere. Be sure when you are doing a PR uninstall that you use the cleaner and that it is the newest version (4.3.0.22 I think 10/22/18). The cleaner tool did not have CC 2019 for a while.

So I am still concluding that voodoo is required. On the main system drive, all is okay with antivirus running. That was on a clone where I was installing only PR and AME 2019. In my case most recent case, disabling antivirus worked most consistently. Then a few weeks down the line, similar but not identical issues. A reinstall did get me back up and running. I had not reinstalled Windows 10 for a long time. If I were still doing this for income, I'd be beside myself. I had no hardware/crash to complicate things. The number of things that seemed to almost work leads to bad conclusions: it runs if you "just hold your mouth right." (Old saying from tennis.) Right now, it is running fine.
#Adobe cc premiere pro install#
Major problems getting 2019 to install and run consistently. You left out signing out and back in to the cloud desktop. So, any help troubleshooting this issue is much appreciated, like where to find relevant log files. All other programs seem to work fine, including After Effects and Media Encoder, which were open during the crash.
#Adobe cc premiere pro driver#
It's possible that the BSOD was a result of an overheating pc and it corrupted some file somewhere that is not replaced by Premiere or graphics driver installation but Premiere needs that file.
#Adobe cc premiere pro drivers#


However, the older version 12.1.2 still works but it won't of course open the projects saved in the new version. I have already spent two days reading forums and trying a lot of things but Premiere just won't launch anymore.

A couple of minutes later the Windows crashed into the blue screen and restared the pc.Īs a result, Premiere died permanentally. After it Media Encoder informed that the rendering had failed and it started rendering the next video in the que. I don't remember the exact course of events anymore, but suddenly there was some glitch in the display/graphics adapter and the screen went black for a few seconds. The problem started after I had been rendering a video in Media Encoder and editing another video in Premiere for a few hours. The last plugin it loads is WebM.prm but if I remove that plugin, then it just crashes after the previous plugin, which implies that plugins are not causing this. It seems to load the plugins and crash in whatever comes after the plugins and pop up the Adobe Crash Report window. Premiere Pro CC (13.0, on Windows 10) used to work perfectly before, but now it crashes while loading up.
