VP14 ".net runtime could not be initialized" on start-up

robinv00 wrote on 10/7/2016, 7:10 AM

Hi,

Shiney new product - awesome. Unfortunately I can't get it to run. Everytime it gets right to the end of it's start-up routine and then craps out with a good old dotnet runtime issue. I'm running Windows 10, dotnet 4.5 is installed. I've looked into installing 3.5 as that used to be the problem in days gone by but i can't figure out how to do it - the usual installers don't seem to work.

I have VP13 running fine and use it every day....

This forum really needs a search function!

Any ideas anyone?

Thanks
Robin

Comments

Musicvid wrote on 10/7/2016, 10:17 AM

Uninstall Vegas, then reinstall and accept the .net version that is packed with the installer. Thatbis the safest method.

robinv00 wrote on 10/10/2016, 3:23 AM

Hi - thanks, I did as you suggested but there is no opportunity to "accept the .net version that is packed with the installer". I'm installing VP14 Suite and i get tick boxes for all the applications - Vegas, DVD, Titler etc but nothing about .net

I've uninstalled and reinstalled and i still get "Failed to initialize the common language runtime engine. Please install the .NET framework (download is available from Windows Update)"

There's no option under Windows update for anything of the sort. My Win10 Pro box is fully updated and dotnet 4.5 is installed and updated. As i said above i can't seem to install dotnet 3.5 but who knows what this is after?

Has anyone else run into this problem?

NickHope wrote on 10/10/2016, 4:50 AM

I have a feeling it needs .NET Framework 4.0. Might very well be wrong though.

robinv00 wrote on 10/10/2016, 5:26 AM

FOUND THE ANSWER! It was something to do with plug-ins - it's always the plug-ins. I renamed my VST plugin folder and it started right up. I was then able to restore the folder and scan for plug-ins within Vegas which worked fine - it rejected a couple of utility plug-ins but didn't crap out or crash. It now starts fine!

Note to self - always rename plug-in folder when you hit problems on start-up. Thanks.