Skip to main content
E
EdCali1960
Participant
February 28, 2022
Question

premiere Pro will not load. stuck at importerQuickTime.prm

  • February 28, 2022
  • 2 replies
  • 8844 views

the splash screen indicates the Premiere Pro is loading ImporterQuickTime.prm plugin. Never advances from this point. 
The Plugin loading.log files shows that the ImporterQuickTime.prm was loaded from the JSON file. 

 

 It appears that files are missing from the C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore

PR Pro is looking for the folloing extension in this directory. Scanning for the following file types: *.prmp, *.prm, *.dll, *.aex, *.8bf.  They do not exist. There is only one file and it's a dummy.txt file. 

What App should I install to the required drivers in this directory. ???

 

 

The issue also exist with After effect, Rush and media encoder. All of them will NOT LOAD!

All the apps mentioned have been updated to the latest version. 

I have made sure they are running as administrator 

I disconnect all devices from the laptop 

PR Pro was working and has stopped. 

 

This is a major issue and needs to be addressed!!! costing me $$$$

 

 

    This topic has been closed for replies.

    2 replies

    D
    douwe27615045myie
    Participating Frequently
    December 17, 2022

    See if you have mapped network drives, especially ones that are not (or no longer) reachable

    Remove them. (terminal --> net use X: /delete (X: is the drive letter of the mapped network drive)

     

    Vishu_Aggarwal
    Vishu_Aggarwal
    Participating Frequently
    February 28, 2022

    Please check the following post - 

     

    https://community.adobe.com/t5/premiere-pro-discussions/importerquicktime-prm/td-p/7498065

     

    Vishu AggarwalAdobe Certified Instructor, Professional and Expert
    D
    default7qju7j9ui8dv
    Participant
    November 5, 2024

    Hi, this is not a solution and this is not closed.  The link you sent is from a 2015 thread.  The fact that this problem continues today, means the issues is not solved or closed.

     

    Creating a separte user acount, etc. is not a solution it is a work-around.  I would expect Adobe to set the correct permission during the installation such that the work around isn't necessary.

    Please ask the Adobe developers to investigate this bug.

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