Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

How to uninstall the components of the .NET Framework 3.5 SP1

How to uninstall the components of the .NET Framework 3.5 SP1

  • Comments 41

Question:

As described in this blog post, I have been evaluating the beta of the .NET Framework 3.5 SP1 and Visual Studio 2008 SP1.  I ran into some issues running my application on a system with this software installed, so I need to uninstall it.  I have tried to uninstall the .NET Framework 3.5 SP1, but all of the .NET Framework 2.0 assemblies are still at the SP2 level and are not rolled back.  How can I fully uninstall the .NET Framework 3.5 SP1?

Answer:

The .NET Framework 3.5 SP1 is a slipstream replacement for the original release of the .NET Framework 3.5.  It installs the .NET Framework 2.0 SP2 and the .NET Framework 3.0 SP2 behind the scenes, and 2.0 SP2 and 3.0 SP2 are both slipstream replacements of previous versions of the .NET Framework 2.0 and 3.0.

In order to fully uninstall the .NET Framework 3.5 SP1 and return to the .NET Framework 3.5, .NET Framework 2.0 SP1 and .NET Framework 3.0 SP1, you must use the following steps.  Note that there are different steps on Windows Vista and Windows Server 2008 than on earlier versions of Windows because the .NET Framework 2.0 and 3.0 are OS components on Windows Vista and Windows Server 2008.

How to uninstall the .NET Framework 3.5 SP1 on Windows XP and Windows Server 2003:

  1. Go to the Add/Remove Programs control panel
  2. Find the product named Microsoft .NET Framework 3.5 SP1 and uninstall it
  3. Find the product named Microsoft .NET Framework 3.0 SP2 and uninstall it
  4. Find the product named Microsoft .NET Framework 2.0 SP2 and uninstall it
  5. Re-install the original release of the .NET Framework 3.5 (which will re-install the .NET Framework 2.0 SP1 and the .NET Framework 3.0 SP1 behind the scenes)

How to uninstall the .NET Framework 3.5 SP1 on Windows Vista and Windows Server 2008:

Note - these steps are not required if you had a beta version of the .NET Framework 3.5 SP1 and plan to upgrade to the final release.  Behind the scenes, the .NET Framework 2.0 SP2 and .NET Framework 3.0 SP2 packages are designed to upgrade older beta versions of the same packages.  These steps are only needed if you are trying to fully remove the .NET Framework 2.0 SP2, .NET Framework 3.0 SP2 and .NET Framework 3.5 SP1 in order to move back to a previous version of the .NET Framework.

  1. Go to the Programs and Features control panel
  2. Find the product named Microsoft .NET Framework 3.5 SP1 and uninstall it
  3. In the Programs and Features control panel, click the link on the left named View Installed Updates
  4. In the list of installed updates, look for an item named Update for Microsoft Windows (KB948610) - this is the .NET Framework 3.0 SP2 OS update package
  5. Right-click on the item and choose Uninstall
  6. In the list of installed updates, look for an item named Update for Microsoft Windows (KB948609) - this is the .NET Framework 2.0 SP2 OS update package
  7. Right-click on the item and choose Uninstall
  8. Reboot
  9. Re-install the original release of the .NET Framework 3.5 (which will re-install the .NET Framework 2.0 SP1 and the .NET Framework 3.0 SP1 behind the scenes)

<update date="8/7/2008"> Added a note clarifying that these uninstall steps are not needed when moving from a beta to the final release.  They are only needed when doing a full uninstall in order to move back to a previous version of the .NET Framework on a system. </update>

 

  • Disinstallare il Service Pack 1 del .NET Framework 3.5

  • Very good article. That's just what I needed after hours of research. Thank you Aaron ;)

  • I am using Windows Server 2008, I ran into some issues when upgrading to 3.5 sp1 (see the url). I tried to uninstall 2.0 sp2 just like you described, but in 2008 the "Update for Microsoft Windows (KB948610)" and "Update for Microsoft Windows (KB948609)" are not in my updates list. Is there a way to manually uninstall 2.0 sp1?

    Thanks Benedikt

  • Hi Benedikt - The .NET Framework 2.0 SP1 and 3.0 SP1 are part of the OS on Windows Server 2008 and you cannot remove them.  However, you do not need to remove them in order to install the .NET Framework 3.5 SP1.  It is somewhat confusing because the .NET Framework 3.5 SP1 log file states that it is trying to install the .NET Framework 2.0 SP1, but it is actually trying to install .NET 2.0 SP2.  The name used in the log file was not changed between the .NET Framework 3.5 and 3.5 SP1.

    For this error code 1, I typically need to look at the following log files:

    %temp%\dd_dotnetfx35install.txt

    %windir%\logs\cbs\cbs.log

    Could you please zip those logs, upload them to a file server somewhere, and post a link to where you uploaded them so we can take a further look?

  • You may have a need to uninstall .NET Framework 3.5 SP1, perhaps for testing purposes or because you

  • Hi all - For anyone reading this in the future, we figured out that the cause of Benedikt's issue was that the install was being run on a checked (debug) build of Windows, and that is not supported for the .NET Framework 3.5 in this case.  I've posted more information about this particular scenario at http://blogs.msdn.com/astebner/archive/2008/08/25/8895729.aspx in case anyone runs into something similar in the future.

  • PingBack from http://www.activoinc.com/blog/2008/10/06/ektron-cms400-70-issues-with-net-framework-35-sp1/

  • PingBack from http://wickedw.wordpress.com/2008/12/02/visual-studio-2008-sp-and-net-framework-35-sp1-has-not-installed-but-says-it-has/

  • Ok, so you have spent your life doing this and read a copy of an anonymous person's sfc cbs.log output before bed each night...

    I can't understand anything but I do recognize that there are words in there, so I'm guessing it's readable.  It's only a tiny bit more (expletive) up-ed than the bcd stores, which are easier to understand in the registry than in the command line, though you still have to tape three pages together and make a map for inheritances.

    I think C++ has invaded the programmer's heads at MS so completely that they have to re-remember the 7-day intro to OOD&P to get cash out of an ATM.  (That was it for me...  I had better luck with Laplace transforms)

    Seriously, though, there is a huge wealth of information inside Vista 6/7 that I will never get to or understand and I've been a computer geek since age 12.  (Tandy 1000, cassette loaded).

    Someone just show me where I can find the wait states for threads in the assembler code runtime output so I can find the bottlenecks in my computer.  So far, after 30 years, it seems it's still the bus.

    Anyway, I'll just send you my 12.5MB tome and you can find the *one* line that's important.  You send me your 401K investments and I'll change them all around for you and only use Adam Smith's 3 necessities.  They seem simple, but...

    Shawn Harvey / sparkinark

    sparkinark@yahoo.com

    Oh, btw, love Vista 7 so far and can't run anything that uses a C++ runtime, like all my games.  Didn't want to use all that power on the two over-priced graphics cards anyway.

  • Hi Sparkinark - The cbs.log file is very long and verbose, so it can be tricky to locate the exact problems if you run into OS update installation issues.  I don't have a ton of experience myself, but I pick up tricks here and there as I investigate issues.  If you'd like me to take a look at your log, please post it to a file server somewhere and reply with a link so I can download it.  Also, please describe the exact problem you're running into in more detail so I'll have a better idea of what to look for in the cbs.log.

  • PingBack from http://merill.net/2009/02/microsoft-net-framework-35-sp1-breaks-microsoft-ccf-customer-care-framework/

  • The Issue: In the last few months, we have seen quite a few cases where after installing .net framework

  • The Issue: In the last few months, we have seen quite a few cases where after installing .net framework

  • The Issue: In the last few months, we have seen quite a few cases where after installing .net framework

  • Do you want to un-install the components of the .Net Framework 3.5 SP1? Then you need to read this article

Page 1 of 3 (41 items) 123
Leave a Comment
  • Please add 4 and 7 and type the answer here:
  • Post