Skip to main content
ryano1534613
Participant
February 10, 2025
Answered

"Adobe Media Encoder 2025" is damaged and can't be opened.

  • February 10, 2025
  • 2 replies
  • 3831 views

I recently updated my after effects and adobe media encoder to 2025. Now everytime i try to render a video through media encoder it says 

"Adobe Media Encoder 2025" is damaged and can't be opened.

You should move it to the Trash.

This file was downloaded on an unknown date.

I'm on a m1 macbook pro and use these programs regularly for work. I tried to install the previous version of media encoder and get the same issue. I don't understad what could be causing this issue. and am struggling to find other people experiencing this online.

Correct answer ryano1534613

I had uninstalled and reinstalled through creative cloud a bunch of times and it wasn't working. What ended up solving it is similar to your second suggestion. I unistalled both after effets and media encoder with appcleaner and reinstalled them(I also cleared my past settings and prefrences, though i'm not sure if that helped at all?)

2 replies

Inspiring
February 14, 2025

Try this Go to System Settings > Privacy & Security, scroll down to Security, and check if there’s an option to allow Adobe Media Encoder to run. If that doesn’t work, try reinstalling using Creative Cloud Cleaner Tool to remove any corrupted files before reinstalling. Hope this helps!

nishu_kush
Community Manager
Community Manager
February 14, 2025

Can you check if dragging the After Effects project file in Media Encoder works? Do you get this issue with all the projects? Are you using any third-party plug-ins for After Effects?

Let us know.


Thanks,
Nishu

ToolfarmJP
Community Expert
Community Expert
February 14, 2025

In order to check the permission of the application, would you try to launch  Media  Encoder, using the command line by Terminal? The command line is something like this.

 

sudo open /Applications/Adobe\ Media\ Encoder\ 2025/Adobe\ Media\ Encoder\ 2025.app

 

 

 

Participant
February 22, 2025

i get the same thing and as soon as a newer version comes out it goes back to not working. not managed to get the beta or non-beta running after installs either. Im also running an M1 macbook pro on Sequoia 15.3.1