.NET Runtime version 2.0.50727.3603 – Fatal Execution Engine Error (7A036050) (80131506) – mscoree.dll

If you are coming from Google, I’m sure that you are having problems that Visual Studio 2008 keep on crashing without showing any message or error when you are trying to open the resource files, XAML or the properties page of your project.

If you look at Event Viewer, you will see this error message “.NET Runtime version 2.0.50727.3603 – Fatal Execution Engine Error (7A036050) (80131506)

Here is the screenshot that I took when I was having this error.

2. .NET Runtime 2.0.50727.3603 - Fatal Execution Engine Error (7A036050) (80131506)

If you click on Red Icon then you will see the error message in details as below.

3. .NET Runtime 2.0.50727.3603 - Fatal Execution Engine Error (7A036050) (80131506) - Details

How to fix then? Yes. it’s very simple. Microsoft already released the fix for this issue. You can go and download it from this link.  As you can see the screenshot below, there are 6 files for you to download. You can download the required files based on your processor. If you are using x84 then you just need to download NDP20SP2-KB963676-x86.exe  and Windows6.0-KB963676-x86.msu only.

hot fix

You downloaded all files and you should get KB963676 folder that contains all six files that you need.

HotFix Download

Here is the step for installing this fix.

1. Double-click on NDP20SP2-KB963676-x86.exe. You will see the welcome screen below. Please click on “Next” button.

1. NDP20SP2-KB963676-x86 - Welcome

2. Check “I have read and accept the license terms”

2. NDP20SP2-KB963676-x86 - License

3. Please wait for a while while installing.

3. Processing

4. You will see the screen once installation is completed.

4. Finsihed

Then, you can re-open your Visual Studio and try to open the resource files or etc. You should be able to open it without any crash. Good luck!

Note: I’m writing this post for documentation purpose so I added full of pictures and detailed steps. I hope people can use it as a reference whenever they are having the same problem with VS.

33 thoughts on “.NET Runtime version 2.0.50727.3603 – Fatal Execution Engine Error (7A036050) (80131506) – mscoree.dll

  1. Thanks so much! I’ve been having this very issue for a few weeks now and trying to resolve it. Hopefully this will do the trick.

  2. This one has been driving me crazy. It looks like you are running windows XP. However, several of those files look like they are for windows vista. Am I just seeing things?

  3. Michael, I haven’t even finished reading the solution but needed to thank you first for taking the time to share it. Like most developers, I tend to immediately copy and paste an error message into Google. In this case I first (for the first time) clicked the link provided by Microsoft in the event viewer…got a “not found”. Your post was one of the first hits on Google. I’m not saying solving this problem has changed my life :). But I was suddenly struck with appreciation for all the people who share things and make it possible for the rest of us (who don’t have a blog and who don’t take the time to share things) to get an answer with a couple of clicks. Thanks again!

    Rodney

  4. This issue still happens after I installed the fix. Same error in the event log. Any advices would be much appreciated.

  5. Michael, After looking for almost a week on the Symantec BackupExec 12.5 site (and finding NOTHING) I found your guide. Within a couple minutes, I was back in business and backing up my servers!

    THANK YOU THANK YOU! It pained me so much to go home yet again without a backup running. Now I can go home and sleep a good night sleep!

    Cheers to Michael!

    Thanks again…

  6. Really appreciate to you. This issue has been trouble me since last week. Apprently I thought that was due to other new software installation crash on my VS. Refer to some forum discussion, I have uninstall VS2010 Express and it’s component according to their suggestion. But non of them works until I found you. Thanks again.

    Ya, in the mean time I fail to open WPF designer in VS, I try kaxaml for the WPF Window editing. I found it quite useful and very lightweight. Of course it cannot compare to Microsoft Expression Blend but it is free to use :)

  7. The link is not available in the connect page anymore. Any more suggestion ? If anyone has the files plz send the same to my email id,
    sijokurien@hotmail.com
    NDP20SP2-KB963676-x86.exe and
    Windows6.0-KB963676-x86.msu
    This is troubling me a lot.

  8. usually those problems were caused by accessing collection object in multiple threads programs. Try to use Concurrent collection objects in .net 4. good luck.

    Jon

Leave a Reply

Your email address will not be published. Required fields are marked *