Failed to launch Vegas Pro 11 due to .NET runtime initialization error

Asked By 10 points N/A Posted on -
qa-featured

Hi Experts,

I have been unsuccessfully trying to run the Vegas Pro 11 I installed for about 5 days now. Every effort on my part to troubleshoot this issue has been useless. As soon as I try to open up the application, I get this error message reporting a failure to initialize the .NET runtime. I tried downloading the latest .NET Framework from Microsoft for Vegas Pro and this did not help by cause any further. I am logged in as admin on this windows Vista machine, but I tried right clicking the program shortcut and choosing the Run as Administrator option. Again, I had no luck. Then I tried uninstalling the Vegas Pro and performed a clean boot of my system by running the system configuration utility to disable all Microsoft services. Again I attempt to reinstall the application. Again the installation reports no errors. However, opening Vegas Pro still results in this error. I tried repairing permissions and uninstalling and reinstalling the application a couple of times. I have exhausted all possibilities. Can someone come up with a better idea to solve this problem? I am all ears. Thanks a million to whoever helps me with a fix.

Image:

Error:

An error occurred during the current operation.

The Microsoft .NET runtime could not be initialized

Failed to initialize the common language runtime engine. Please install the .NET Framwork (download is available from windows update)

SHARE
Answered By 10 points N/A #184696

Failed to launch Vegas Pro 11 due to .NET runtime initialization error

qa-featured

The main problem is that you do not have the right .Net framework installed. You need Microsoft .NET Framework 2.0/3.0/3.5 in order to ensure that Vegas Pro 11 successfully run on it. But before doing that ensure the application is closed and if possible open the fresh system with no open application. If the .Net framework is already installed, un-install the same first before making fresh installation. To be on a safe side use .Net framework version 3.5.

Login/Register to Answer

Related Questions