Failing to launch. Crashes on splash screen. Version 15.0 (Build 416)

MFX wrote on 11/3/2019, 4:00 PM

Trying to launch Vegas Pro.

I have just reinstalled it to see if that resolves it, but has happened again.

Crashes almost immedieately on Vega Pro splash screen Vegas Pro Build 416
Creating file I/O manager.
Have run with admin privileges.

Extra Information

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 15.0 (Build 416)

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 15.0\vegas150.exe
   Process Version:     Version 15.0 (Build 416)
   Process Description: VEGAS Pro
   Process Image Date:  2018-11-19 (Mon Nov 19) 21:28:04

My system I am sure is fine, so need some help pinpointing it.

Run Cubase 10.0.5, Reason, Maschine and others fine.

System is as follows:

INTEL 7820X 4.6GHZ. 32gb Ram NvMe 1GB, SSD array

RME Fireface 800, Maschine and various outboard.

Windows 10Pro [1809] Build 17763.805

I cannot seem to locate any config files, so unclear what I can do to resolve this.

 

Thanks in advance

Mark

 

Comments

MFX wrote on 11/3/2019, 4:01 PM

Incidentally, how do I contact support to raise a ticket? ALl the links take me to a deadend with FAQ options with no details!?

How to reach MAGIX

Technical inquiries concerning your VEGAS product

Support:
Internet - https://support2.magix.com/customer/vegas

vkmast wrote on 11/3/2019, 4:41 PM

If you use the link you mention and proceed you'll see the text "My problem is not solved here". Clicking that you'll get this more direct link https://support2.magix.com/customer/en/vegas/form .

MFX wrote on 11/4/2019, 10:19 AM

Thank you both, Ill have a look through the troubleshooting.
Simply loaded to try and do some video for parents as a christmas gift, but honestly If its going to be troublesome may go down demo route of alternative software options. Only paid £20 for it on the hmblebumble deal and doing some beta testing for 3rd party developers (dont read into that not initiated yet).

But I noticed that some have reported issues with various win builds and sony software. So if its going to be all time consuming, then Ill simply bin the software. I really dont know why it shouldnt work when all the other software does cubase, wavelab, reason, etc.