ImporterQuickTime.prm

[edup87484288]

After I install windows 10 my premiere don't start.

The loading stops in "ImporterQuickTime.prm"

Somebody help me?

[jeanblier]

Same thing here but with media Encoder 2015

[joaocverde]

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)

[Jeff Bellune]

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 · Accepted solution]

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.

[Jeff Bellune]

Good news -- and good troubleshooting!

Cheers,

Jeff

[dpColletto]

Which folders exactly need to be accessed by admin?  Why does starting up premiere as admin not fix this?

[rowanc16797025]

Which folders exactly need to be accessed by admin?  Why does starting up premiere as admin not fix this?

[Will..]

I tried, but it did not help.... I've commented also in this thread about the same issue: loading importerquicktime.prm - crush

[Will..]

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.

1. You have to force delete it either through your command prompt, or by installing a program that does it for you.
2. I used a free program called lock hunter: https://lockhunter.com/download.htm
3. https://lockhunter.com/download.htmAfter you install lockhunter, you can right click the SharedTags file and go to 'What is locking this file?'.
4. Then lock hunter will open and if you open the 'system' dropdown, it will reveal the SharedTags file.
5. Select the SharedTags file (Not system)
6. Hit the delete button below.
7. 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.
8. After the restart, it will say successfully deleted.
9. You'll now be able to start Premiere pro.
10. 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?

[SonicPau]

That's the fix!
Even just renaming the file, like I did, and premiere just started.

Thank you.

[alinaart]

Thank you adobe, project over which I worked 5 days more not is a.

[Guest]

Worked for me. THANK YOU!!!

[victoriafini]

Worked for me!!!!! THANK YOU!!! Hope Adobe gets some help.

[yevgeniyp76506545]

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

[gt450]

Did you end up finding it. I can't either?

[Caleb5CBE]

me too

[Guest]

I have the same problem. Were you able to fix this problem? Help me please!!

[therealpj]

I was able to circumvent this problem by running Premiere Pro as an
administrator.

(Also, since updating my Premiere Pro CC to the 2021 version, this issue
seemed to go away regardless.)

[Joan5C9F]

I don't have the Essential Sound directory there. Still stuck. I've tried many of the other options in this forum. 

[ram.86.filmmaking]

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

[therealpj]

That worked for me!  Thanks!

[Dooby5E27]

Thanks.  This worked and I only had to do it once.

[Guest]

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]

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