Home Dashboard Directory Help

Problem with uninstall .Net Framework 4.0 by a__pRZEMEK


 as External Help for as External

Sign in
to vote
Type: Bug
ID: 478238
Opened: 7/29/2009 9:39:49 AM
Access Restriction: Public
User(s) can reproduce this bug


I had strange problem with uninstall and ran repair mode .Net Framework 4.0 when I upgrade Windows Vista to SP2. When I tried uninstall .Net Framework 4.0 I always get error "Program Microsoft Common Language Runtime native compiler has stopped working". And I must click on Cancel button.
I tried used removal tool to fix .NET Framework, but this tool removed only .Net Framework 3.5 SP1. I can not installed once again .Net Framework 4.0 and 3.5 SP1, because I got always error during installation.
VS 2010 was uninstalled successfully.

I can not ran any applications for .Net platform, and another applications because msvcr100.dll file is missing. I had to must reinstall OS!!!
I uninstall .Net Framework 4.0 without any problems in the Windows Vista SP1.

I attached a screen shot and installation log.
Sign in to post a comment.
Posted by forefrontwithSP on 11/3/2009 at 10:40 AM
thanks for your post, you just saved me from flattening my box.
Posted by John J. Hughes II on 10/31/2009 at 10:25 AM
Note you have to click the close button a zillion times !
Posted by breed001 on 10/30/2009 at 12:00 PM
thank you for the fix
Posted by breed001 on 10/30/2009 at 11:59 AM
I can not ran any applications for .Net platform, and another applications because msvcr100.dll file is missing.
Posted by Microsoft on 8/3/2009 at 2:20 PM

Please allow .NET Framework 4 setup uninstall continue to finish by clicking on “close program” when you see the crash dialog. Then, reinstall .NET Framework 4 Beta 1. It looks like C Runtime 10 was removed from your machine and the reinstall will fix up your machine. In Beta 2, .NET Framework will not depend on the C Runtime 10 setup, and therefore will not have the same issue.

.NET Framework deployment team
Posted by Microsoft on 7/31/2009 at 1:46 AM
Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.