Cant render out in any AV1, H.264 or H.265

Sging2 wrote on 9/13/2025, 7:26 AM

Hi, I am having an issue with Vegas Pro 22 & 23 where I cant render out to these formats, AV1, H.264 or H.265. I know its a codec licensing issue but the codecs are installed so not sure why Vegas is not seeing them. I tried it with a video and and a simple photograph to rule out any issues with the footage. ProRes renders ok.

I am getting, "The activation code is incorrect. please make sure it has been entered correctly or contact the Magix customer service." I am on 365 so the activation code is correct, I have contacted support about a week ago but haven't had a response.

Hope someone can advise please

Regards

Stephen

Windows 11 ~ 32 GB RAM ~ CPU Intel i9 12900K ~ GPU NVIDIA GeForce RTX 5090 ~ Vegas 365

Comments

Sging2 wrote on 10/23/2025, 9:48 AM

If anyone from Magix is on here can you please help with this as I cannot render my projects. I have raised a number of tickets and I have had no response. My 365 renews next month so I will be stopping the auto renew until this is sorted.

Brianimal wrote on 11/20/2025, 9:13 AM

I am in the same boat. After updating from Windows 10 to 11 via a clean install, I am getting the same error when trying to render. (see screen shot of the most simple test) I have submitted 3 support tickets over the last 16 days, and have yet to receive any human response. One even self closed with out a response. I'm not one to use public forums, but I'm running out of patience. At least I see I'm not alone with this issue. I tried the reset, turning off firewalls and antivirus, and also completely uninstalled, removed all remaining folders, and reinstalled with no luck. Even went so far as to look for registry key permission issues. However, I tried to install it on my laptop and another computer and it activates the codec and renders just fine, so I'm not sure what makes the difference. (I did deactivate the key on the other system after the test) I know its activated correctly as I see it showing up in my account on their website. I'm still on VP22 and have gotten more SPAM emails about updating than I have received support. I hope someone here can point me in the right direction, or at least get someone at MAGIX attention. Thanks!

W11 25H2, i7-12700KF, 32GB, RTX3050

Brianimal wrote on 11/26/2025, 9:39 AM

After 22 days, I finally got a reply from MAGIX about my issue (no apology for the delay or explanation) Turns out I had a invisible character before my email address when activating, I'm assuming an artifact from when I copy pasted my email and activation code from their website. (I think either a tab or CR character, definitely not a space) This seemed to allow the initial software activation with that extra invisible character, but not the rendering codec activation. This is what I got from them incase the other details can help someone else @Sging2
""
What should I do if MPEG-4 codec activation is not possible?

  • Please deactivate the program first via "Help > Deactivate software on this pc" and then restart it.
  • If you are now prompted to register, enter the corresponding serial number and the email address you have already used.
  • Make sure that there are no spaces in the entry.
  • Start the program for activation as an administrator by right-clicking the desktop icon and selecting "Run as administrator".

If activation is still not possible, please open the Windows registry and search for the following key: Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{7DC6E619-5C35-4371-9D2A-9CF021CB55D1}

If the key exists but an error message appears when you click on it, the key is corrupt and must be deleted, but unfortunately this is not possible in the Windows Registry Editor.

Based on our positive experience, we recommend the free program Registrar Registry Manager Home
Registrar Registry Manager Free Home Edition

Enter this key for "Address":
Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{7DC6E619-5C35-4371-9D2A-9CF021CB55D1}
Right-click on the key and select "Delete".

Then open your program with administrator rights and try to activate it again.

""