Inspiring

Answered

crash while loading importerquicktime.prm (WIN 10)

Forum|Forum|7 years ago
October 19, 2018
14 replies
45342 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:

create new OS user
log in on new OS account
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

B

beng16140477

Participant

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

R

Radek5C72

Participant

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.

B

Bradley5F93

Participant

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

L

Live2Line

Participating Frequently

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

Filipe Cunha

Participant

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

A

Andreas_Bk

Participant

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

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.

L

lavg95225162

Participant

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

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

Le Ill KidCorrect answer

Inspiring

This Youtube video helped me!!!

Premiere CC 2019 Quicktime Crash Fix - YouTube

V

virus191Author

Inspiring

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

Kevin-Monahan

Community Manager

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

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

P

phydeaux98038

Participant

Hi Will,

There's actually a lot Adobe can do. It's a choice that customers are left testing and reporting for you, instead of spending money on producing quality products, and getting it right on the first release.

The developers are in charge of quality control, fixing bugs, and handling feature request. It's best to leave them feedback on user voice.
- User voice is not a great place to get quick advice or "how tos."
- User voice is not a great place for 1-1 support.
These forums are better suited to solving quick "how to" problems.
- The forums are not a great place to complain about the quality of the software.
- The forums are not a great place for leaving bug reports.
- The forums are not a great place for leaving feature requests.
The call and chat queue are best for solving issues you need 1-1 support with.
- The call and chat queue is not a great place for "how to" issues.
- The call and chat queue is not a great place for bug reports.
- The call and chat queue is not a great place for feature requests.

As you deal with all the time in these forums it seems, you are VERY aware of how unstable it is and how many complaints there are.

Yes, I do report back to the team about certain trends and issues, as does call and chat, however, the forums are not well suited to giving the team feedback. That's what user voice is best suited for. Sure, you can complain in forums and to our call center about quality issues, but it's not as effective as engaging them directly.

I hope that makes sense.

Thanks,
Kevin

Hello all,

I, too, am running into the same issue here, with the error loading the importerQuickTime.prm in WIN10. This is a new computer, given to my son just two days ago. Adobe CC was installed the same day, and was working last night. Today, with no crash noted, he runs into the error. Running as Administrator, or as a second user, have all produced the same result. Additionally, the Essential Sound directory is not found in %APPDATA%\Adobe\Common\ for any of the users I have been trying with.

I would prefer to not go the route of reinstalling Windows, but since this system is only 2 days old, it can be done without much fear of losing data.

-Eric