Sharing our knowledge

Michael Sync

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

October 31st, 2009 by Michael Sync

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.

5 Responses

  1. Lee Says:

    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. Michael Sync Says:

    Your welcome! Lee.

    Good luck :)

  3. Bruno Caimar Says:

    Tks for sharing the solution with us. This solution works perfect for me!
    Bye!

  4. Arnoud Lems Says:

    Thanks for posting this, the issue has been bothering me for some time

  5. Rams Says:

    Thank you for the excellent post. Help me greatly

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.