.NET Framework 3.5 Installation validation tool

  • Article

If you want to detect if your .NET Framework 3.5 installation was successful, you can use this tool to verify that the right versions are installed.

Instructions:

1. Download the following file to your computer: https://cid-e7f319723234fb5c.skydrive.live.com/self.aspx/Public/netfx35tools/NetFx35_detect_issues.bat

2. Open a command prompt by doing start -> run and type cmd.

3. enter the full path to where the script runs.

What is happening:

This script will check the registry for the right versions of the .NET Framework 3.5, .NET Framework 3.0 SP1 & .NET Framework 2.0 SP1.  they are not there then it will return what it did find and let you know that an error happened.

Further on Vista, it will tell you if you have appropriately installed .NET Framework 2.0 SP1 & 3.0 SP1.

 Return codes:

0 == Success

>0 == Failure

Comments

  • Anonymous
    November 30, 2007
    One of my colleages, Aaron Ruckman , has created and posted a tool that can be used to verify the installation
  • Anonymous
    November 30, 2007
    One of my colleages, Aaron Ruckman , has created and posted a tool that can be used to verify the installation
  • Anonymous
    December 04, 2007
    We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying issue
  • Anonymous
    December 04, 2007
    We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying
  • Anonymous
    December 04, 2007
    We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying issue
  • Anonymous
    December 04, 2007
    Visual Studio 2008 Installation Validation Tool I don't know how many of you have started to work
  • Anonymous
    December 10, 2007
    Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx Step
  • Anonymous
    December 10, 2007
    Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx
  • Anonymous
    March 08, 2008
    I recently upgraded from Windows 2003 to Windows 2008. Note keyword was upgraded. Other than having to
  • Anonymous
    June 08, 2008
    A couple of days ago I reinstalled VS 2008 RTM version and I happily tried to create a website. Unfortunately,
  • Anonymous
    August 20, 2008
    Looks like a useful tool, BUT:  could you please post it in a zip file?Some unfortunate souls (like me) are sitting behind corporate web filters that block batch files, script files, exes, etc.  
  • Anonymous
    March 06, 2009
    The comment has been removed
  • Anonymous
    March 06, 2009
    Forgot to mention that Windows Update is enabled, and states I'm all up to date.
  • Anonymous
    August 05, 2009
    Please note that this tool in its current release does not support detecting NetFx3.5 SP1
  • Anonymous
    January 28, 2010
    Hi Aaron,Thanks for this!  I wasn't quite sure what the output meant (included for your reference below) but it gave me the hint to download & repair my .net framework 3.5 sp1 installation.  I still get the same response as below from your tool (as you mentioned above that's not supported yet), but the problem that prompted me to run this tool in the first place is now solved.THE FOLLOWING SCRIPT will check to make sure that .NET Framework 3.5is installed properly and will tell you what is not configured appropriatelyWINDOWS VERSION: 6.0.6001POTENTIAL ERROR: REGISTRYDUMP: reg query "HKLMSOFTWAREMicrosoftNET Framework SetupNDPv2.0.50727" /v "SP"HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv2.0.50727   SP    REG_DWORD    0x2ERROR: NetFx2.0 SP1 is not installedPOTENTIAL ERROR: REGISTRYDUMP: reg query "HKLMSOFTWAREMicrosoftNET Framework SetupNDPv3.0" /v "SP"HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv3.0   SP    REG_DWORD    0x2ERROR: Netfx3.0 SP1 is not installed
  • Anonymous
    July 23, 2010
    Useless on Vista Ultimate SP2. The monitor window closes automatically before you have a chance to read the results of running the .bat file, and it writes no log.
  • Anonymous
    December 08, 2010
    Hey Bill,Open the command prompt before locating and running the batch and your window will stay open.'You must walk before you can run'