The activation of AAC (MC) failed - Vegas Pro 18

Comments

vkmast wrote on 10/25/2023, 7:45 AM

@Kauko-Suominen have you checked this thread (in the German forum)?

Kauko-Suominen wrote on 10/26/2023, 1:33 AM

I've tried all the advice except reinstalling the system, which helped in that case. For some, the problem has returned shortly after reinstalling. The connection of Vegas to Internet Explorer may be an explanatory factor for the problem and there is no definitive solution. Windows updates in some configurations may remove the previously working activation.

Kauko-Suominen wrote on 10/30/2023, 3:34 AM

I asked Magix to send me an explanation of the Vegas codec activation mechanism so I could look for the reason why it doesn't work, even though I've tried all the ways I could find to fix it except reinstalling the system. I haven't received any answer. At least I wouldn't feel any pangs of conscience if I looked for pirated Vegas now and see if it works on my PC.

RogerS wrote on 10/30/2023, 4:13 AM

How would a pirated version handle the codec activation any better? Doesn't that just break the license check?

Anyway I hope you find a solution or move on as nobody seems to be able to assist.

Last changed by RogerS on 10/30/2023, 4:14 AM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.239

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Kauko-Suominen wrote on 10/30/2023, 7:44 AM

It is obviously wishful thinking that the activation of the codecs would have been changed as well. The most amazing thing is that nobody seems to have solved this most difficult kind of activation problem except by reinstalling the entire system. Even though the whole other system works except Vegas pro.

Kauko-Suominen wrote on 10/31/2023, 3:55 AM

How can I open and read Vegas error files .erpt?

Kauko-Suominen wrote on 11/1/2023, 6:13 AM

I wish that person had put that registry key on the forum, when Magix doesn't say it. Magix. Magix stopped contacting me when I asked for more in-depth instructions.

vkmast wrote on 11/1/2023, 7:29 AM

So the comments (and the solution) from user Kwigg in the German language thread I gave a link to did not help in your case?

@Kauko-Suominen

Kauko-Suominen wrote on 11/1/2023, 10:42 AM

They didn't help. The only thing I haven't been able to try is the aforementioned connection to the desktop version of Internet Explorer. It no longer works after Microsoft has disabled it. I haven't found any working instructions for restoring IE.

Edo-Amin wrote on 11/20/2023, 6:09 AM

So I, too, have this activation issue on VP14 (yep, and my standard superstable workspace is still VP12). VP14 on a fairly clean machine, and using mobile phone Internet connection instead of network, still no go. I guess this is the end of the road, right?
Where do you go from here, guys? What editor do you use after old VP do not activate anymore?

RogerS wrote on 11/20/2023, 6:39 AM

Did each of you file a support request? Would be good for them to know there are multiple people with this issue and perhaps they have a fix for at least someone?

Kauko-Suominen wrote on 12/6/2023, 1:47 PM

I had a long exchange of messages with Magix. There was no useful advice. It became clear that the activation is tied to Internet Explorer components. Microsoft has killed IE. According to Magix, it should still work. But I think the problem may be related to that. I never received any more in-depth explanation of how the activation works so I could research.

Andre-Koch wrote on 1/9/2024, 9:07 AM

Im having the same issue for a few months now. Really sad that Vegas is now unusable. I tried a lot of things and advices from other threads, as it seems there are more people with that issue.

- uninstalled, reinstalled several times

- Allow software in firewall and defender, also tried with completely deactivated firewall and windows defender

- Starting as adminstrator

- Deleted a bunch of (red) registry entries

- deactivated and reactivated my computer on the vegas account page

- converted the mp4-files via an online-video-converter in other formats and files

- contacted the magix support

- Tried some changes in the internal-settings-tab

frmax wrote on 1/9/2024, 4:19 PM

Translation of the solution from the German forum of user Kwiqq  on 6/29/2021

The solution was to delete one or more Regedit entries.
In my case:
Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{A807D72D-4267-43fa-8217-07C9FDCDBFF6}

This was not possible with the normal Windows Regeditor, as it claimed the entry was defective. With this program it was possible:
Registrar Registry Manager

https://www.resplendence.com/downloads
As this key alone was not enough, I deleted other keys according to the same pattern within CLSID, which were marked as "unknown" (red) by the program. After that it worked. The defective key came back, when I had the program running and deleted it while it was running, all the plugin activations also worked.

 

Similar findings of webkeeper  https://www.vegascreativesoftware.info/us/forum/vegase-16-mpeg-4-codec-not-activating-failure-during-start--116991/#ca728922

Hope it helps, friends

I9900K, RTX 2080, 32GB RAM, 512Mb M2, 1TB SSD, VEGAS Pro 14-20 (Post), Magix ProX, HitfilmPro
AMD 5900, RTX 3090 TI, 64GB RAM, 1 TB M2 SSD, 4 TB HD, VP 21 Post, VP22

Monitor LG 32UN880; Camera Sony FDR-AX53; Photo Canon EOS, Samsung S22 Ultra