Skip to main content
Participant
August 3, 2013
Answered

Media Encoder CC not starting

  • August 3, 2013
  • 16 replies
  • 113949 views

Windows7 64 bit

Media Encoder CC (7.0.1)

AME worked a while. I exported a couple of jobs to it's queue. All good. Tried to cancel the jobs and it seemed to hang. Had to kill the application from task manager.

Since then AME will not run. It crashes on startup. No splash screen.. nothing. Appears briefly in task manager then dissapears.

I have deleted all files from C:\Users\login\AppData\Roaming\Adobe\Adobe Media Encoder\7.0

Have reinstalled PremierProCC after uninstalling and using the cleanup tool.

Still no luck. Is there a queue file anywhere that should be deleted?  A registry entry maybe?

This topic has been closed for replies.
Correct answer MaxxDaemon

A MUCH SIMPLER SOLUTION: Open the file (C:\Program Files (x86)\Common Files\Adobe\SLCache\X19zbGNfZmVhdHVyZXNfXw==.slc) in any text editor, delete all of the contents, save it, and set the file to read-only. You'll never have to delete it again and you won't need to mess with all of this batch file, load-order stuff.

16 replies

gabrielr96043275
Participant
June 3, 2020

Had a similar problem and decided to downgrade to previous version. It works as a temporary fix until the next update is released that maybe addresses some issues

Fazal Shah
Participating Frequently
July 11, 2018

Really Helpful.

I tried this but it asks me to do this everytime.

So I automated the process by writing a script.

Here:

Media Encoder CC not starting | EXITMedia - YouTube

Santhosh S
Participant
July 12, 2017

QUES : THE APPLICATION WAS UNABLE TO START CORRECTLY (0XC000007B)

ANS :Copy all files from this path and paste it on to [ C:\Program Files\Adobe\Adobe Media Encoder CC] this path.

This is working for me, try this also maybe help you to recover from the problem.

Thanks.

neob65066384
Participant
April 12, 2017

Where i can find this file ?

KBGamer
Participant
January 16, 2017

Create a bat file with del "C:\Program Files (x86)\Common Files\Adobe\SLCache\X19zbGNfZmVhdHVyZXNfXw==.slc" in it and save it. Before running AME just run the .bat and it'll work.

I tried the "read only" thing but it doesn't work for me.

Participating Frequently
December 14, 2016

I found a way and made a video for it HERE. Full solution, no BAT file, permanent, no extra steps. Should work.

Participant
October 11, 2016

Hello Everyone, Try this ( It worked for me)

Solution #3 (as Roberts Štālbergs suggested) [actually very different issue but same symptoms]

1. Go to "C:\Program Files\Adobe\Adobe Media Encoder CS6" and delete the "amtlib.dll" file [directory may vary depending on what version of Encoder and Windows you have]

2. Go to "C:\Program Files\Adobe\Adobe Premiere Pro CS6", copy the file "amtlib.dll" and paste in the directory from step 1 (C:\Program Files\Adobe\Adobe Media Encoder CS6). [directory may vary depending on what version of Premiere and Windows you have]

Pdt: If don`t Have Premiere, use the same File of other Adobe programm.

Dmitri Graf
Adobe Employee
Adobe Employee
August 12, 2016

Hi Bill,

What happens when you try to launch AME?

What GPU do you have in your Mac Pro?

What have you and tech support tried to do to resolve it?

Has it worked before 2015.3?

Loft54
Known Participant
August 12, 2016

Launched fine. Green arrow to render did not work at all. Called tech support, the fixed it, made a new alias but then  preimier broke. They fixed that today by clearing out all video caches and other files.

video would not play.

Everything worked fine in .2 - sounds like a lot of bugs .3-.4

up and running now. May not update the other 2 computers for awhile  

Running a new 980ti card.

Participant
May 1, 2016

I cleared the text, made it read only, then i denied everyone all permissions for the file and that fixed it!!!

Inspiring
May 8, 2016

Imo, that is the permanent workaround, because if AME has access to this file, it will be overwritten and AME won't start next time.

Cleary, this is a very easy to reproduce bug. Hard to know why Adobe didn't fix it yet.

Participant
April 8, 2016

Thanks a lot......