Participant

Answered

Premiere Pro CC 2019 crashes on startup

Forum|Forum|7 years ago
November 15, 2018
10 replies
49427 views

Hi Everyone

I had an BSOD - "Bad_Pool_Caller", and after the restart, premiere pro CC 2019 just wont start.

It gets stuck during initialization on the "Importerquicktime.prm" plugin.

I have tried reinstalling all video related CC apps, renaming the plugins folder, running the app as admin and clearing out the Temp folder in app_Data.

The only thing that worked was to create a new windows account and open premiere there.

However I would really not want to do all the windows user setup just because I got an BSOD.

Does anyone know which user settings have this effect on premiere? any ideas on how I can avoid having to setup a complete new user?

crash crashing

This topic has been closed for replies.

Correct answer Kevin-Monahan

Hi KimDT,

Can you find the file here? %APPDATA%\Adobe\Common\Essential Sound\SharedTags.json

If so, please remove it and see if the situation returns to normal after restarting Premiere Pro.

Thanks,

Kevin

I

IanPaulsaligumba

Participant

That's also my problem. And if i will open mh Premier Pro it will close automatically

G

govind3080

Participant

Adobe Premiere Pro CC 2019 not opnig

RinTinTinny

Participant

In case anyone is having this problem with 13.1.5, I finally was able to get through to someone at Adobe, and this worked for me.
1. Go to Documents.
2. Go to Adobe folder.
3. Rename the folder "Premiere Pro" to "Old Premiere Pro."
You can imagine my frustration after having tried all of the "reset your preferences" and "uninstall and reinstall" and "delete your plugins" tips were attempted over the course of an entire lost day of work.

brianm85557099

Participant

Thank you so much—this is the only solution I've come across that has actually worked for me. You saved the day—thanks!

R

rhune_raymaekers

Participant

hi can anybody help me my premiere pro ceeps crashing after it shows this screen

Kevin-Monahan

Community Manager

Rhune,

Can you try removing audio plug-ins?

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

RIOT Media

Inspiring

I foundanother problem and solution that can make problems with any recent Adobe cc19 App.
Killing the %APPDATA%\Adobe\Common\Essential Sound\SharedTags.json file solved part of it. And I though it did the trick.
I got further but it still crashed on startup.
It seems the final solution is to remove any cpu and gpu overclocking. As soon as I disable my overclocking settings in the Bios the problems seem to have gone away.
A problem that I did not have with previous versions. Also other applications like Resolve, Gimp, transcoding and rendering tools run fine with overclocking under heavy load as long as the system it self stays stable. This is why it took me a while and 2 system restores to find a solution for the current problems...

I read a note from someone who solved it by disabling gpu tuning. But it seems Adobe apps also don't like cpu overclocking as well.

Please Adobe, fix this. We selected and bought our hardware to get maximum performance. Working with a pulled handbrake is not efficient. It can be done as other applications proof.

RIOT Media

Inspiring

Just after the Premiere 13.1.0 Update windows crashed as soon as I tried to open any project.
It crashed so badly that I needed to do 2 system restores to get windows running again, while trying to fix this problem.
Also other programs like AfterEffect or Photoshop produced those complete win10 crashes.

Removing the mentioned Jason file seems to do the trick for me.
Updating all drivers to latest versions did not do anything to solve my problem.

RIOT Media

Inspiring

Quick correction I'm using 13.1.2 the latest version not 13.1.0 as mentioned above.
Why can't we edit posts our self in the forum..

A

Anonymous

There is No "sharedtags" file. Premiere pro automatically closes after a few seconds of program launch.

Wes Howell

Adobe Employee

Hello,

Sorry to hear that you’re experiencing issues. Did you recently upgrade to the latest release?

Are you working on Mac OS? Recently updated by chance?

Happy to help.

Wes

A

Anonymous

Upgraded to the latest release, working on Windows 10.

Y

yus60106768

Participant

Can't find SharedTag as well... I can't open Premier Pro 2019 after updates....

Kevin-Monahan

Correct answer

Community Manager

Hi KimDT,

Can you find the file here? %APPDATA%\Adobe\Common\Essential Sound\SharedTags.json

If so, please remove it and see if the situation returns to normal after restarting Premiere Pro.

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

W

Will..

Inspiring

I can confirm that deleting this file on the user account that's preventing Adobe Premiere Pro will work to fix the problem:

C:\Users\YOUR USER FOLDER\AppData\Roaming\Adobe\Common\Essential Sound/SharedTags

If you can't get there, go to any open folder and at the top under View;check show hidden files.

This file will NOT delete just by right clicking and deleting it. It will say it cannot be deleted because it's in use. Even with closing all Adobe related files in task manager, it still was unable to be deleted because 'System' is using it.

You have to force delete it either through your command prompt, or by installing a program that does it for you.
I used a free program called lock hunter: https://lockhunter.com/download.htm
https://lockhunter.com/download.htmAfter you install lockhunter, you can right click the SharedTags file and go to 'What is locking this file?'.
Then lock hunter will open and if you open the 'system' dropdown, it will reveal the SharedTags file.
Select the SharedTags file (Not system)
Hit the delete button below.
It will tell you that you STILL can't delete it because it's in use, so it will ask if you want to delete it when you restart the computer, say yes.
After the restart, it will say successfully deleted.
You'll now be able to start Premiere pro.
Premiere Pro CC will automatically put back in a new SharedTags file into the Essential Sound folder, but this time since the computer didn't crash while in Premiere (yet), that file didn't get corrupted, meaning all is good, until the next crash, which you'll then need to redo this process.