Skip to main content
emre_7835
emre_7835
Participant
March 29, 2026

Media Encoder fails all proxy jobs after one corrupted file

  • March 29, 2026
  • 1 reply
  • 18 views

When creating proxies via Premiere Pro using Media Encoder, if one corrupted video file fails during encoding, all subsequent proxy jobs in the queue also fail.

Even completely unrelated files fail after the first error. Restarting Media Encoder temporarily fixes the issue.

Expected behavior: Media Encoder should skip the problematic file and continue processing the rest of the queue.

System details:

Mixed sources (DJI H.265 10-bit + Android)

Hardware decoding disabled

Latest version of Premiere Pro and Media Encoder

    1 reply

    R
    Community Manager
    Rach McIntireCommunity Manager
    Community Manager
    March 30, 2026

    Hi ​@emre_7835, 

    Thanks for the detailed report and the clear repro steps, that really helps.

    A few follow up questions that would help us dig into this further:

    * Which file failed first? Was it one of the DJI H.265 10-bit clips or an Android file?
    * Does it consistently fail on the same file, or does it vary?
    * Are you sending the proxy jobs from Premiere directly, or adding them manually in Media Encoder?
    * Your OS and version
    * Your GPU and driver version

    If you can share the Media Encoder logs from a session where this occurred, that would also be really helpful. You can find them via Help > Log Files in Media Encoder. Feel free to DM me if you prefer.

    Sorry for the frustration, I hope we can get this sorted soon.

    emre_7835
    emre_7835Author
    Participant
    March 30, 2026

    Hi, thanks for your response and for looking into this.

    Here are the details you asked for:

    • Which file failed first?

    The first failure consistently happens on a DJI clip. Specifically, H.265 / HEVC 10-bit footage recorded in D-Log M from a DJI drone.

    • Does it consistently fail on the same file?

    Yes. The same DJI clip always triggers the first failure.

    After that failure occurs, Media Encoder starts failing all subsequent proxy jobs in the queue, even for completely unrelated and previously working files (including Android H.264 clips).

    • How are proxy jobs sent?

    Proxy jobs are sent directly from Premiere Pro using the built-in proxy workflow (Ingest Settings → Create Proxies).

    They are not manually added inside Media Encoder.

    • OS and version

    Windows 11 (latest updates installed)

    • GPU and driver

    NVIDIA RTX 3050 Laptop GPU

    Using NVIDIA Studio Driver (updated March 13, 2026)

    • Additional observation (important)

    Once Media Encoder encounters the first error:

    All subsequent jobs fail immediately

    Even if the files are valid

    Restarting Media Encoder restores normal behavior temporarily

    This suggests the failure leaves Media Encoder in a broken state rather than handling the error per file.

    • Logs

    I will share the Media Encoder logs from a failing session shortly.

    Summary:

    The issue is not just the corrupted file itself, but that Media Encoder does not recover after encountering a failure and incorrectly fails all subsequent jobs.

    Thanks again for investigating this — let me know if you need sample files or additional reproduction steps.

    R
    Community Manager
    Rach McIntireCommunity Manager
    Community Manager
    March 30, 2026

    Hi ​@emre_7835,

     

    Thanks for the detailed follow-up.  A couple of things to try/ questions:

     

    * If you manually skip the DJI clip in the queue, do the remaining jobs complete successfully?

     

    * In Media Encoder, go to Preferences > General and try disabling Parallel Encoding. Does that change anything?

     

    If you have the logs, please do share them. Also, if you can share the DJI clip that triggers the failure, that would be really helpful for us to try to reproduce it on our end. The lack of recovery afterwards is particularly what I’d like to reproduce.  Feel free to DM me if you prefer.

     

    Thanks again for the detail, it really helps.

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