[SOLVED] Vegas pro edit 14 full & 15 Trial will not open, same errors

aidanodr wrote on 12/15/2017, 11:12 AM

Hi Guys,

I have VEGAS PRO EDIT 14 Full ..

I installed Vegas Pro 14 Edit from that bundle on my Win 10 Pro laptop ( Dual card - Intel / Nvidia GT750m ), then launched it AND CRASH. On the Splash screen it loads the plugins on the system, gets so far but then comes up with the crash report screen -

The "Unmanaged Exception (0xc0000005)" error. Fault module is the Vegas EXE itself

I cannot get beyond this.

I also randomly get the "crt not initialized r6030" error.

Whichever one, I cannot even get into VEGAS.

I have tried reinstalls after thorough cleanup, latest NVIDIA Driver, Done the CTRL + Shift thing. All to no avail. I then tried the Vegas Pro Edit 15 TRIAL .. SAME THING here.

So guys, any ideas? Is there anyway of temp bypassing the plugins check during the Vegas Load? HELP!!

 

Comments

aidanodr wrote on 12/15/2017, 12:29 PM

OK .. I have solved not being able to open VEGAS PRO EDIT 14 because of errors arising like:

 

The "Unmanaged Exception (0xc0000005)" error. Fault module is the Vegas EXE itself

OR

I also randomly get the "crt not initialized r6030" error.

 

SORTED IT. Here is how.

1. RENAME your VST folder/s ( i just stuck OLD before the orig name )

2. Now launch VEGAS. It opens no problem.

3. RENAME VST folder/s back to original names

4. Go to OPTIONS / PREFERENCES menu item in Vegas ( Still open as of 2 above )

5. VST EFFECTS tab, RESCAN the plugins ( might get some errors, bypass )

 

Thats it.

set wrote on 12/16/2017, 7:34 AM

Thanks for updating the situation and sharing the solution.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

fathomstory wrote on 1/22/2018, 3:53 PM

I am encountering the same issue with Vegas, but will not rename my VST folders. That is ridiculous. Other programs use those folders. Surely Vegas can post a fixed version of their software. Not very pro.

aidanodr wrote on 1/22/2018, 4:09 PM

I am encountering the same issue with Vegas, but will not rename my VST folders. That is ridiculous. Other programs use those folders. Surely Vegas can post a fixed version of their software. Not very pro.

This is a temporary rename. Literally only rename them for time Vegas is initially opening for 1st time. Then rename them back to what they were a few seconds ago .. Its not a big deal!

 

fathomstory wrote on 1/22/2018, 4:16 PM

Well, if a software program makes you do something bad to make it work, it is telling. I'll just try some other software until Vegas gets this issue resolved. Pity though, I was on the cusp of buying. Glad this happened.

NickHope wrote on 1/22/2018, 10:57 PM

I am encountering the same issue with Vegas, but will not rename my VST folders. That is ridiculous. Other programs use those folders. Surely Vegas can post a fixed version of their software. Not very pro.

@fathomstory The developers are not psychic. Maybe they don't know that your VSTs cause this issue. How about you contribute by finding out which one(s) it is and letting them know so they have a chance to fix it?

fathomstory wrote on 1/23/2018, 2:03 AM

I am all for helping companies debug their software and making it better. However, there are two issues here; the bug will not even let the program start. That is issue one. Issue two is that a fix requires a renaming of key folders that other programs depend on. Even if that is for a few seconds, I find it a troubling and obscure way to fix. A better way is if Vegas provides debugger software to run as Vegas itself runs. For instance, something like this: https://www.gnu.org/software/gdb/

So fixing the problem needs to entail that tenet, "Do no harm."

@Nick Hope, by the way, I just tried the suggested fix and it did not work for me. The program still crashes at launch.