Microsoft and DiscountASP.NET news

Technical Evangelist: Mark Wisecarver

If VS2010 ends up hosing Vista. . .

It happens to the best of us, right?

OK, OK, I should be using VM for things like this but I admit that I was so excited to test VS2010 that I jumped right on the Web install from Microsoft.
At first everything was fine.
I use two Vista SP2 systems, Ultimate for my Webcasts and Expression Studio plus VS2008 and SQL Server 2008. . .
Thing is...I tested VS2010 on my Vista Home Premium machine. . .Which I actually like a lot more than the Ultimate system, especially the way the UAC works, better.

Yes as you can tell by the title above things did start going haywire, possibly because I test just about everything Microsoft sends me. ;-)
All of a sudden everything in my Office 2007 apps started bombing out with .NET erorrs, including Outlook Pro 2007. (My poor RSS feeds.)

At the same time I got an offer from Microsoft to beta test Microsoft Security Essentials. (Which I love so far.)
Once installed I was getting the same .NET errors. . .
MSVCR100.dll was not found
\v4.0.20506\mscoreei.dll could not be loaded

Most of the time these were recursive error dialogs and you could not escape them, you know, Cancel, Close, Cancel, Close...Grrrr

So I should have Repaired the .NET framework, right? I did, multiple times, or at least tried. The Repair and Uninstall functions would all rollback.
Look at the logs, right? Yup, and Oh my gosh! I could fall asleep reading those logs. :-)

What I did was uninstall VS2010 and reinstall it. Errors gone. Office apps back, MSE working.

Then this morning I see the very helpful post pasted below by Stephen Boots, in the Microsoft Social forums:

To remove a corrupt .Net Framework install, use this tool: http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip

The download of .Net Framework 2.0 can be found here:

http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en

 

To repair .Net Framework 2.0 and 3.0 on Vista, see this blog entry:

http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx

 

Note that after repairing or reinstalling .Net Framework, you will need to reapply the .Net Framework 3.5 SP1 update via Windows Update.

 


Wow. . .This is one of those times when we really need tips like that. ;-)
  All the best,
    Mark
   http://twitter.com/msftwise

Comments

If VS2010 ends up hosing Vista. . . - Microsoft and DiscountASP.NET news said:

Pingback from  If VS2010 ends up hosing Vista. . . - Microsoft and DiscountASP.NET news

# June 26, 2009 11:25 AM

If VS2010 ends up hosing Vista. . . | Nexo IT - Information Technology News said:

Pingback from  If VS2010 ends up hosing Vista. . . | Nexo IT - Information Technology News

# June 26, 2009 7:28 PM

CT Yeung said:

From the articles you suggested as well as others and personally testing, .NET framework 2 and 3 are part of the OS and can't be removed with the cleantool.  The only option is re-install Vista 64.

I have attempted to re-install .NET framework 2 without success.

Do you have an alternative suggestion ?  

# July 19, 2009 12:59 AM

mysorian said:

Your links are all unreachable or broken. Where do you find v4.0.20506?

# August 6, 2009 10:08 AM

Jasee said:

This happened to me too.  Basically, VS2010 Beta doesn't uninstall completely and gracefully, leaving .net 4.0 beta as the default .net framework to use.  I'm going to try reinstalling .net.

# August 20, 2009 12:23 PM

Jasee said:

My experience may be different, but didn't think to look for .Net 4 in "Add/Remove Programs".  There's a main .Net 4 Beta and a .Net 4 Extender Beta instance.  Uninstall these and restart and all is good! Good luck.

# August 20, 2009 1:26 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)