Unable to install mc_enc_hevc.dll

[rackerman]

I have tried all solutions found through google and used the adobe cleaner to do a fresh install of premiere, nothing seems to get this DLL to load properly. I do have an active Adobe CC subscription as well.

1. OS: Windows 10

2. Version: Adobe Premiere Pro Version 15.2.0 (Build 35)

3. System: 1700x 32gb RAM RTX 3070rakc

4. Footage form Canon R5: H.265 4:2:2 10-bit UHD 4k @ 59.94fps

[Marc220862260e1e]

Normally once you select PremiereProSolver as an user, you will go throught the classic windows settings that need to be done whenever a new user logs in for the first time. 

The rest of what you said is correct, except you don't have to export something, just drop a clip in HEVC format in your timeline. The encodings files will be querried by premiere and installed at this precise moment. 

[Adarsh3612596582wb]

Thank you so much brother . It worked

[yannr23066990]

this was of great help!

what a shame that such massive bugs are not fixed

[defaultwdbjge2k9m0e]

Hello, the first part of this fix worked for me, I can import the video to Premiere in the new account (PremiereProSolver), but when I return to my original account, it still doesn't work 😕 Why can that be? Thank you in advance

[Lyndon285890790riy]

OMG! Works really great! Thank you!

[alzoxp]

Just came to say this fixed my issue - is it great we have to do this...no so Adobe sort this nonsense out.  Thank you for the fix worked perfectly for me and was really easy to follow

[ZAYKO30318156dyj2]

Hey, the command is not working for me. Syntax error

[Christopher3363030271ve]

yes!!!! this helped me, upvote and comment to signal boost!!  Adobe, please fix this issue

[Ian5FF1]

Wow dude, elegant, clean, maybe 10 minutes in total. Great stuff, thanks a ton.

[Sebastian34081706c86a]

Hi. I have NEVER in my 28 years bothered to login to a forum to thank someone for solving a pressing issue, but this here needs to be said:
THANK. YOU. From the bottom of my heart!
I am currently behind in schedule in a project because of this nonsensical error that appeared. (I was working with Sony vegas before and thought it would be a good idea to start fresh with this new project and boy did I run into issues)

Long story short: Thanks a LOTTTTT for clarifying what the guy above said. I wouldnt have understood how to do it even though he explained it. I watched hours of youtube videos and went through every single thing.

At the end I found these things:
- when I ONLY used MP4 files in my project, exporting worked fine. But as soon as I had .mov files, everything went to hell and this error appeared making me lose hair in real time for hours and hours on end

Converting the files to .mp4 before editing them also worked. HOWEVER there are certain files that HAD to stay in .mov (because apparently, the background is then transparent. Like certain after effect stuff I got from envato elements)

-this mentioned folder "AdobeInstalledCodecsTier2" was empty. Completely. BEFORE applying what you said.
Right after I did what you said (I did a quick export from within the "PremiereProSolver" user though just because I didnt want to wait any additional second to check if it works.
It worked.

After going back to my main windows user, it first did NOT work. Because the project (premiere pro) was still open during that time. I did not log out of the users, I just switched.

However, once I closed premiere pro (after doing everything you said), and opening it again, then exporting worked.

Fun Fact:
I found a shortterm solution to that problem previously which was: I changed the path. From my first internal SSD harddrive to my other one (both are identical and were bought only 1 week apart from another). Somehow this worked. For 2 days.
Until now the error came back and almost took my soul.

TL;DR: The solution above worked! THE ONLY THING that truly worked. No other forum, nor youtube video could help!! THanks a freaking lot! Hope you are alright wherever you are.

[Sebastian34081706c86a]

Edit: Forgot to end a sentence:
The "... .dll" files (2 of them) appeared in the "AdobeInstalledCodecsTier2" folder after apply everything you said and going back to my MAIN user and trying the first export.

[Sebastian34081706c86a]

I think my initial comment wasnt replied to the right guy. Search for my name if you want to see a thank you @Marc220862260e1e 

You truly saved me. Thank you!

[TheSailingChannel.TV]

Thank youk Marc. This process worked for me. Previously I had spent nearly two hours with Adobe Premiere Pro tech support with the tech controlling my computer. She said the answer to the problem was to to a clean install of all my CC aps, which I let her do. This took another hour or so due to day's slow internet connection. Eventually we got cut off. After the fresh install I tried again and got the same error. Which I had search this forum first.

When I first ran the command above, I got "this group doesn't exist." But when I ran 'net user' there was PremiereProSolver. I logged in to the new admin account and followed the rest of the directoins. After successfully creating a single proxy by dropping an original 4K file into Media Encoder (I selected Prores quarter frame, which creates a 1920x1080 proxy for a 4K file) magically, two heevc files appeared in the 4.0 folder. I then switched back to my regular admin account and created the rest of my proxies starting in Premiere.

[creativecolors_]

Oh my gosh thank you SO MUCH! I have been dealing with this issue the past few days, I had to literally switch editors and work in da vinci resolve for a few days so that i could make deadlines for a client im working with. I had looked up this issue and even got into contact with adobe support and it wasn't much help. I just thought the footage I was given was just bad because when i worked on a different project it was fine, it was strictly only this footage. I'm so glad i stumbled upon this today, because this has been a literal life saver. Now I can proceed working in premiere pro!
Also for those who may come to this,
I created the user like listed above, and signed in to the profile, then i opened adobe premire pro, downloaded the footage that was giving me issues (this can just be really short) exported it and it was fine. You can also check the folders as well. Once you do that you can go back into your original profile and everything should work

[Yohannes26897706eh9h]

why is this not on top?🤦‍:male_sign:

About to try this, Thank you in advance

[Khan Odita]

Thanks mate, this is the ONLY solution that has worked for me. I have tried about 4 now.

Using DJI Mini 4 pro and suffering issues with premiere and media encoder.

[Proeliator]

This fix is still working in 2025. Thank you!

[ThioJoe]

If Marc220862260e1e's solution works for you then it likely means there's a problem with your Windows account itself.

I believe this happened to me after earlier in the month I changed my Windows account from local to Microsoft account, then back to local again. Perhaps a similar situation for others having the issue. I wonder if it would also happen if you cleared your TPM module.

The .dll files are apparently stored encrypted in "C:\Program Files\Adobe\Adobe Premiere Pro 2025\RuntimeInstallers" for example as ".dat" files, and Adobe decrypts them. (Probably some licensing requirement from MainConcept who makes the DLLs). 

To decrypt it, Adobe apps seem to use Windows' Data Protection API (DPAPI) which stores credentials tied to your user account, and I think in changing between local/Microsoft account the 'master credential' got messed up.

If I look in the Windows Event Viewer logs under "Applications and Services Logs > Microsoft > Windows > Crypto-DPAPI > Operational" , I see errors like this at the same time the error box appears:

DPAPI Unprotect failed .

 	Status:	0x8009000B
 	ReasonForFailure:	Could not get the master key

That would explain why creating a new user account would work. I have not yet found a "proper" solution.

[madalenatphoto]

If this has not worked for you please do check this, as it was what worked for me: 

https://www.youtube.com/watch?v=jxShFDfbr7Y&ab_channel=InacioRedmeen

In short the problem was the windows antivirus blocking the acess, so you just need to manually enable it. Cheers. 

[michaelf28699390]

I have to thank this user and also Marc220862260e1e this was the only solution after countless hours of trying to troubleshoot this. Thank you thank you thank you. 

[aa7bq]

Of all the software packages that I have, Adobe CreativeCloud is the most disappointing, and I've been using Photoshop since version 1.0   I also have this problem and truthfully, IT ISN'T MY PROBLEM TO SOLVE.   If Adobe made automobiles, they would be in the repair shop 100% of the time.   This isn't the Adobe that I used to know.  This is some monstrosity now.  It does not work.

This specifically includes Premiere Pro, Photoshop, and Illustrator.  They all suck now. Thanks Adobe.

[marcelov96479431 · Accepted solution]

Logré reparar el problema. Se soluciona creando otro usuario administrador
en windows. Al activar el nuevo uso de Adobe premiere termina funcionando.

[aa7bq]

Gracias Marcelo. La solución funcionó para mí también. Algo está terriblemente mal con este software si uno tiene que crear un nuevo usuario para solucionar un problema. Adobe debería dejar de actuar como si esto no fuera un ERROR, porque lo es.

[default1j3qujr8y4c9]

This has happened to me today. After years of having it work fine now my software is bricked. I hope someone can tell me a support email or a phone number I can call to get this resolved. I was trying to edit a YouTube video but this has made me highly discouraged. I am to be honest at my wits end over this.

[Kevin-Monahan]

Hi,

Sorry about the frustration. Yes, you can contact support if you are a Creative Cloud customer. Please go to this link: https://helpx.adobe.com/support.html. In the lower right corner is the chat pod. You can request to be connected to the video queue to find our video specialists.

Thanks,
Kevin