.NET Framework Setup
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error ...
Question:
I am getting error .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7C812A5B) (800703e9) while starting Visual Studio 2005 IDE. It is only showing splash screen when I start the IDE and logging the error message in event log. I have reinstalled the .Net Runtime and VS 2005 but problem is still continuing. I am not able to use VS 2005. Can any one provide some help?
Answer1:
I'm getting this error too.
Uninstalling and re-installing Visual Studio 2005 did not work.
Repairing the .NET 2.0 framework did not work.
Has there been a "live update" to the .net 2 framework in the last couple of days?
Answer2:
Fixed it.
You need to uninstall the .NET Framework 2.0 security hot"fix" 922770.
Answer3:
I have this error too but couldn't found this update.... Is there other solution?
Answer4:
Hi,
I had the same issue after installing VS.Net 2005 SP1 Beta.
I saw in some other newsgroups that if you remove Windows Workflow Foundation VS.Net will work again.
May you check out if you have installed WWF on your System...
For me it helped to remove WWF!
best regards,
Johannes
Answer5:
Thanks Johannes. I got it working after installing WWF and VS components for WWF.
Answer6:
Hi,
I had the same problem on a Win XP, IE 6, Virtual Machine with Visual Studio 2005 SP1, CMS Server 2002 and SQL Server 2005 and Windows Workflow foundation.
As previously noted, repairing .NET 2 framework failed, and re-installing the Vis Studio 2005 SP1 also failed.
Removing Windows Workflow foundation worked for me.
regards
Stephano
Answer7:
Same problem here. Win XP Pro/SP2, IE7, .NET Frameworks 1.1 and 2.0 installed, MS Visual Studio 2005 (no SP1 installed), MS SQL Server 2005 and Visual Studio 2005 Extensions for Windows Workflow Foundation installed.
Reinstall of .NET Framework 2.0 did not help, but removal of Visual Studio 2005 Extensions for Windows Workflow Foundation did the trick. It seems like latest security updates somehow interfered with these Extensions and IDE could not load them. I suspect latest security updates have mistakenly replaced an assembly which is a part of Windows Workflow Foundation Extensions.
Thanks everybody for pointing this out.
Fadil
Answer8: