Aaron Stebner's WebLog

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

Mailbag: Do I need still need older versions of the .NET Framework on my system after installing the .NET Framework 4?

Mailbag: Do I need still need older versions of the .NET Framework on my system after installing the .NET Framework 4?

Rate This
  • Comments 27

Note: This is an updated version of a previous mailbag entry that I posted before the .NET Framework 4 shipped.


I recently installed the .NET Framework 4 on my system. Afterwards, I looked in Add/Remove Programs, and it shows that I have all of the following versions of the .NET Framework installed on my system:

  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 2.0 SP2
  • Microsoft .NET Framework 3.0 SP2
  • Microsoft .NET Framework 3.5 SP1
  • Microsoft .NET Framework 4 Client Profile
  • Microsoft .NET Framework 4 Extended

Do I need any of these older versions of the .NET Framework now that I’ve installed the .NET Framework 4, or can I safely uninstall them?


In general, my recommendation is to leave the .NET Framework 2.0 SP2, 3.0 SP2, 3.5 SP1 and 4 installed on your computer.

Unlike previous versions of the .NET Framework, the .NET Framework 4 does not allow an application that was built with previous versions of the .NET Framework to migrate forward and run on it if the previous version is not installed. If you are using any applications that were built with any version of the .NET Framework before version 4, then I recommend leaving both the .NET Framework 3.5 SP1 and the .NET Framework 4 installed.

You cannot use the .NET Framework 3.5 SP1 unless you also have the .NET Framework 2.0 SP2 and 3.0 SP2 installed. Therefore, you will not be allowed to uninstall the .NET Framework 2.0 SP2 or 3.0 SP2 if you have the .NET Framework 3.5 SP1 installed. If you try to uninstall the .NET Framework 2.0 or 3.0 when the .NET Framework 3.5 is installed, their uninstall processes will block and tell you that they are needed by another application on your system.

The .NET Framework 1.0 and .NET Framework 1.1 can be installed side-by-side with the .NET Framework 2.0, 3.0, 3.5 and 4. Most applications that were created for the .NET Framework 1.0 or 1.1 will automatically use the .NET Framework 2.0 instead if it is installed on the system. In most cases, that means you do not need to keep the .NET Framework 1.0 or 1.1 installed on your system if you already have the .NET Framework 2.0 installed.

However, there are some applications that are configured to require a specific version of the .NET Framework, even if later versions of the .NET Framework are installed. If you have any applications like that on your system and try to run them without installing the .NET Framework 1.0 or 1.1, you will get an error message that looks like the following:

MyApplication.exe - .NET Framework Initialization Error
To run this application, you first must install one of the following versions of the .NET Framework:
Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.

In the above error message, the version number will be v1.0.3705 if you need to install the .NET Framework 1.0, and it will be v1.1.4322 if you need to install the .NET Framework 1.1.

If you end up seeing any error messages like this, you can re-install the .NET Framework 1.0 or 1.1 in order to resolve the errors. If you don't end up seeing any error messages like this, then you don't need to worry about re-installing the .NET Framework 1.0 or 1.1.

  • Thank yo for the info it was very helpful. Wish they could do like java and do away with the previous versions.

  • Great answer, Thanks! I wish I didn't need the older versions, though. :(.

  • where did you read that " .NET Framework 4 does not allow an application that was built with previous version"

  • Hi Royi - This behavior is described in the Application Compatibility and Deployment section of the MSDN page at msdn.microsoft.com/.../ms171868.aspx.

  • I agree one would think a step forward in the Net framework would be a step forward not just another bundle of updates and patches and so forth.

    I look at how practically most of the software is filled with Microsoft junk.

    Good system too much baggage.

    Net 4 should be all inclusive in order to do away with the early Packs.

  • Completly agree with the other posters, in that it should be more like Java. It can be a pain trying to manage a system that has all these installations. Add in all the C++ redistributables & the machine I'm looking at now has over 15 instllations just from .net & C++.

  • thanks for these helpful tips...

  • Thank you very much for the informative explanation.  I was almost framed to remove all the pervious .NET Framework.  :)

  • Thank you as well!  I also was going to remove them prior to your information.  Very helpful to me and very much appreciated.

  • Thanks for the very informative answer! I was cleaning up unused programs and stumbled upon the .net frameworks. I was about to delete them. Good thing I didn't.

  • i too had 2.0,3.0,3.5 in my xp with sp3. i downloaded manually 1.0 and left it. but windows update installed the remaining. but i am not a developer. i removed 1.0 but i now understand why i cannot remove the remaining. What type of applications use this framework?

  • Hi Saradhi - You can find more information about what types of applications use the .NET Framework at en.wikipedia.org/.../.NET_Framework.

  • Hi Aaron,

            Came across this thread because having trouble .net 2 hogging CPU. None of the fixes worked. I note you stated that various versions don't replace other, and yet you wikipedia link seems to be saying in most cases they do.

    For non techies this is of course confusing. Could you please clarify.

  • Hi Robert Feal-Martinez - Some of the information about replacing/superseding in the Wikipedia article isn't exactly right.  The .NET Framework 3.5 requires both the .NET Framework 3.0 and 2.0 behind the scenes, and the .NET Framework 3.0 requires the .NET Framework 2.0 behind the scenes, so 3.0 and 3.5 don't supersede 2.0.  Also, the .NET Framework 1.1 is a side-by-side version and doesn't supersede 1.0.

    I'm not sure I understand your CPU hogging problem though.  The .NET Framework is not an application, it is a framework used by applications.  Is there a specific .NET Framework application that is hogging CPU on your computer, or does that happen for all .NET Framework-based applications?

  • Thank you ?+)

Page 1 of 2 (27 items) 12
Leave a Comment
  • Please add 7 and 6 and type the answer here:
  • Post