Skip to main content
V
virus191
Inspiring
October 19, 2018
Answered

crash while loading importerquicktime.prm (WIN 10)

  • October 19, 2018
  • 14 replies
  • 45320 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

    B
    beng16140477
    Participant
    July 8, 2022

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

    R
    Radek5C72
    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.
    B
    Bradley5F93
    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

    L
    Live2Line
    Participating Frequently
    March 13, 2021

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

    Filipe Cunha
    Filipe Cunha
    Participant
    November 16, 2019

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

    A
    Andreas_Bk
    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
      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.

      L
      lavg95225162
      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

      V
      virus191Author
      Inspiring
      December 8, 2018

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

      comment_afpzDqUi431QA0WCniYMM0cwgIbRLWfd.jpg

      Kevin-Monahan
      Community Manager
      Kevin-MonahanCommunity 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
        V
        virus191Author
        Inspiring
        November 19, 2018

        Sorry, but I dont have time to wait. I reinstalled OS on the same day.

        C
        cooldude45545
        Known Participant
        November 19, 2018

        Any update on this issue?

        sosborniv
        sosborniv
        Participant
        November 16, 2018

        I'm having the same issue.

        Nothing seems to be working to fix the issue.

        Absolutely terrible.

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

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices