Pre-RTM Visual Studio 2005 Automatic Uninstall Tool
It's highly recommended that you install the RTM version of Visual Studio 2005 on a clean machine.
But...but...we realize a lot of people have installed some pre-release version of Visual Studio 2005, and to that end, the setup team has created our "best effort" for uninstalling the product, which is the (also unsupported) Automatic uninstall tool.
A couple of notes on the uninstaller
- Do not use this tool if you have installed SQL Server 2005 Workgroup Edition or higher (SQL Server 2005 Express is okay). Why? Because we don't do ref counting on who is using the Framework and you can get into a situation where the uninstall tool will remove a pre-RTM version of the .NET Framework 2.0, but SQL Server 2005 Workgroup+ will still be installed on the machine. Because Workgroup edition uses managed code, you've now "hosed" your SQL 2005 Workgroup edition uninstall. Check the product readme for step-by-step instructions
- Do not click "Cancel" when the Automatic uninstall tool is running. Depending on when you click Cancel, it can "hose" your machine uninstall
Comments
Anonymous
October 27, 2005
The comment has been removedAnonymous
October 27, 2005
This won't require a reboot, will it? If so, under what circumstances?Anonymous
October 28, 2005
Worked great for me. You don't know how much time it saved me using this tool. Thanks!Anonymous
October 29, 2005
Great tool! Thanks.Anonymous
October 31, 2005
Okay, I saw "workgroup" and didn't see the "+". I had the Developer version installed, which obviously gets broken when you run the uninstall tool. As far as I can tell, the only thing I need to do is re-install the correct 2.0 framework to then uninstall the remaining SQL 2005 bits. It would be helpful if all of the framework pre-release versions were available and then have a table of which version goes with which pre-release version of SQL 2005.
I'm not complaining...just trying to avoid the reformat option if at all possible.Anonymous
October 31, 2005
When I used the Uninstall tool, it did not uninstall MSXML 6.0 (which is listed in the readme as a "must go").
Is that a bug?
BTW: I was uninstalling VS Team RC1.Anonymous
October 31, 2005
The Tools worked fine for me though.
www.thezubair.netAnonymous
October 31, 2005
Sounds scary... hosing anything is never a good idea! I've got SQL Express Edition installed; and would need to migrate the data to the 'real' version. Will this be a problem?Anonymous
November 01, 2005
I have SQL 2005 Dev installed. So should I uninstall this before or after running the uninstall tool?
ThanksAnonymous
November 01, 2005
On my machine, I got an error that said "framedyn.dll is not found" (or similar). It seems someone forgot to bundle a required file with this uninstaller?Anonymous
November 01, 2005
The comment has been removedAnonymous
November 02, 2005
The uninstall tool worked great for me. I rebooted beforehand (just to be sure), ran the tool, it ground away for quite a while, and then completed successfully. After that, the RTM version installed without incident. Thanks!
TabletDev.com - Essential information for Tablet PC developers and users.Anonymous
November 09, 2005
The uninstall tool got refreshed on 11/7 and will be refreshed as more instalation issues will be known.
Please download from: http://go.microsoft.com/fwlink/?LinkID=47598
Before that date at that URL there was available a tool that do clean everything.
The older tool is still available (but not recommended unless you want RTM bits removed): http://go.microsoft.com/fwlink/?LinkID=55128
Krzysztof
MS DevDiv SetupAnonymous
November 09, 2005
The comment has been removedAnonymous
November 10, 2005
Did the error "Suite Integration Toolkit Executable has encountered a problem..." appeared to you?
Its really frustrating I deleted, installed and dis-registred anything about Beta 2 of VS.Net 2k5 and this problem still appears.
please mail to paomeow@hotmail.com for any comments. Thanks.Anonymous
November 11, 2005
Worked like a charm! Thanks a lot.Anonymous
November 12, 2005
Nope. I have one pesky system that (I thought) never had any beta software installed. When I ran the uninstaller It returns "Visual Studio TT UO module has encountered an problem and needs to close. ...
I'm on the cusp of reinstalling windows on this system... but I really don't have a week to waste on the job.Anonymous
November 20, 2005
I used the uninstaller tool after the 11/7 fix. It rendered both Visual Studio 2005 and C# Express betas completely inoperable. All recently coded projects were simultaneously destroyed by loss of cproj readability.
Several (5-6) attempts to reinstall Visual Studio 2005 have been unsuccessful. C# Express also initially failed, but finally it did install. However, the product displays several strange and bothersome behaviors. Help doesn't work--but I can go to the Developer Center. Also, several of the IDE windows work sporadically. There are more such examples.
I did a system restore, but that didn't help. I also tried to revert to Visual Studio 2003, but that install failed also.
This problem has consumed incredible amounts of time, and has virtually killed productivity at a very bad time. IT IS A KILLER.Anonymous
November 20, 2005
I used the uninstaller tool after the 11/7 fix. It rendered both Visual Studio 2005 and C# Express betas completely inoperable. All recently coded projects were simultaneously destroyed by loss of cproj readability.
Several (5-6) attempts to reinstall Visual Studio 2005 have been unsuccessful. C# Express also initially failed, but finally it did install. However, the product displays several strange and bothersome behaviors. Help doesn't work--but I can go to the Developer Center. Also, several of the IDE windows work sporadically. There are more such examples.
I did a system restore, but that didn't help. I also tried to revert to Visual Studio 2003, but that install failed also.
This problem has consumed incredible amounts of time, and has virtually killed productivity at a very bad time. IT IS A KILLER.Anonymous
December 09, 2005
The comment has been removedAnonymous
July 05, 2006
OK .. help! I did hit Cancel on the unistaller .. now it just sits for a LONG time with 0 files .. any way out of this other than wiping the system?Anonymous
September 01, 2006
This doesn't seem to fix the "Suite Integration Toolkit Executable has encountered a problem..." crash. I just got VS 2005 Standard and I can't install it. I ran this tool and it said it couldn't find anything. I reinstalled XP SP2 (as recommended by others), but the VS 2005 installation still crashes. I am desperate. Please help.
johnjbolton@AT@yahoo.DOT.comAnonymous
September 16, 2006
This Tool Is Awesome! I tried to uninstall the VS2005 Pro and it errored with a message "uninstaller could not find a logical folder order! uninstall will now exit." One click on this tool and the problem vanished. Thank You for a GREAT job. I will be forwarding this URL to the Tech departments of all the institutions I have dealings with.Anonymous
January 08, 2007
Suite Integration Toolkit Executable has encountered a problem and needs to closeAnonymous
January 15, 2007
아직 VS2005/SQL2005 한글버젼이 나오지는 않았지만... .NET Framework 2.0은 여기 서 여기 서 받을 수 있습니다! (VS2005와 SQL2005 영문버젼은Anonymous
October 15, 2007
OK, the actual and old tools does not run!!! The resulte is the same "a valid destination folder for the install could not be determined" How about remove manually all files? Where I find the relation of this files? please reply to: nalthor@hotmail.comAnonymous
November 15, 2007
PingBack from http://www.devslife.com/2005/10/27/pre-production-vs-2005%e3%82%a2%e3%83%b3%e3%82%a4%e3%83%b3%e3%82%b9%e3%83%88%e3%83%bc%e3%83%ab%e3%83%84%e3%83%bc%e3%83%ab/Anonymous
November 16, 2007
The comment has been removedAnonymous
November 17, 2007
PingBack from http://www.devslife.com/?p=682Anonymous
May 05, 2008
PingBack from http://graham.infomediaguide.com/serviceexecutablehasencountered.html