Thanks for the updates everyone. I agree with others that it looks like Nvidia has no intention of supporting API calls that older versions of Vegas are using. I'd pay $10 to fund a patch so I can continue using Vegas 21 and be able to update my Nvidia drivers. I'm not even joking. It looks like 23 has its own set of issues and I've finally gotten to a point that 21 is working okay on my machine and don't want to jinx it.

I might upgrade from 21 to 24 whenever that comes out, but I have little interest in 23 unless it goes on a big sale. I'd consider 23 for like $50 if they give users of older versions a special coupon as an alternative to paying for a version 21 patch. The big problem I see is all of the 22 users that recently bought in through the humble bundle and like others mentioned that older versions exist on Steam.

@ccscotty A dual-boot setup would allow different Nvidia driver versions to co-exist on the same machine.

@ccscotty A dual-boot setup would allow different Nvidia driver versions to co-exist on the same machine.

Dual boot setup will work but one would have to buy another Windows license and possibly licenses for other software. It's a very inconvenient solution to say the least. Given that gamers struggle with older games breaking or running worse on newer drivers I'm surprised that Nvidia hasn't added a feature that allows one to select the driver version one wishes to use without having to uninstall/reinstall. Even if one had to reboot to switch, though it would be best if one could switch driver version without rebooting.

Given that this is a serious issue MAGIX should make a public statement about it and if they plan to fix it or not. They should also update the system requirements and list Nvidia driver versions that are compatible where they sell VEGAS Pro 22 and older versions. If they don't plan to provide a fix it would go a long way if MAGIX would offer a significant discount to upgrade to VEGAS Pro 23, even if it's limited to those that have recently purchased VEGAS Pro 22.

>without having to uninstall/reinstall
Sadly not really under nVidia's control. It's really part of Microsoft's kernel-level driver framework that requires an Install as part of replacing a driver

@ccscotty A dual-boot setup would allow different Nvidia driver versions to co-exist on the same machine.

Dual boot setup will work but one would have to buy another Windows license...

@LucidDreams Not according to this discussion:

https://forums.tomshardware.com/threads/how-many-licenses-do-i-need-dual-booting-with-one-drive-being-a-clone-and-the-other-being-moved-from-an-old-pc.3883812/

However, I've never dual-booted the same OS version myself. I've done win10 &11 most recently starting with oem win10 upgraded for free to 11. But Vegas saw win10 and 11 as different machines that consumed both of its 2 allowed licenses.

Thanks for the updates everyone. I agree with others that it looks like Nvidia has no intention of supporting API calls that older versions of Vegas are using. I'd pay $10 to fund a patch so I can continue using Vegas 21 and be able to update my Nvidia drivers. I'm not even joking. It looks like 23 has its own set of issues and I've finally gotten to a point that 21 is working okay on my machine and don't want to jinx it.

I might upgrade from 21 to 24 whenever that comes out, but I have little interest in 23 unless it goes on a big sale. I'd consider 23 for like $50 if they give users of older versions a special coupon as an alternative to paying for a version 21 patch. The big problem I see is all of the 22 users that recently bought in through the humble bundle and like others mentioned that older versions exist on Steam.

@ccscotty A dual-boot setup would allow different Nvidia driver versions to co-exist on the same machine.

I'd rather see Magix offer a solution even if it's at a small fee. I don't suspect they will do that. I think I need to start sending them feedback directly because I don't know how much employees monitor this forum. I'm not really looking for solutions like this, but I understand you are coming from a place of trying to help. Thanks

I want to see Vegas Pro succeed as a application from a popularity and financial standpoint, but from my perspective as a somewhat long term customer (v14 or v15 for Pro and before that Vegas consumer versions), they are struggling with lack of resources while also making choices that make it difficult for me to recommend their software when options like Resolve exist. I've had people ask me what editing software I use and I always have to give them a list of caveats, but I also say that Vegas Pro scripting capabilities for technical people is a massively powerful feature and the reason I continue to use it. Though even with that feature they removed script debugging capabilities with Visual Studio due to business reasons which circles back to my frustration as a customer.

Then there's features like the text based editing which I purchased 21 to try out, but used it only one or twice due to it using a slow web service to turn speech into text. I might roll my own local solution with a script eventually. Anyways, my point is as a paying customer and one that generally likes the program, I'm hoping for better from the company and business side. Sure, they can follow their policy strictly where only the latest version gets any form of patch, but I'm hoping for more as a long term customer.

@ccscotty A dual-boot setup would allow different Nvidia driver versions to co-exist on the same machine.

Dual boot setup will work but one would have to buy another Windows license...

@LucidDreams Not according to this discussion:

https://forums.tomshardware.com/threads/how-many-licenses-do-i-need-dual-booting-with-one-drive-being-a-clone-and-the-other-being-moved-from-an-old-pc.3883812/

However, I've never dual-booted the same OS version myself. I've done win10 &11 most recently starting with oem win10 upgraded for free to 11. But Vegas saw win10 and 11 as different machines that consumed both of its 2 allowed licenses.

Er ... the thread you reference makes it pretty clear you need a licence for each instance

@LucidDreams Not according to this discussion:

https://forums.tomshardware.com/threads/how-many-licenses-do-i-need-dual-booting-with-one-drive-being-a-clone-and-the-other-being-moved-from-an-old-pc.3883812/

However, I've never dual-booted the same OS version myself. I've done win10 &11 most recently starting with oem win10 upgraded for free to 11. But Vegas saw win10 and 11 as different machines that consumed both of its 2 allowed licenses.

Er ... the thread you reference makes it pretty clear you need a licence for each instance

@MikeS Negative on that. Only comment I see in that thread where 2 instances might require separate OS licenses is when one is remote. Which is not a dual-boot situation. I would go further and expect multiple licenses to be appropriate when multiple instance run concurrently, even if local, as they would with virtualization.

I'm personally not inclined to go dual-boot again to accommodate Nvidia. I'll use Nvidia gpus as long as they perform better and more conveniently for me than the competition. But if Vegas gets itself back up to speed with Amd and/or Intel gpus, I'll switch. Or go back to a multi-gpu system. I still haven't settled on a new workhorse desktop setup... my thinking was moving away from Xeon or Ryzen workstations with an abundance of pcie lanes and slots but Nvidia is giving me 2nd thoughts.

>without having to uninstall/reinstall
Sadly not really under nVidia's control. It's really part of Microsoft's kernel-level driver framework that requires an Install as part of replacing a driver

There are ways to create drivers that don't require a reboot. It reminds me of the days when databases had to be inactive to back them up. That's no longer the case nowadays. I can see why companies don't do it since it would take more development time that adds no value to the function of the drivers themselves. Likewise, without Microsoft creating a standard for it then installs could break from changes Microsoft makes to Windows.

@LucidDreams Not according to this discussion:

https://forums.tomshardware.com/threads/how-many-licenses-do-i-need-dual-booting-with-one-drive-being-a-clone-and-the-other-being-moved-from-an-old-pc.3883812/

However, I've never dual-booted the same OS version myself. I've done win10 &11 most recently starting with oem win10 upgraded for free to 11. But Vegas saw win10 and 11 as different machines that consumed both of its 2 allowed licenses.

Er ... the thread you reference makes it pretty clear you need a licence for each instance

@MikeS Negative on that. Only comment I see in that thread where 2 instances might require separate OS licenses is when one is remote. Which is not a dual-boot situation. I would go further and expect multiple licenses to be appropriate when multiple instance run concurrently, even if local, as they would with virtualization.

Technically one can install Windows 11 twice on the same PC using the same license. But it's in violation of Microsoft's end user license agreement. Same applies to VMs, a separate license is needed per active installation, even if only a single instance will ever be run at a time. There's also the problem that people might have to purchase another license for software they want to use in the second instance of Windows 11 as well. With all the tracking Microsoft is doing with Windows 11 nowadays and defaulting installs to create a Microsoft account, unless one manually overrides it, they could decide to crack down on multiple installs on the same PC or the use of the same Microsoft account on multiple installs could cause problems in the future.

>There are ways to create drivers that don't require a reboot
Never suggested otherwise.

>Negative on that

I think you are being somewhat optimistic in your interpretation of the thread.

But let's be clear, the Windows EULA says different:

You may install one copy of the software on one device.

and:

A separate license is required for each instance of the software installed.

Microsoft uses the word “instance” to mean each installed copy, not each physical machine.

So if you install Windows twice on the same PC — even on separate partitions or drives — you have two instances, and therefore need two licences.

Sure, there are plenty of ways to get a dual boot system working with only a single licence, but you'd be in breach of the EULA. Of course, you may not care about that.

>There are ways to create drivers that don't require a reboot
Never suggested otherwise.

 

>Negative on that

I think you are being somewhat optimistic in your interpretation of the thread.

But let's be clear, the Windows EULA says different:

You may install one copy of the software on one device.

and:

A separate license is required for each instance of the software installed.

Microsoft uses the word “instance” to mean each installed copy, not each physical machine.

So if you install Windows twice on the same PC — even on separate partitions or drives — you have two instances, and therefore need two licences.

Sure, there are plenty of ways to get a dual boot system working with only a single licence, but you'd be in breach of the EULA. Of course, you may not care about that.

@MikeS Your idea of what a device is for the purposes of Microsoft OS licensing seems to be different from theirs. They employ a device ID that is calculated from hardware registered in bios. This discussion on the Microsoft support site refers to that... apparently if the dual boot is implemented on a single boot device, the ID's for both boots come up identical and they are fine with that:

https://learn.microsoft.com/en-us/answers/questions/2198975/is-dual-boot-still-allowed-on-a-single-pc-with-a-d

This usually only comes up with OS updates and is the common way to beta-test and report issues to Microsoft. I don't recall the problem folks are having here coming up since the time Nvidia removed OpenCL from it's drivers to force wider adoption of the then new Cuda api... back then allot of folks froze their Nvidia driver updates until they needed to get a newer gpu, often switching to Amd.

Hello, it's been two months since I've been able to update NVIDIA because of this rendering problem with VP22. At first, there were no issues, but now I can't even shut down my PC because of the outdated updates. What can I do? (I can't use VP23 because of its poor color handling on MOV files) 😣

NVIDIA updates or lack thereof shouldn't have any impact on shutting down your PC. I have two systems with 581 era drivers myself.

NVIDIA released a security patch for 581 though seems to target systems that aren't able to upgrade to 59X.XX.

If something stopped working right with the drivers you can use the NVIDIA cleanup tool and reinstall. https://developer.nvidia.com/downloads/cleanup-tool

Microsoft appear to be acknowledging that W11 has been a mess over that last few months with update after update breaking windows stability. MS have issued a statement that improved stability will be the focus over the coming updates. You tubers such as Britec ( and others following the issues and offering advice on keeping your system stable.

That's interesting. I haven't experienced problems with Windows 11 Currently I'm on 25H2 Build 26200.7623.

My current 25H2 is 26200.7705 which includes some updates to fix past issues.

My current 25H2 is 26200.7705 which includes some updates to fix past issues.

Yes, on checking 7705 is now available for my system.