Aaron Stebner's WebLog

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

.NET Framework Repair Tool now supports diagnosing and repairing .NET Framework 2.0, 3.0 and 3.5 setup issues

.NET Framework Repair Tool now supports diagnosing and repairing .NET Framework 2.0, 3.0 and 3.5 setup issues

Rate This
  • Comments 20

A little while ago, I posted an introduction to a new .NET Framework Repair Tool that can be used to diagnose and repair .NET Framework 4 setup issues.  An updated version of the repair tool has been released today to add support for diagnosing and repairing issues with .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 setup.  The repair tool can identify and fix issues with the installation of MSI-based versions of the .NET Framework, but it cannot fix issues related to versions of the .NET Framework that are installed as a part of Windows.

If you run into installation issues with the MSI-based versions of the .NET Framework 2.0 SP2, 3.0 SP2, 3.5 SP1 or 4, I strongly encourage you to download the .NET Framework Repair Tool and run it to see if it resolves your issue before resorting to trying the .NET Framework cleanup tool. Here are links that you can use to find additional information about the .NET Framework Repair Tool:

  • Hi Jim - The exception message you describe sounds like a problem with the application as opposed to a problem with the .NET Framework, but I'm not positive.  Are the other HP applications .NET Framework applications too, and do they show any error messages when you try to run them?  There are a couple of other .NET Framework applications that come as a part of Windows that you can try to see if you can narrow this down further - Windows Media Center and MMC.  If those work, then the problem is likely application-specific and you might want to try contacting the application manufacturer to see if they have any known issues related to that exception message.

  • Thanks for taking the time to answer. The HP applications don't show any error. The dialog just says "The application has stopped working, Windows is searching for a solution ...". Before the SQL problem, all HP applications worked. I've uninstalled and re-installed the applications and they still don't work. Windows Media Center and MMC both work. When using "Turn Windows features on or off" and adding either of the Windows Communication Foundation sets listed under .NET 3.5.1, Windows errors with "An error has occurred. Not all features were successfully changed.". Thanks again.

  • Hi Jim - There might be entries in the application event log on your computer that give more information about the HP application crashes.

    You don't need to add that Windows Communication Foundation component in order to use the .NET Framework.  However, you also shouldn't be seeing errors like that if you try to add it either.  Here are some steps I usually recommend to solve that type of Windows feature install problem:

    1.  Install the latest Windows service pack if you haven't yet.

    2.  Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.

    3.  Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.

    If none of the above help, you might need to repair/re-install Windows to fix this type of error.  It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.

  • Please Help Me! While I Downloading The Microsoft Net.framework 2.0 sp2 it's says windows vista was not meet the requirments but im using Windows 7 and all requirments are meet why it's says that please Help me Aaron Stebner's ? :(

  • Hi Rand - It sounds like your computer is applying settings from Windows Vista compatibility mode before it tries to run the .NET Framework 2.0 SP2 installer.  To work around that, you should be able to do one of the following:

    1.  Delete the registry values described at blogs.msdn.com/.../10064318.aspx.  That post is about a different installer, but you should be able to modify the steps as appropriate for the .NET Framework installer.

    -or-

    2.  Save the .NET Framework installer to your computer, rename it, and run it with the new name.

Page 2 of 2 (20 items) 12
Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post