We have been using vs 2010 for years on this machine, (server 2003) and now visual studio just started crashing on startup. there is no way to run it at all, it just crash
I had this very issue after being forced to reinstall Visual Studio 2010 to get BizTalk 2010 ESB working.
I was unable to download KB2581206 as it appears to have no valid content any more. However there is an alternative download which also does the job...
http://www.microsoft.com/en-us/download/details.aspx?id=29082
...which is the Visual Studio 2010 SP1 Team Foundation Server Compatibility GDR.
I had the same problem.
I reinstalled Visual Studio SP1 and uninstalled Net Framework all language packs. After that problem was solved.
It looks like the problem was a windows update that was incompatible with the Team Foundation Server 2010 Power Tools that were installed. When I installed the latest version of the power tools, VS stopped crashing.
http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f
I had removed all of that, but i guess.. who knows...
I uninstall Power Tool (didn't work) I install latest Power Tool (didn't work) I uninstall TFS (it start working) then I install TFS again (It still working :))
Thanks and by the way detail off error message in windows event log was:
Fault bucket 3292093736, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0
Problem signature: P1: devenv.exe P2: 10.0.30319.1 P3: 4ba1fab3 P4: Microsoft.TeamFoundation.Common P5: 10.0.0.0 P6: 502e379e P7: 4b6 P8: 45 P9: System.MissingMethodException P10:
Attached files:
These files may be available here: C:\Users\rahiljm\AppData\Local\Microsoft\Windows\WER\ReportArchive\Critical_devenv.exe_1e501d4117b8b2664a23a63826807fb1d894270_1b9a7992
Analysis symbol: Rechecking for solution: 0 Report Id: f92dcd0f-91aa-11e2-8682-8c89a571d971 Report Status: 0
Following worked for me
Close all instances of VS
go to [System Drive]:\Users[User Name]\AppData\Roaming\Microsoft\VisualStudio\10.0
delete all the files and folders from the above folder.
and reopen the VS and everything should be back to normal.