Vegas Pro Edit 16 won't Open

mickhardy wrote on 8/27/2018, 9:03 PM

I have the same issue. The problem details highlight the ignitecore bundle from the Vegas 16 Suite.

C:\Program Files\Common Files\OFX\Plugins\IgniteCore.ofx.bundle

I removed HitFilm Ignite Pro and it now finishes loading the plugins but still crashes before starting at "Initialising DotNet framework...".

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 16.0 (Build 248)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
   Fault Address:       0x00007FF98EC43D4C
   Fault Offset:        0x0000000000073D4C

gamehits wrote on 8/27/2018, 9:17 PM

I too can't launch vegas 16. is there some way to contact tech support without posting on the forum?

mickhardy wrote on 8/27/2018, 9:18 PM

I uninstalled Vegas 16, all the plugins that came with the suite and Microsoft C++ 2013. This was everything that was installed today. I rebooted for good measure. I reinstalled Vegas 16 on it's own and it's starting fine now.

Former user wrote on 8/27/2018, 9:25 PM

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

mickhardy wrote on 8/27/2018, 10:02 PM

After the Vegas installation, I installed each plugin individually and fired up Vegas between each installation. Everything is still working with all the plugins from the suite installed and activated.

I'm guessing Joelson-Forte's solution also works.

The plugins are downloaded to "D:\My Documents\MAGIX Downloads\Installationsmanager" during the suite installation. I didn't install "MAGIX Connect" or "Music Maker" during the initial suite installation nor during the re-installation.

Crazy workaround for a suite of plugins but it's all good now.

AlanH wrote on 8/28/2018, 9:11 AM

Similar problem on my notebook machine, with VP16 stalling on boot, but in my case referring to several plugins in \AppData\Local\VEGAS Pro\16.0\... citing "multiple contexts" (see at bottom of post). So J-F's OFX folder renaming trick doesn't work.

The VP16 installation on my main editing machine works fine (alongside VP15 - I'm not brave enough to de-install that yet).

Is there some weird problem that although my Magix account tells me the VP16 licence allows 2 simultaneous installs (like its predecessors), some of its new internal effects do not?

Note that I don't install any of the separate bundled plugins, as they have generally proved crash-prone, are single install only and have limited functionality.

I have removed and reinstalled VP16 three times with the same result.

Any ideas?

=========

FAULT REPORT TEXT...

   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\dx_video_grovel_x64.log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_video_grovel_x64.log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'com.sonycreativesoftware_Filters.Stereoscopic3DAdjust' (0, Multiple Contexts).log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'com.sonycreativesoftware_Filters.Stereoscopic3DAdjust' (0, Filter).log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'de.magix_Stabilize' (0, Multiple Contexts).log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'de.magix_Stabilize' (0, Filter).log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'com.magix.ofx.panorotation' (0, Multiple Contexts).log
   File:                C:\Users\alan\AppData\Local\VEGAS Pro\16.0\svfx_Ofx1_1_plugin_x64-'com.magix.ofx.panorotation' (0, Filter).log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 16.0 (Build 248)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
   Fault Address:       0x000000100000000D
   Fault Offset:        0x000000100000000D

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
   Process Version:     Version 16.0 (Build 248)
   Process Description: VEGAS Pro
   Process Image Date: 2018-08-15 (Wed Aug 15) 15:59:40

oliverSpain wrote on 8/28/2018, 9:27 AM

I have been the same issue. Thank to Jetdv, in this forum, It was solved when I updated the video driver.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-error--112631/

AlanH wrote on 8/28/2018, 9:48 AM

My video drivers are up to date, according to Windows, so I'm still struggling to understand this problem.

gamehits wrote on 8/28/2018, 10:12 AM

I have been the same issue. Thank to Jetdv, in this forum, It was solved when I updated the video driver.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-error--112631/

I too solved my issue _finally_. uninstalled everything. installed one component at a time. everything works now. strange that following the standard installation procedures would cause it to crash... more beta testing?? [hintidy hint hint]

AlanH wrote on 8/28/2018, 10:22 AM

OK - did something like J-F's scheme and renamed c\Program Files\Vegas Pro 16.0\OFX Video Plug-Ins folder as ..._OLD.

This gets the program running, but I'm obviously missing a load of native plugins. Guess I'll have to selectively rename sub-folders until I identify the specific culprits, then who knows...

My notebook install is just for quick on-site edits that don't generally need a load of sophisticated effcts, but this all seems a bit tedious!

brian-smith wrote on 8/28/2018, 10:22 AM

Found out my install of VP16 was not playing nice with the existing Hitfilm Ignite Pro which was installed already. I uninstalled Ignite pro and it booted just fine. I reinstalled Ignite Pro and so far so good. VP16 boots just fine.

ryclark wrote on 8/28/2018, 10:32 AM

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

Thanks very much. This fix let me start VP16 successfully at last after trying for a couple of days but crashing towards end of launch with the DotNet Framework error. 😁

fr0sty wrote on 8/28/2018, 10:54 AM

Please tag one of the posts as a solution, so that users browsing for answers to this problem will know this thread contains one.

AlanH wrote on 8/28/2018, 10:57 AM

Found that the only culprit was OfxStitch.ofx.bundle

When I moved this to a dummy folder, it all works.

Not sure what fx I'm left missing, but life's too short to pursue it any further.

Cheers and happy editing!

AlanH wrote on 8/28/2018, 11:11 AM

Hi FrOsty - Difficult to tag just one post as a solution as although this thread is headed "Vegas Pro Edit 16 won't open", it results from two problematic plugins with slightly different solutions:

(a) Ignite (Common Files solution by Joelson-Forte)

(c) OfxStitch.ofx.bundle (Program Files solution - sorta - by me)

Alberto-Meyer wrote on 8/28/2018, 11:14 AM

My Vegas 16 crash at start. Renamed the plugins folder, etc. Error: Initializing GPU-Accelerated video processing... I have a GTX 1080 Ti with latest drivers. Any help, please?

Caylyn wrote on 8/28/2018, 4:33 PM

I have tried all the "fixes" in this thread and I still can't open Vegas Pro 16 Suite. Everything still works fine on Vegas 15 Pro Suite. The error I get is: "Failed to initialize the common language runtime engine. Please install the .NET Framework (download is available from Windows Update)." I have installed and reinstalled the .net framework along with all of the Vegas Suite programs. I also get errors with my plugins even with the OFX name changed to OFX.OLD. Any suggestions? I've been trying to solve this for two days now. Thanking you in advance...

jozef-pavlik wrote on 8/29/2018, 3:45 PM

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

Thanks very much. This fix let me start VP16 successfully at last after trying for a couple of days but crashing towards end of launch with the DotNet Framework error. 😁

thank you works here

Caylyn wrote on 8/30/2018, 12:50 PM

I have tried everything in this forum to get Vegas Pro 16 Suite to open. I've uninstalled (rebooted, soft and hard boots) and reinstalled everything for days (rebooting between installations). I have renamed the OFX folder following the instructions for that fix, and still Vegas crashes instead of opening. The error I get is: "Failed to initialize the common language runtime engine. Please install the .NET Framework (download is available from Windows Update)." The .NET Framework is installed and has no errors. Has anyone else had this problem? Anyone know of a work around or know of the fix for this? I am at my wits end. Vegas Pro 15 Suite still opens, so I can't figure out why I am getting the error. Any help anyone can give me is appreciated. Thanking you in advance...

Caylyn wrote on 8/30/2018, 1:05 PM

I don't know what has happened or how this was fixed, but it is working now with all original settings. I thought I would let who ever reads this know. If it stops working again, I'll be back. :-)

Ehud_Aha wrote on 8/30/2018, 5:53 PM

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

Thanks very much. This fix let me start VP16 successfully at last after trying for a couple of days but crashing towards end of launch with the DotNet Framework error. 😁

thank you works here

I have the very same problem - this fix doesn't work for me.

Ehud_Aha wrote on 8/30/2018, 5:55 PM

I have the very same problem - this fix doesn't work for me.

James-Swan wrote on 9/10/2018, 2:50 PM

Hey guys, I've been trying everything and I am still having issues with Ignite pro specifically. A few of you are mentioning that the latest version of Ignite Pro fixes the issue however I am downloading my version from:

https://fxhome.com/software-install/ignite-pro

and I am still encountering an immediate crash on startup when reaching creating video plug in factory when ignite pro files are present. If they are deleted/moved then it boots up normally.

Where are you guys getting the download/installer that works? The official one clearly isn't working...

Kinvermark wrote on 9/10/2018, 3:00 PM

Don't know about he ignite problem specifically, but here is the general troubleshooting guide for others that are having startup problems:

https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/