Thank you, I've read about this on various websites and I know that Nvidia version 581.80 works, but I find it unfortunate that Team Vegas isn't doing anything to fix this problem!

Please see this forum post about NVENC compatibility having been removed by NVIDIA with the release of the 591.44 driver: https://www.vegascreativesoftware.info/us/forum/nvenc-nv-encoder-problem-with-new-nvidia-drivers-vp22--150573/. There are other posts about the same issue as well.

As noted in that post, the current options are to roll-back the NVIDIA driver to a version prior to 591.44 or to upgrade to Vegas Pro 23 which doesn't have the NVENC problem - or of course in Vegas Pro 22 (or earlier) use another render format that doesn't involve NVENC.

@L7CFox As you say you've read it on various websites, what have you read?

. I've read about problems with the recent Nvidia drivers on gaming sites, Reddit & the other Magix forum, therefore it's a Nvidia problem not a Vegas problem.

Yes @Gid, it's definitely an Nvidia issue, but when a problem like this affects paid software, the least someone on both sides could do is find a solution instead of passing the buck. This problem is affecting a lot of people and nobody's doing anything! I find it unacceptable that there isn't a temporary fix from the Vegas team, and instead they're suggesting we upgrade to Vegas Pro 23. I don't want to spend any more money to avoid this problem. Upgrading to version 23 is fine, but if the problem reappears later in version 23, that's just unacceptable, and I don't want that!

@L7CFox Take it easy, VP 23 is built with the latest NVIDIA SDK so it and later versions won't be a problem.

There's no way VEGAS is going to reopen development of versions 15-21. The only one that possible is 22 because it's been on sale as of late, but even that isn't likely. If you want to use NV Encoding stick to 580.xx drivers, use NVENC through Voukoder or HOS or upgrade to 23.

Okay, but I'm sorry, I don't approve of this approach at all. They're telling us to upgrade to v23, or I'll have to pay €129.99 to avoid a simple problem that nobody wants to fix! And if this happens again in v23, what will they tell us?! I'm seriously considering quitting Vegas and switching to another editing system because I'm really disappointed!

Upgrading to version 23 is fine, but if the problem reappears later in version 23, that's just unacceptable, and I don't want that!

On that basis, you'd never upgrade to a new version of any software because NVIDIA, Windows and so on might in the future make a change that is problematic for that (any) software. Let's look at a recent example. During Vegas Pro 22's lifetime, Windows removed support for AC-3 with a clean install of 24H2 and Vegas reacted by including inbuilt AC-3 support in the last two VP22 builds - 248 and 250.

As pointed out earlier, NVIDIA's cessation of NVENC support is not just limited to affecting Vegas Pro - do a Google search to find out for yourself. 591.44 looks like it even had a bad effect on Microsoft Fight Simulator.

@L7CFox NVIDIA opted to end support for an older method of encoding. VP 23 by definition doesn't use that method so it can't happen again with 23. If you used another editing system you'd need to pay a subscription or upgrade price to use the current version. I encourage you to join the number of users complaining to NVIDIA via their forum and support channels.
If you want to use NV Encoding stick to 580.xx drivers, use NVENC through Voukoder Pro (69 EUR) or HOS ($59) or upgrade to 23.

Thank you for your messages. I'll think about it, but I can't afford €129 right now. I'll wait for a discount.

@NewVegas22

Vegas 23 was released early september 2025:

https://www.vegascreativesoftware.info/us/forum/release-vegas-pro-23--149552/

You obviosly know nothing about Vegas.

Hello J-Toresen, I didn't understand what this post via your link is about? Is it about upgrading from Vegas 22 to 23?

@L7CFox ...

J-Toresen's response I think was directly in reaction to NewVegas22 hijacking your post with - in English:

According to European law, if Magix doesn't fix this within 3 months, all users will have to be paid $2,000 USD. On Reddit, many people are hiring lawyers. So, Magix will probably patch Vega 22. Or we could make a good profit if you live in Europe.

Vega 22 was sold in January 2026. You can claim your money back or upgrade to Vegas 23 automatically if you have an official Vegas 23 account. If Magix doesn't pay, the fine could be millions of dollars for fraud. I'm okay with a free update, but $2,000 sounds pretty good...

Anyway, Magix, I started legal proceedings in Germany for fraud, and the police told me the Magix address is Wrangelstraße 100, 10997 Berlin, Germany.

I can't see how NewVegas22's comment has anything to do with your original post.

I can't see how NewVegas22's comment has anything to do with your original post.

Seems directly on-point to Nvenc not working for him in vp22. This is not legal advice, but I would speculate that the fact that it works for everyone else with a compatible Nvidia gpu and driver might result in his case being dismissed as frivolous.

I had the pleasure of running into this problem last night. What an absolute pain in the ass. MAGIX seems to be taken the road of 'its Nvidia's problem'. No, it is your problem as it is happening to your product, which was still being sold till very recently. As someone who uses their PC for gaming and video editing, fingers crossed there is a fix in the works . Both companies responses certainly don't inspire confidence. I'd change to AMD, but I changed to Nvidia as I have constant rendering issues with AMD.

The problem has been caused by a change made by Nvidia, not by Vegas. It's a similar situation to Microsoft dropping AC3 encoding/decoding with Windows 11.

Personally I find Nvidia's attitude somewhat arrogant and it puts me off Nvidia.

Yep, classic Nvidia move, they don't care. If AMD worked for me I'd be using them, but Vegas pro and AMD have never worked on my computer unfortunately

For most users there would be no legal case as VEGAS Pro 22 performed as promised during its release cycle and NVIDIA breaking NVENC with a driver happened after 23 was released.

The only question I have is if there's any liability as 22 was sold into 2026 on a discount site, but if that is clearly described as an old version sold as is not sure there are grounds there either. If Microsoft released Windows 12 tomorrow and broke VEGAS 1-23 that's on the user to avoid as it was never sold as compatible.

Whilst I agree that Nvidia's removal of this old support was terrible, it was listed to be removed in 2023 in the developer communications from Nvidia.

Magix should have received this communication, and they clearly knew about it given that they released v23 with updated support, despite Vegas 21 being in current cycle with the communique, and 22 released after the communique.

Magix released a time-bomb with 21 and 22, and they should get updates.

Very disappointed because I only just upgraded to 22 (still for sale) and am ineligible for a refund since it has been activated and used.