Skip to main content
Inspiring
July 16, 2026
Question

Media Encoder Queue Management Woes

  • July 16, 2026
  • 4 replies
  • 57 views

I have some serious issues trying to manage the queue in Media Encoder (v26.3.1).  I loaded 250-odd items into the ME queue. After a couple has processed, I changed my mind and stopped processing the queue (red Stop Queue button). I then closed ME down for the day.

Next day, I restarted ME and I found that the Queue pane was empty with the status saying 2 of 252 items processed, a bad sign IMHO.  The Start Queue and Stop Queue buttons were greyed out. I dropped another file into the Queue pane and Start Queue turned green. I clicked Start Queue to start the conversion. ME then started processing the original queue contents from the previous night. Not what I wanted and a bit unexpected.

It seems I need to clear out the old queue. There must be a way to do this but I can't find it. I can't select the files and remove them individually as the old queue members are not visible since I restarted ME.

So, two questions:

1) How do I clear the ME queue?
2) How do I redisplay the queue members after restarting ME?

I would be grateful for any help...

    4 replies

    Participant
    August 29, 2026

    I found the answer: Open Media Encoder and hold Shift (Mac & Windows) while it boots up. This will bring up a dialog box. From there, check “Reset app preferences” & “Clear media cache files,” then hit “Relaunch with Options.” This will restart Media Encoder, and you should be good to go. I just had this happen to me and spoke with Adobe Support, and this is how they fixed it.

    NickMcGAuthor
    Inspiring
    September 9, 2026

    Good one.  Lot simpler than my eventual solution which was to delete the cache (and cache database) folders, uninstall, reboot and then reinstall and try again.

    Participant
    August 20, 2026

    Same. I’m stuck with the same issue. I can’t clear the queue. Whenever I start encoding a new one the old queue shows up. Such a waste of time

    Participant
    August 19, 2026

    Same error for me on 26.3.2