Participating Frequently

Answered

Premiere Pro crashing at start-up screen

22 replies
6148 views
Translate

Has there been a fix for this yet:

The 80 crash reports I sent the last few days hasn't led to a resolve yet.

Thank you,

tony

This topic is closed to new replies. Start a new post to keep the conversation going.

W

Will..Correct answer

Inspiring

After a long back and forth in another Adobe thread, I can confirm that deleting this file on the user account that's preventing Adobe Premiere Pro will work to fix the problem (For me it did at least after trying 25 other things that didn't work):

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.

So this was NOT an issue with Microsoft. It was an issue with Premiere Pro, and its latest sound "feature", specifically.

Foxtrot25Author

Participating Frequently

I went through about 2 hrs of a tech support controlling my system. He couldn't get it fixed.

It went up the line to a sr tech support who controlled the system for 3 hrs. Same result.

Making another windows user account will allow the premiere to work. He deemed that there is something corrupted with my Microsoft (original user profile) that he could not identify.

Adobe thinks it's on Microsoft's end. He recommended contacting them for a repair. I did not do this as I can use another user sccount when I use Premiere.

Not what anyone wants to hear.

I hope another user account will work for anyone else with this problem.

Translate

W

Will..Correct answer

Inspiring

After a long back and forth in another Adobe thread, I can confirm that deleting this file on the user account that's preventing Adobe Premiere Pro will work to fix the problem (For me it did at least after trying 25 other things that didn't work):

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.

So this was NOT an issue with Microsoft. It was an issue with Premiere Pro, and its latest sound "feature", specifically.

Translate

N

nfsv

Participating Frequently

Exactly.

in my case I looked for the file that is "invisible" and basically, I changed its name. - SharedTags to SharedTags1

Started working again.

NV

Translate

Foxtrot25Author

Participating Frequently

Almost 24hrs since first contact with tech support. Haven't heard back yet.

I deleted most everything to do with premiere and re-installed multiple times.

I just don't get it.

Was editing along, crash and then it won't start. I've gotten hangups when changing filenames during exporting before but nothing like this. Been at least a week or 2 since the new updates. I didn't update anything else on my computer, so what is causing this all of a sudden?

Frustrated.

Translate

Foxtrot25Author

Participating Frequently

It hangs on ImporterQuicktime.prm

As far as I know, all plugins have been removed and I re-installed the whole cloud out of the box new.

The only plugin I use is RedGiant and I took that out of the Common folder.

The previous versions of premiere work but my current projects are not backwards compatible so i can't use them.

I did notice support trying to start premiere without the graphics card usage and even in safe mode. It still hangs at that very same point. Tech didn't communicate all that much with me but seemed to begin his troubleshooting as a graphic card issue.

The only crash report I get is the Adobe screen that I posted above.

Since the crash (Wednesday) I tried rolling back nvidia drivers. Everything else system-wise seems to operating fine.

Translate