Thanks for the input. I record video in either Long GOP or All-Intra, which I then import to Vegas, do some colouring, etc. I leave Vegas at the default settings. It's when I click on rendering that the crash happens, so I can't get to the rendering settings. Below is/are the error details.

Extra Information
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\fileio_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\persist.prefs
   File:                
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\dx_video_grovel_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\svfx_video_grovel_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\ocio_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\dx_grovel_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\vst_grovel.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\vegas_script_x64.log
   File:                C:\Users\LONGHORNE\AppData\Local\VEGAS Pro\22.0\hub.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 93)

Fault Process Details
   Process Path:        C:\PROGRA~1\VEGAS\VEGASP~1.0\vegas220.exe
   Process Version:     Version 22.0 (Build 93)
   Process Description: VEGAS Pro
   Process Image Date:  2024-07-23 (Tue Jul 23) 08:02:32

Also, I get the below pop up error whenever I start Vegas, though it does not crash. I have Microsoft Edge, and Webview2 installed.

'Webview2 failed initialization, error information follows:

Server execution failed (Exception from HRESULT:0x8008005 (CO_E_SERVER_EXEC_FAILURE)'

Does it crash immediately upon choosing "Render As" or does it show you the whole dialog for choosing render templates etc and then crash when you "Render". If the latter, does it depend which render template you choose?

It crashes upon choosing "Render As".

Make sure you have the latest .Net Framework for your system, from Microsoft installed: LINK

And the latest Microsoft Visual C++ Redistributables: LINK

It crashes upon choosing "Render As".

This usually means that one of the codecs is failing to initialize. This is very unusual for VPro 22, but not unheard of. After a crash, please provide this file to us to examine: C:\Users\(user name)\AppData\Local\VEGAS Pro\22.0\vegas_script_x64.log

Thanks Steve_Rhoden. I installed the latest .Net Framework, but the error persists.

VEGASDerek, I have since downgraded to v20, just to see if I had any luck. I also downgraded NVIDIA graphics to v537.58, as many folks in the NVIDIA community seem to be happy with.

The error popup that happens right after I click on 'render as', seems to indicate it's a hardware decoder error.

vegas_script_x64.log

INFO 2024-09-12 13:55:09 *** Start of VEGAS Scripting log ***
INFO 2024-09-12 13:55:09 VEGAS Pro 20.0
INFO 2024-09-12 13:55:09 Version 20.0 (Build 403)
INFO 2024-09-12 13:55:09 
INFO 2024-09-12 13:55:10 Invoke View.ColorGradingToolsCommand Succeeded
INFO 2024-09-12 13:55:11 Invoke View.ProjectNotesPaneCommand Succeeded
INFO 2024-09-12 13:55:12 Invoke View.TransitionWPFPaneCommand Succeeded
INFO 2024-09-12 13:55:12 Invoke View.MediaGeneratorWPFPaneCommand Succeeded
INFO 2024-09-12 13:55:12 Invoke View.VideoFXWPFPaneCommand Succeeded
INFO 2024-09-12 13:55:12 Invoke View.HubExplorerPaneCommand Succeeded
INFO 2024-09-12 13:55:13 Invoke View.StoryblocksGuiCommand Succeeded
INFO 2024-09-12 13:56:31 Invoke Tools.PreferencesDialog Succeeded

So4HardwareDetectionOutput

<?xml version="1.0" encoding="utf-8"?>
<hardware_detection>
    <version>2</version>
    <operating_system>
        <version>2009</version>
        <build_number>19044</build_number>
        <updated_build_revision>1288</updated_build_revision>
    </operating_system>
    <OpenCL>
        <num_platforms>2</num_platforms>
        <platform_0>
            <name>NVIDIA CUDA</name>
            <vendor>NVIDIA Corporation</vendor>
            <version>OpenCL 3.0 CUDA 12.2.146</version>
            <num_devices>1</num_devices>
            <device_0>
                <name>NVIDIA GeForce RTX 3060 Laptop GPU</name>
                <version>OpenCL 3.0 CUDA</version>
                <driver_version>537.58</driver_version>
                <boardName/>
                <pciId>0</pciId>
                <pciSlot>0000:01:00.0</pciSlot>
                <platformIndex>0</platformIndex>
                <deviceIndex>0</deviceIndex>
            </device_0>
        </platform_0>
        <platform_1>
            <name>AMD Accelerated Parallel Processing</name>
            <vendor>Advanced Micro Devices, Inc.</vendor>
            <version>OpenCL 2.1 AMD-APP (3444.0)</version>
            <num_devices>1</num_devices>
            <device_0>
                <name>AMD Radeon(TM) Graphics</name>
                <version>OpenCL 2.0 AMD-APP (3444.0)</version>
                <driver_version>3444.0 (PAL,HSAIL)</driver_version>
                <boardName>gfx90c</boardName>
                <pciId>5688</pciId>
                <pciSlot>0000:05:00.0</pciSlot>
                <platformIndex>1</platformIndex>
                <deviceIndex>0</deviceIndex>
            </device_0>
        </platform_1>
    </OpenCL>
    <DXGI>
        <num_adapters>3</num_adapters>
        <adapter_0>
            <adapter_number>0</adapter_number>
            <vendor_id>4318</vendor_id>
            <device_id>9504</device_id>
            <device_name>NVIDIA GeForce RTX 3060 Laptop GPU</device_name>
        </adapter_0>
        <adapter_1>
            <adapter_number>1</adapter_number>
            <vendor_id>4098</vendor_id>
            <device_id>5688</device_id>
            <device_name>AMD Radeon(TM) Graphics</device_name>
        </adapter_1>
        <adapter_2>
            <adapter_number>2</adapter_number>
            <vendor_id>5140</vendor_id>
            <device_id>140</device_id>
            <device_name>Microsoft Basic Render Driver</device_name>
        </adapter_2>
    </DXGI>
    <hardware_decoders>
        <num_decoders>2</num_decoders>
        <preferred_decoder_0>
            <vendor_id>4</vendor_id>
            <vendor_name>NVDEC</vendor_name>
            <device_name>NVIDIA GeForce RTX 3060 Laptop GPU</device_name>
            <vendor_unique_id>0</vendor_unique_id>
        </preferred_decoder_0>
        <preferred_decoder_1>
            <vendor_id>3</vendor_id>
            <vendor_name>UVD/VCN</vendor_name>
            <device_name>AMD Radeon(TM) Graphics</device_name>
            <vendor_unique_id>327680</vendor_unique_id>
        </preferred_decoder_1>
    </hardware_decoders>
</hardware_detection>
 

Hey @James-Segwell, Did you find your solution to this issue.

Hey @James-Segwell, Did you find your solution to this issue.

He there, No luck. I've given up on Vegas, in Magix hands. The Sony days never gave me these kind of problems. I've tried just about all other video editors, and all of them worked perfectly. The problem with Vegas Pro is that the core has never been rectified, so the bugs will continue.

Well to be honest, if it was up to Sony, there would currently be no Vegas Pro right now. They were choking & killing off Vegas..... Magix actually has saved Vegas Pro and made it far better and stronger as it is now. And actually, the core is currently being rectified gradually right now.

Anyway back to the matter at hand.... Since you have an extreme situation, i am gonna provide you with an extreme solution that will work..... Do you currently have a copy of Vegas Pro 19, and does it work perfectly on your system?

Well to be honest, if it was up to Sony, there would currently be no Vegas Pro right now. They were choking & killing off Vegas..... Magix actually has saved Vegas Pro and made it far better and stronger as it is now. And actually, the core is currently being rectified gradually right now.

Anyway back to he matter at hand.... Since you have an extreme situation, i am gonna provide you with an extreme solution that will work..... Do you currently have a copy of Vegas Pro 19, and does it work perfectly on your system?

Good to know Magic is working on it. For the positives, Vegas has been my main all time favourite, due to its common sense editing, and easy of use.

Since my first post, I've used 5 different Vegas versions. I have 1 copy each of Windows 10, and 11, but leave 11 for special occasions, since I prefer 10 for the bulk of my work. The Vegas version I have now is 21, though it has the same 'render as' crashing problem. Otherwise it works fine.

I can install v19 to test your solution, so please advise how to proceed.

Thank you

Well then, this solution will work for both 21 and 22, until we find what's on your system that's causing this conflict.

Install your copy of Vegas 19, then go into its installation folder in the Program Files directory for example: (C:\Program Files\VEGAS\VEGAS Pro 19.0), and look for the .dll file name RenderAsDialog. Copy and paste this file to your desktop... Now what you gonna do is paste this file inside the Vegas 21 or 22 installation folder, replacing the one that is already there.

Great, thanks for that. I'll give it a try. Will it work in reverse also (RenderAsDialog) from 21 or 22 to 19?

No it wont. You may run into the same issue.

No it wont. You may run into the same issue.

Ok, I tried your suggestion. Same problem am afraid. I may give it a try in Windows 11, and see what happens.

Otherwise, I'll have to wait until Magix fixes the bugs.

Then something on your system is seriously causing this conflict with Vegas Pro....wow.

Then something on your system is seriously causing this conflict with Vegas Pro....wow.

If all other editors I tried, work flawlessly, then the culprit is Vegas. I now have Vegas 22 (the latest version), which has the same problem.

I recently watched a 3-year-old YouTube video, on yet another 'fix'. Well, the fix worked for me, so far. In Vegas folder, there is another folder called 'x86'. The fix was to delete it. I just cut and pasted it to another part of my drive for backup, in case things went wrong.

Hope it would help someone with the same problem, whether the fix is temporary or permanent.

@Xectis, I looked and saw that "x86" folder, and it's still there. I am rendering any time that I choose.

Strange that removing that file works. But as long as it does, go for it!

X86 folder contains shared plugins and help files, so these are likely to be broken if folder removed. Maybe there is an issue with the shared plugins causing render problems.

No...

I think you are thinking about the program files (x86) folder.

The x86 folder that is being referred to here contains the FileIOSurrogate utility, which is used to handle older 32 bit file i/o plugins...for most users, this is executed when the user has activated the QuickTime plugin. This is why we have deprecated it in VEGAS as it often causes all sort of havoc right now, though some people still want to turn it on to use to decode some media.

Based on the above, try making sure QuickTime is unchecked in Vegas Deprecated prefs. If everything is good after doing that, also consider removing it from Windows Apps if you see the old win7-era QuickTime 7 installed.

Perhaps it's time x86 becomes a museum piece.

Perhaps it's time x86 becomes a museum piece.

Yes except that a 64 bit QuickTime windows codec was never developed by Apple.