Skip to main content
saintsjake
Participant
March 18, 2018
Question

Adobe Premiere Won't Open (No Loading Screen)

  • March 18, 2018
  • 2 replies
  • 308 views

Hi all,

Upgraded to CC2018 and now I cannot even load Premiere. Premiere is running in task manager Processes tab but not Applications.

Have re-installed app both versions and checked for hardware updates and drivers.

Intel Core i7-8700 CPU      16GB RAM        AMD RADEON R7-370           Windows 7 (64bit SP1)

Have tried troubleshooting from a couple of forum posts and nothing yet.

Any more details needed or any suggestions on the problem?

Many thanks for all suggestions.

This topic has been closed for replies.

2 replies

Legend
March 18, 2018

Sometimes PP gets stuck when closing.  It won't restart until you kill that process with a right click.

saintsjake
Participant
March 19, 2018

I can't even get it to start let alone close xD

I have to kill the process with the right click after I try to launch and it fails.

Legend
March 20, 2018

OK.

Check Windows Event Viewer.  What does it say about the crashes?

John T Smith
Community Expert
Community Expert
March 18, 2018

Do not count on Windows to be fully up to date when it comes to device drivers

Go to the vendor site to be sure you have an updated driver for your graphic adapter

•ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool

There are also intermittent reports that the newest driver is not always the best driver due to driver bugs or compatibility issues, so you MAY need to try an earlier driver version

saintsjake
Participant
March 19, 2018

Hi John thank you fort your response

Downloaded a different set of drivers 3 times and still nothing I don't even get a splash screen. I have Adobe Premiere running in the processes tab but nothing in application manager. Even 2017 wont load from application launcher or launching through a new project :/

I have recently upgraded my computer and added a new motherboard.processor.RAM&Power supply is there anything That might be affecting it in the programme files or something like that possibly?