What solved it was to disconnect all USB devices from the computer: external hard drives, USB drives, external DVD burner, and external floppy drive reader. They have all been connected from a few days to a few months. disconnect and reboot and everything worked. What gave it away was that attempting to unstall all of Adobe products locked up halfway through indicating that Adobe was in a fight with the computer. (plugged everything back in after reboot and all was OK)

peterw49300033Correct answer

Participant

DON`T CLICK ON THE LINK - IT`S SPAM...

K

K6DR

Participant

Go to %APPDATA%\Adobe\Common\Essential Sound in windows explorer. Rename the file "SharedTags.json" to something like SharedTags.json-xx

Restart Premier Pro

Worked for me 🙂

firstlightm20140249

Participant

I've spent so much time trying to fix this, several days now. Followed the many suggestions above. Nothing is working. Was in chat with Adobe customer service and even allowed tech to take control of my computer. Still will not launch and the tech crash my computer. I am so over the top frustrated!!!!!!!!!! How can there be this many threads for something and no fix from adobe???

SonicPau

Participating Frequently

Just a follow up: do you guys can export now? I mean, if I ctrl + m (or command + m) from the timeline, or same thing but from the menu, instead opening AME it stays in PP doing nothing. If I try to click anywhere I can't do anything. Have to force close PP. The only way to render something is to open AME and import PP project and timeline.

That's also very bothering.

J

Jonzy

Known Participant

Beside of the obvious free advertisement, I did not used the Lock Hunter's software. I just deleted the frickin file and my Premiere Pro work again.

In my case, Premiere Pro was working fine for many days, until my computer crashed. When I rebooted I experienced the issue like everyone else here.

I deleted many personal preferences folders in my machine by thinking a file was corrupt for absolutely nothing and perhaps valuable pieces has been lost in the attempt of recovery.

Deleting the SharedTags file did the trick (and nothing to do with the software btw). Please acknowledge this.

A

Anonymous

This is absolutely ridiculous and infuriating. Happens only with Premiere (not AFX) as of this AM (5 hours lost and counting...). My specs are well beyond what's needed:

Windows 10

Dual Xeon 2.40 GHz

64 GB RAM

Nvidia Quadro K5200 (driver version 411.95) 8 GB DDR5 RAM

I have tried, in no particular order:

1) Running as administrator

2) Temporarily moving the "WebM.prm" file (which is the last Loading element I see before it crashes)

3) Moving plugins one by one and wholesale from the MediaCore folder

4) Uninstalling/re-installing Premiere Pro

5) Clearing my Temp folder (except for the ones I cannot delete, even if I cancel or temporarily rename running Adobe processes)

No luck. I don't have admin rights to this machine. So setting up a new account is a non-starter. PLEASE fix this, Adobe.

CityWyde

Participant

If anyone is still having this issue

I learned to let my computer do it's thing for about 15mins after logging in. I just cut the computer on, log in, and let it sit on the desktop while I go do something. when I get back to the computer, Adobe fires right up with no problems. It hasn't failed once ever since.

I've never tried any of the other ways on this thread, so give this a try if those didn't work for you

ram.86.filmmaking

Participant

Start the program as Administrator. DONE. (no need of restart)

T

therealpj

Participating Frequently

That worked for me! Thanks!

Jeff Bellune

Legend

Create a new user account and try starting Pr again from the new account. If it launches successfully, then go back to your original account and launch Pr while holding down the Shift+Alt keys. That should reset your plug-in cache and preferences. Doing that will often fix startup and other crashes in Pr.

Cheers,

Jeff

joaocverde

Participant

Thanks Jeff.

In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.

yevgeniyp76506545

Participant

joaocverde wrote
Thanks Jeff.
In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.

This did NOT work for me, but after a very long and annoying back and forth in another thread, the problem was isolated to a file in User App Data that needed to be force deleted. Here's what I did to fix it for me:

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.

This is a perfect example of how Adobe loves to introduce new features (Essential Sound) that causes conflicts with other parts of Premiere that used to work perfect. In this case, the new feature wouldn't even let Premiere start up.

Adobe, can we please all agree that you seriously need to do FULL testing before new features are introduced?

It doesn't contain such folder as Essential Sounds even when I see hidden folders and files (

joaocverde

Participant

Same thing here.

Given that I'm actually paying for Premiere and I need it, it bugs me quite a lot...

NVIDIA drivers up to date (355.82) GeForce GTX750

Windows 10 Pro, DirectX 12, 16GB RAM

Quicktime 7.7.6 installed (but it crashed before also)

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded