Vegas Pro 18 Render As window crashes due to Unmanaged Exception

Dr Zen wrote on 8/12/2020, 7:58 PM

Hello fellow Vegas users 👽

This morning I was greeted by an old chestnut when trying to render a video with Vegas Pro 18.
Every time I tried to open the Render As window, Vegas Pro 18 would crash.
I then opened many older versions of Vegas Pro and they were all still working OK without crashing.

I am confident that I have found the cause of this crash, so I'm posting my solution in case other users experience the same problem.

Cause of problem
I believe the cause of this problem is due to some of the latest Windows 10 Updates that were just released.
I am currently using the latest version of Windows 10 - Version 2004, OS Build 19041.450
In the last couple of days, Windows released some updates for:
.NET Framework 3.5 and 4.8 (KB4569745)
Cumulative update for Windows 10 (KB4566782)

Solution
I found an old forum post here which hinted that this solution may fix the Render As window crash.
Go to the Windows Control Panel / Programs & Features
In the top left corner, select Turn Windows Features on or off
Deselect .NET Framework 3.5
Be patient and wait for Windows to do it's thing
Once it is finished, open window again and turn .NET Framework 3.5 back ON
It may ask to download files - say yes and be patient...

Re-boot computer
Open Vegas Pro 18 and test Render As window - hopefully it is now back to normal.

Regards
Derek

Comments

fr0sty wrote on 8/12/2020, 9:09 PM

Nice. Thank you for sharing. I've seen many posts here lately about users having issues in VEGAS after the new windows update, so perhaps they all should give this method a shot as well.

Dr Zen wrote on 8/12/2020, 9:27 PM

UPDATE!
I spoke to soon. I still have the same problem and am totally depressed.
I don't understand what is causing this.
The first time I re-booted .NET Framework, Vegas Pro 18 stopped crashing when I went to Render As.
But I just re-booted my computer and the problem has returned unfortunately.
I re-booted .NET Framework again, but it is still not working.

The weird thing is that all older versions of Vegas Pro and Vegas Movie Studio Platinum are working OK. So it seems there must be a problem with Vegas Pro 18.

Marco. wrote on 8/13/2020, 3:03 AM

If you have DebugMode FrameServer and/or Voukoder installed, be sure you install their latest versions which were adopted for the work with VP18. These tools may interfere the render workflow from the time you open the render window.

Robert Johnston wrote on 8/13/2020, 5:31 PM

I found a workaround for the "File > Render As" crash on MY machine. It seems that when at least one HEVC media is in the Media Bin, I don't get a crash. The HEVC media doesn't have to be on the timeline, just in the Media Bin. I have no idea why. But now I am able to test rendering in 18, where I found that Magix AVC with QSV creates artifacts, so I just use Sony AVC with QSV.

Dr Zen wrote on 8/14/2020, 9:43 PM

Final report back with the solution that worked!

Thank you @Marco. I did uninstall Debugmode FrameServer v3.0 and Voukoder before you posted your reply. I thought that may have been the cause of the problem as well. Alas it didn't help at all.

I went on a fishing trip into the deepest waters of the Vegas Forums and found another user from years ago, who experienced the exact same problem. The only way he fixed this problem, was to do a "clean" install of Windows.

As much as I was dreading a re-install of Windows 10 (yet again), I decided it would be easier to do that, than waste days on end in the Bermuda Triangle and get lost forever. I firmly believe now that a bad install of the latest .NET Framework updates for Windows 10 v2004, was the cause of the problem. I remember when the update was installing, that something weird happened I had never seen before. When I tried to use Windows Restore, it got stuck in an infinite loop and completely screwed up Windows 10.

Doing a clean install of Windows 10 has fixed the problem with Vegas Pro 18.

I have since installed and uninstalled Debugmode FrameServer and Voukoder numerous times, and nothing has caused the Render As window to crash again, which makes me believe these items had nothing to do with the original problem. It was just another Windows 10 X-File 👽👽👽

Mickael-Lacoste wrote on 12/16/2020, 6:37 PM

Hello all, on my side, I never saw the Render as window, always crash when clicking on button ! I tried many tips, .Net reinstall, Vegas pro reinstall (I'm currently testing trial of 18 and this heavy bug should give me the idea to forget about Vegas).

But after trying to add HEVC vid in media pool ... strange but it works !! Many thanks to

I found a workaround for the "File > Render As" crash on MY machine. It seems that when at least one HEVC media is in the Media Bin, I don't get a crash. The HEVC media doesn't have to be on the timeline, just in the Media Bin. I have no idea why. But now I am able to test rendering in 18, where I found that Magix AVC with QSV creates artifacts, so I just use Sony AVC with QSV.

Many thanks Robert Johnston

TheFox wrote on 12/20/2020, 10:21 AM

Hello all, have anyone of you a HEVC vid for me. I dont find one and i have the same problem. If someone have a HEVC vid, maybe he can send me on my eMail: *@*. Thank you

TheFox wrote on 12/20/2020, 11:04 AM

@Dr Zen. I dont know what you mean with. "Another Windows 10 X-File." I dont know wich File and how i fix the problem. Can you explained for my stupid brain?

vkmast wrote on 12/20/2020, 12:16 PM

@TheFox by "x-file" Dr Zen most likely refers to a case designated "unsolved".

Dr Zen wrote on 12/20/2020, 9:29 PM

Thanks @vkmast

The X-Files was a No.1 hit Sci-Fi show from 90's and 00's
There is no logical "earthly" explanation for an X-file.

dg-pro wrote on 1/3/2021, 12:50 PM

The only solution that worked for me is to disable Integrated graphic card (Intel(R) HD Graphics 4000) in "Device Manager>Display Adaptors" on my laptop leaving only GPU (Nvidia GeForce). Apparently Vegas has issues with it's driver and it was the latest available driver on Intel website.

P.S. The Driver that Vegas Driver Update suggests to install (win64_15.33.53.5161) gives an error "The driver being installed is not validated for this computer..."

RogerS wrote on 1/3/2021, 9:14 PM

@dg-pro Intel(R) HD Graphics 4000 (2012) isn't supported in VP 18. I'd disable it or stick to previous versions of Vegas for this older computer.

dg-pro wrote on 1/4/2021, 12:59 PM

@dg-pro Intel(R) HD Graphics 4000 (2012) isn't supported in VP 18. I'd disable it or stick to previous versions of Vegas for this older computer.

Is there any way to disable usage of Integrated graphic card in Vegas? Otherwise I'll have to disable and then enable it again in Device Manager every time I need to render something because disabling it permanently removes some display features like brightness adjustment after computer restarts.

VEGASPascal wrote on 1/4/2021, 1:39 PM

The only solution that worked for me is to disable Integrated graphic card (Intel(R) HD Graphics 4000) in "Device Manager>Display Adaptors" on my laptop leaving only GPU (Nvidia GeForce). Apparently Vegas has issues with it's driver and it was the latest available driver on Intel website.

P.S. The Driver that Vegas Driver Update suggests to install (win64_15.33.53.5161) gives an error "The driver being installed is not validated for this computer..."

This happens so often to me. Windows detects the onboard GPU but the Intel driver is not able to install. You need a monitor at this onboard device (otherwise the GPU is deactivated).