Skip to main content
Inspiring
October 19, 2018
Answered

crash while loading importerquicktime.prm (WIN 10)

  • October 19, 2018
  • 14 replies
  • 45338 views

Brand new OS Win 10 Pro - specially for CC 2019. During the work on one project I get BSOD BAD_POOL_CALLER. - after restart  I can't run Pr. They crushing at loading importerquicktime.prm.

Tried:

-reinstal Pr

-Adobe CC cleaner

-restore system

WORKAROUND: I read some tips:

  1. create new OS user
  2. log in on new OS account
  3. works!

But how do I repair that bug?

Correct answer Le Ill Kid

This Youtube video helped me!!!

Premiere CC 2019 Quicktime Crash Fix - YouTube

14 replies

Participant
July 8, 2022

I ran Adobe Premiere as Adminstrator account and it's now opening fine.

Participant
January 19, 2022
For me works this:
Open this file (in Notepad): C:\Users\"YOUR USER"\AppData\Roaming\Adobe\Premiere Pro\"YOUR AP VERSION"\Debug Database.txt
Locate the following flag entry:
 
DS.ForceCPUOnly false false
 
Modify the flag entry to true as shown below:
 
DS.ForceCPUOnly true false
Save the file.
Participant
September 28, 2020

I'm having this issue and have found ZERO soluations. Any help please? I'm running the latest version 14.4

Participating Frequently
March 13, 2021

You can start Premiere with admin rights. this solved the problem for me.

Filipe Cunha
Participant
November 16, 2019

Yesterday I have the same problem, but in the MAC OS. And The folder MediaCore is empty.

Participant
November 30, 2019

I've struggled with this issue as well, with Premiere Elements 2020 on Win 10, and was not helped by the "%APPDATA%\Adobe\Common\Essential Sound\SharedTags.json" solution (no "Essential Sound" folder). I removed all things Adobe and reinstalled several times, all in vain.

But, creating a new user worked, so it seemed to be a permissions problem. Finally I found a solution that worked for me, see #2 in https://thegeekpage.com/solved-fix-adobe-error-16-in-windows-10/ ! I only had to fix the permissions for the SLStore folder, exactly as described, and it works!

This was a really infurating problem, so I hope this will help someone else as well.

turment
Participant
January 20, 2020

Tried same passages but I have a AzureAD account to log in in Windows 10 and so it's not possible to give ownership to it.

 

Creating a local account or running as Administrator solves but it really sucks as a solution.

Participant
January 5, 2019

Me and other users do not seem to have this Essential Sounds folder

It worked a few hours ago and now nothing...

Le Ill Kid
Le Ill KidCorrect answer
Inspiring
December 8, 2018

This Youtube video helped me!!!

Premiere CC 2019 Quicktime Crash Fix - YouTube

virus191Author
Inspiring
December 8, 2018

I get this crush second time - this solution works for me!

comment_afpzDqUi431QA0WCniYMM0cwgIbRLWfd.jpg

Kevin-Monahan
Community Manager
Community Manager
November 19, 2018

virus,

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
Inspiring
November 19, 2018

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, 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?

We should not be the ones having to go through this, Adobe should be finding these bugs out, fixing it and then releasing the NEW and IMPROVED version. Or at least name your new releases 'BETA' for 6 months, until they have been fully tested by Editors who are willing and fixed by your engineers. Maybe you could hire a beta testing team for each new release specifically for testing. I can guarantee Adobe would easily make far more money by spending a bit more up front because the customers would be HAPPY using your software. Right now it's a giant pain and it seems more and more everyday we're searching for alternatives. Premiere is AWESOME when it works. Unfortunately, it doesn't work awesome all the time.

Kevin-Monahan
Community Manager
Community Manager
November 20, 2018

Hello Will,

Very sorry for these issues. I'm glad we were able to help you get to the heart of the issue and that your steps will definitely help others too. Sorry for the frustration around this nasty bug. I will make sure that we get a bug filed and provide a knowledge base doc so that others can be helped.

  • This is a perfect example of how Adobe loves to introduce new features...
  • Adobe, can we please all agree that you seriously need to do FULL testing...
  • We should not be the ones having to go through this....
  • Adobe should be finding these bugs out
  • until they have been fully tested by Editors who are willing and fixed by your engineers...
  • Maybe you could hire a beta testing team
  • Right now it's a giant pain
  • Unfortunately, it doesn't work awesome all the time.

We are in support. I'm afraid that we can't do much to address your complaints about the dev process or quality control around Premiere Pro, though I do understand your frustration and need to vent that out.

Suggestions to developers are better made here: Premiere Pro: Hot (3271 ideas) – Adobe video & audio apps Please direct your efforts for feedback to the devs there.

Very sorry for the frustration around this issue. I hope we can provide a full fix in an upcoming update of Premiere Pro.

Thanks for understanding,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Known Participant
November 19, 2018

Any update on this issue?

sosborniv
Participant
November 16, 2018

I'm having the same issue.

Nothing seems to be working to fix the issue.

Absolutely terrible.

virus191Author
Inspiring
November 16, 2018

For me, an Adobe consultant on a remote desktop session said it was a problem with file rights and recommended reinstalling the system.

Thank you so much for such helpful advice ...