This file requires the HEVC codec which is included with a Creative Cloud membership. To upgrade...

[Macgeekppc]

For some reason, Adobe Premiere Rush won't import a small H.265 clip. It gives me this error when it opens the folder where the clip resides:

"This file requires the HEVC codec which is included with a Creative Cloud membership. To upgrade to a paid plan, go to..."

I have purchased Rush. I have uninstalled it then reinstalled it. I have signed in and out of Creative Cloud on the Web as well as the desktop app. I still get the error.

Also, the thumbnail of the clip, when trying to start a new project shows "Unable to Load Preview." When I select it and click Create, I get another error message:

"The importer reported a generic error."

Any suggestions on how to fix this?

[Larry38649694wjkx]

It's October of 2024, the problem still exists. The error says, "This file requires the HEVC codecs wich is included with a Creative Cloud membership. To upgrade to a paid plan, go to www.adobe.com/go/video

This takes you to a Page Not Found.  Of course I have a CC membership. apparently,, this problem has been going on for 5 years.. Now, Microsoft wants a dollar for the Codecs, which does nothing. Corporate greed.

[Larry38649694wjkx]

okay, this using an older version solution works, for 3 exports only, which shows Adobe knows how to fix it, but it's just greed. Just like wanting to use our content to teach it's AI. Just disgusting, instead of telling the truth, they make users jump through hoops as if they're working on the problem. Previous versions work, they just want more money.  See here:

------

jeremyh53115868

Community Beginner , 

Nov 06, 2021

Copy link to clipboard

I believe I found a fix! I reinstalled an older version of Rush. Version 1.5.54 works. The most recent (1.5.62) and the second most recent (1.5.58) both gave me the error.

You can reinstall older versions from Creative Cloud. Click the three dots beside Premiere Rush and then 'Other versions'. Install 1.5.54.

[ProDesignTools]

@Larry38649694wjkx –

Note: Adobe does not use customer content to train AI.

"We do not and have never trained Adobe Firefly on customer content.

Adobe Firefly is trained on a dataset of licensed content, such as Adobe Stock, and public domain content where copyright has expired. Adobe Stock content is covered under a separate license agreement, and Adobe compensates contributors for the use of that content.

We do not train and have never trained Adobe Firefly on user content."

https://www.adobe.com/ai/overview/firefly/gen-ai-approach.html

[Larry38649694wjkx]

Wow, a double denial. Sure, but Adobe was going to, according to the recent Terms of Service. Adobe backed off only  when it got a firestorm of customer complaints. This is well documented, unless Adobe deleted the comments.

What's glaringly missing is the denial that Adobe caused this Premiere Rush problem deliberately, because it worked in previous versions. Yet, Adobe allows customers to chase their tails and waste their time, when Adobe KNOWS they've caused the problem. Where's the denial about that?

[Kevin-Monahan]

Hello @Larry38649694wjkx,

Thanks for the note! Please check out my response here to see if it helps: https://community.adobe.com/t5/premiere-rush-discussions/this-file-requires-the-hevc-codec-which-is-...

HEVC codec licensing might also be an issue with R/W permissions and the OS, not Rush. This problem can also crop up in Premiere Pro, so I suggested you check for the same issue in Rush.

Let me know if that works for you.

Thanks,
Kevin

[BruceK360]

At least you brought some humour to this frustrating situation.  And a warning that I shouldn't spend the rest of my retirement years floundering with Adobe Support looking for a solution.  Booked a game at the golf simulator instead, thinking that the frustration of bad golf will ease my frustration not being able to edit my Snow Owl videos.  Smashing my thumb with a hammer made my headace disappear.

[rickeyw13557106]

I am also having the same issue while using Windows 10. I am a paid customer and cannot understand why Adobe will NOT just fix the issue instead of asking their customers to waste time attempting to resolve the issue using workarounds. This is insane!

[ProDesignTools]

Hi @rickeyw13557106 

Please try this solution suggested below, and let us know it it helps:

https://community.adobe.com/t5/premiere-rush-discussions/this-file-requires-the-hevc-codec-which-is-...

Thanks

[jeremyh53115868]

I believe I found a fix! I reinstalled an older version of Rush. Version 1.5.54 works. The most recent (1.5.62) and the second most recent (1.5.58) both gave me the error.

You can reinstall older versions from Creative Cloud. Click the three dots beside Premiere Rush and then 'Other versions'. Install 1.5.54.

[Ioannis5E6D]

This is true, it worked for me as well, i tried it today, maybe after seeing your post Jeremy so thanks anyway.

It is amazing Adobe support is not aware of this huge how can we call it, bug or similar? Instead of telling you go to 1.5.54 they waste your time.

After about an hour my agent told me to try the previous version, 1.5.58, i did but failed as the newest one. I did not think of installing "2 versions before"

No more HECV or freeze or crash of RUSH now. 

[alayynay]

Also worked for me. 

With version 2.0, it says "unlimited exports for all users!". You would think that this issue would be fixed but no, version 2.0 i still get the HVEC issue. Weird especially because I had exported this exact video a couple versions ago, not sure if it was after 1.5.54.

Cmon adobe, figure this out! 

[lieutenantdaily]

This worked for me as well!

Adobe,

While this workaround does solve the problem, it is not a real solution. Using an outdated version of the software is not how this should work.

[ProDesignTools]

Agreed – but the workaround has been marked as the correct answer to this inquiry for now, because it addresses the problem and there is no better solution at this time.

That way, others who search the error message and come across this thread from Google etc., will immediately know what to do in order to take care of the issue and get back to work, without wasting too much time.

(Of course, once Adobe addresses this by updating Rush or some other fix, then we can adjust the correct answer to this discussion.)

[lieutenantdaily]

I spoke too soon. It stopped working... 😕

[Silas5FAB]

Mine never worked with the downgraded version.  Mine also isn't working by canceling my 2 subscriptions and combining them in the new photography 1T plan that has Photoshop and Rush in the same.  This was tech supports fix and it still is broken. 

[reece5FE3]

This still hasn't been resolved in 2.0 and now 1.5.54 no longer works

[amandab93190441]

I tried this as well, however it didn't work for me. I'm on 1.5.54, and I still have issues loading videos from my Hero 7. For now I'm using handbrake to encode the videos. Once I do that they work fine. This is an ok solution for me for part time because I only use the Hero 7 for a few clips in every other video I publish. Can't wait to see a real fix, or I may upgrade to the full suite as I've been debating that for a while.

[excited_soldier98BC]

This works!!! 

I'm new to all things video and you folks have turned my despair into hope that I can do this! 

[ct_cyclist321]

I've had the same issue, and downgrading to 1.5.54 didn't work either.  This only seems to happen when I try to upload 5k video from my GoPro Hero 9.  Looks like Adobe has no clue why this is happening or how to fix it from what I can see.

[Brad Mustow]

Its still happening to me with Gopro 11 files in Dec 2022. Maybe there's a connection some how. Cant even use the older Rush it just causes blue screen of death and a reboot now when it used to work.

[Daniel_K90]

This worked for me, with v1.5.54, January 28th, 2022. Can't believe it's still not fixed!

[defaultqi8nplwh12nr]

Thx so much! It means it's a problem that was added with an update... wow

[hermez kendo]

Can confirm, this seems to still be the only workaround as of August 2022.

[Chrooth]

Testing this now! Thankfully, Adobe is absolutely committed to never adding feature updates so they can screw people into upgrading to Premiere Pro, so going back to the old version shouldn't be painful.

.....

Wild... Going back to the old version seemed to result in a performance hit, not too bad though. Also, got a completely new error the first time I tried to render... Changed NOTHING... Second render attempt worked perfectly.
....
For those who can't get the older version to work, I was also able to get what I needed, albeit at lower quality by loading clips into rush, playing the preview and using the OBS screen capture tool. The codec error didn't have any impact on the process until I tried to render so OBS capture worked fine.

[Wongsakorn5C47]

I just tried that as you said and now my latest project are gone lol, is there any way to recover the work on this version?