Uninstall VS2010 Beta 2 Ultimate

Self build / N/A
July 19, 2010 at 13:08:55
Specs: Vista SP1, 3.0Ghz,2Ghz
I installed Visual Studio 2010 Beta 2 Ultimate on my laptop. I noticed the laptop slowed down right after that. Today I received an error message from IE 8 regarding VS2010 Beta. The error was: an unhandled Win 32 exception occured in iexplore.exe [3476]. Possible debuggers: New instance of MS VS2010. The laptop only has 512mb of memory and sometimes locks up frequently. What is the best way to go about uninstalling VS2010 Beta 2 Ultimate and the .NET framework 4? I've heard that things must be uninstalled in a certain sequence or you may experience problems. Thanks.

See More: Uninstall VS2010 Beta 2 Ultimate

Report •


#1
July 22, 2010 at 13:01:56
The error was: an unhandled Win 32 exception occured in iexplore.exe [3476]. Possible debuggers: New instance of MS VS2010.
All this is saying is IE crashed, and Windows wants to know if you want to start up VS to debug it. If the system is really dragging, and it's not the SQL Server Express VS likes to install, you probably picked up a virus.

What is the best way to go about uninstalling VS2010 Beta 2 Ultimate and the .NET framework 4?
Use this tool.


Report •

#2
July 22, 2010 at 20:24:19
Thanks for the link. Can the tool be used for the beta version also?

Report •

#3
July 23, 2010 at 03:15:27
Donno, let me know how it works for ya.

Report •

Related Solutions

#4
July 23, 2010 at 13:50:43
I found this article online. You can uninstall via Control Panel. VS2010 Ultimate Beta 2 is specifically mentioned. Looks like you don't need the uninstall tool unless you get an unexpected error.

Report •

#5
July 23, 2010 at 13:51:43
This is the link to the above mentioned article: http://www.kodyaz.com/articles/unin...

Report •

#6
August 15, 2010 at 18:42:36
VS2010 uninstalled with no issues using the direction of the above article. SQL Server 2008 was another story. Turns out there was a bad registry entry. After the bad entry was removed, SQL Server 2008 uninstalled with no problems.
The bad registry entry was in this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager

Report •


Ask Question