Highlighted

Premiere 2018 freezes while "Loading PlayerMediaCore.prm"

Explorer ,
Jan 05, 2019

Copy link to clipboard

Copied

When I launch PE2018 on my new Lenovo 8185 (Display adapter "Intel HD Graphics"), the loading screen freezes when it gets to the point that it is "Loading PlayerMediaCore.prm".

For the record, I checked the graphics driver and made sure it is the latest one. Initially, I only updated it on the Win OS level, but then I saw a more specific driver update on the Levono site and installed that one.

As a side note, this is "progress" over the first issue I was seeing when loading the application would immediately at the "Initializing application" stage... The good news is that I got past that... but now the startup procedure freezes on this PlayerMediaCore stage.

I did some checking on other similar threads. One was almost identical to mine but it turned out to be specifically about an AMD Graphics card... and was resolved focusing on that card. My adapter is an "Intel HD Graphics", so the solutions found in that thread do not apply to my adapter. For reference, here is a link to that thread:\

https://forums.adobe.com/message/10801402#10801402

I did do some tests and tried some things that were used in that thread (and some ideas of my own), however.

Here are some of them:

1. In the Debug Database.txt file, I went to the DS.ForceCPUOnly entry and set it to "true    true".

I tried opening PE2018 again but saw no change in behavior.

2. I took a look in the file called Plugin Loading.log   ...

The last few lines do indeed show everything stopped as the program was trying to load "PlayerMediaCore" in the Registry and from the disk.

Here are the relevant last few lines:

Loading C:\Program Files\Adobe\Adobe Premiere Elements 2018\Plug-ins\Common\PlayerMediaCore.prm

Invalid registry entry found so the plugin will be loaded from disk.

Loading from disk...

There was an error loading C:\Program Files\Adobe\Adobe Premiere Elements 2018\Plug-ins\Common\PlayerMediaCore.prm from the plugin cache

The registry key will be deleted and the plugin will be loaded from disk.

Loading from disk...

After that, log entries into that text file just stop (which makes sense because startup froze at that time.)

3. OK... Here's when I tried something tricky. It didn't work but it was worth a shot.

Since the path to the PlayerMediaCore.prm file was listed (see previous #2), I thought perhaps the file was corrupted. I have PE2019 up and running. It also has this file, so just for fun, I changed the name of the 2018 version to PlayerMediaCore_old.prm and copied the PE2019 version of the file to this directory.

I wasn't clever enough, however, as when I tried to load the program, it somehow knew I had changed the name, so tried to load that original renamed file (although it had an altered name). Since that didn't work, I revered those file rename/copy commands to get me back to where I was. (Nothing ventured, nothing gained.)

4. Out of curiosity, I went into the registry to see what the entry said there that PE didn't like.

Other than the "default" REG_SZ entry, the only other entry was a "HasPipl" entry with a data value set to "0".

I made no changes there... I just looked.

5. I took a look in this file: BadDrivers.txt

Here is the single entry there: ##FALSE###FALSE#0

So that's it... As the similar referenced thread came to a warm and fuzzy conclusion (but dealing with an AMD video adapter), I'm hoping a similar solution is already know (or will be found) for my own video adapter (assuming that is somehow the culprit).

Any ideas what to try next?

Thanks!

Hey, I struggled with this exact same issue last night and this morning and finally found my issue. For me, I had recently updated all my drivers in order to resolve a Windows 10 100% Disk issue. The culprit for me was my newly updated graphics driver (Intel(R) HD Graphics 620). Once I rolled it back from a 12/10/18 version back to a 2/28/18 version, my PE18 opened and is so far working normal again. Hopefully this helps!

Views

492

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Premiere 2018 freezes while "Loading PlayerMediaCore.prm"

Explorer ,
Jan 05, 2019

Copy link to clipboard

Copied

When I launch PE2018 on my new Lenovo 8185 (Display adapter "Intel HD Graphics"), the loading screen freezes when it gets to the point that it is "Loading PlayerMediaCore.prm".

For the record, I checked the graphics driver and made sure it is the latest one. Initially, I only updated it on the Win OS level, but then I saw a more specific driver update on the Levono site and installed that one.

As a side note, this is "progress" over the first issue I was seeing when loading the application would immediately at the "Initializing application" stage... The good news is that I got past that... but now the startup procedure freezes on this PlayerMediaCore stage.

I did some checking on other similar threads. One was almost identical to mine but it turned out to be specifically about an AMD Graphics card... and was resolved focusing on that card. My adapter is an "Intel HD Graphics", so the solutions found in that thread do not apply to my adapter. For reference, here is a link to that thread:\

https://forums.adobe.com/message/10801402#10801402

I did do some tests and tried some things that were used in that thread (and some ideas of my own), however.

Here are some of them:

1. In the Debug Database.txt file, I went to the DS.ForceCPUOnly entry and set it to "true    true".

I tried opening PE2018 again but saw no change in behavior.

2. I took a look in the file called Plugin Loading.log   ...

The last few lines do indeed show everything stopped as the program was trying to load "PlayerMediaCore" in the Registry and from the disk.

Here are the relevant last few lines:

Loading C:\Program Files\Adobe\Adobe Premiere Elements 2018\Plug-ins\Common\PlayerMediaCore.prm

Invalid registry entry found so the plugin will be loaded from disk.

Loading from disk...

There was an error loading C:\Program Files\Adobe\Adobe Premiere Elements 2018\Plug-ins\Common\PlayerMediaCore.prm from the plugin cache

The registry key will be deleted and the plugin will be loaded from disk.

Loading from disk...

After that, log entries into that text file just stop (which makes sense because startup froze at that time.)

3. OK... Here's when I tried something tricky. It didn't work but it was worth a shot.

Since the path to the PlayerMediaCore.prm file was listed (see previous #2), I thought perhaps the file was corrupted. I have PE2019 up and running. It also has this file, so just for fun, I changed the name of the 2018 version to PlayerMediaCore_old.prm and copied the PE2019 version of the file to this directory.

I wasn't clever enough, however, as when I tried to load the program, it somehow knew I had changed the name, so tried to load that original renamed file (although it had an altered name). Since that didn't work, I revered those file rename/copy commands to get me back to where I was. (Nothing ventured, nothing gained.)

4. Out of curiosity, I went into the registry to see what the entry said there that PE didn't like.

Other than the "default" REG_SZ entry, the only other entry was a "HasPipl" entry with a data value set to "0".

I made no changes there... I just looked.

5. I took a look in this file: BadDrivers.txt

Here is the single entry there: ##FALSE###FALSE#0

So that's it... As the similar referenced thread came to a warm and fuzzy conclusion (but dealing with an AMD video adapter), I'm hoping a similar solution is already know (or will be found) for my own video adapter (assuming that is somehow the culprit).

Any ideas what to try next?

Thanks!

Hey, I struggled with this exact same issue last night and this morning and finally found my issue. For me, I had recently updated all my drivers in order to resolve a Windows 10 100% Disk issue. The culprit for me was my newly updated graphics driver (Intel(R) HD Graphics 620). Once I rolled it back from a 12/10/18 version back to a 2/28/18 version, my PE18 opened and is so far working normal again. Hopefully this helps!

Views

493

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jan 05, 2019 0
Community Beginner ,
Jan 06, 2019

Copy link to clipboard

Copied

Hey, I struggled with this exact same issue last night and this morning and finally found my issue. For me, I had recently updated all my drivers in order to resolve a Windows 10 100% Disk issue. The culprit for me was my newly updated graphics driver (Intel(R) HD Graphics 620). Once I rolled it back from a 12/10/18 version back to a 2/28/18 version, my PE18 opened and is so far working normal again. Hopefully this helps!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 06, 2019 3
Explorer ,
Jan 06, 2019

Copy link to clipboard

Copied

Hey Brent,

Thanks for that great reply. I'm so glad to hear you got PE2018 up and running again.

My Lenovo laptop (containing the "Intel HD Graphics" graphics card is only about 2 weeks old, so I don't have "previous drivers" available. When I view the driver info through the system device manager, as I see is the driver I downloaded from Lenovo a couple of days ago. The device manager driver list doesn't show any "previous drivers" to rollback too.

So I am wondering where I might get that older driver. Do you think the Intel website has the older driver you suggested archived there?

I'm also a bit reluctant to monkey around with the drivers too much as I also have PE2019 on my laptop. I'm afraid if I "fix" the driver in the 2018 edition, that my 2019 version will choke on the older driver... I guess all I can do is try that older driver to see if it can "do good without doing any bad."

So anyway, what source did you use for your driver downloads?

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 06, 2019 0
Community Beginner ,
Jan 06, 2019

Copy link to clipboard

Copied

Hey Coolblueice, if you don’t want to mess with your drivers you could see if Adobe support has other options once their back in office tomorrow. As for my drivers, I updated them via DriverEasy but rolled back via Device Manager on windows 10

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 06, 2019 2
Explorer ,
Jan 06, 2019

Copy link to clipboard

Copied

Hey Bret!

Brilliant! I decided to take the chance and rollback my driver... I found a previous version through the device manager...

After rollback, PE2018 is working just fine, as is PE2019! Thanks sooo much!

Since I had the trial version of PE2019 up and running, I was just about to pay for the license just to get a working version... But now I don't have to shell out that $69.95 ....

I didn't even want to go to the 2019 version because it appeared some fancy video fade was the only new feature that I would remotely stand a chance of using....But now I do not have to buy it!

Thanks again!

          RJ (Coolblueice)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 06, 2019 1
Community Beginner ,
Jan 06, 2019

Copy link to clipboard

Copied

Hey RJ, glad it worked for you as well!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 06, 2019 1
New Here ,
Oct 09, 2020

Copy link to clipboard

Copied

I tried all of these solutions and they did not help.  I resolved the issue by uninstalling Media Encoder and reinstalling it, for anyone looking for further possible solutions.  Get your sh!t together Adobe.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 09, 2020 0