Redundant Installations?

JayGee 181 Reputation points
2021-03-05T15:35:56.653+00:00

This is probably a simple question.
I noticed there seem to be older versions of the same installation associated with Visual Studio, on my system.
74893-ms.jpg
Microsoft Help Viewer 1.1 Microsoft Corporation 3/27/2018
Microsoft Help Viewer 2.0 Microsoft Corporation 3/27/2018
Microsoft Help Viewer 2.1 Microsoft Corporation 3/27/2018
Microsoft Help Viewer 2.2 Microsoft Corporation 3/27/2018

I'm wondering if I can safely remove them, and keep the latest, or would that be a problem for earlier versions of Visual Studio, such as VS2010?

What's the difference between Microsoft .NET Framework 4.5.1 Multi-Targeting Pack (ENU), and Microsoft .NET Framework 4.5.1 Multi-Targeting Pack?

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,624 questions
0 comments No comments
{count} votes

Accepted answer
  1. Michael Taylor 48,576 Reputation points
    2021-03-05T16:28:54.07+00:00

    You cannot remove major versions of the C++ runtime as any app that relies on that major version will fail but you could remove older patch versions. So in your case 12.0.40660 needs to stay but the other 12.0.* versions could be removed. Just be careful to leave both the x64 and x86 versions.

    For .NET Framework the SDKs can be removed but the targeting packs need to stay. If you remove the SDK then you are likely to break the VS workload as well. SDKs are not backward compatible as they are simply a series of tools. Many apps that rely on SDK features use a path that includes the version of the SDK. Removing the SDK will break that. I would recommend that you use the VS installer to try and remove any SDKs that are installed that you don't want. If a workload relies on it then the installer will not let you remove it.

    The targeting pack is what allows you to select that framework in VS. If you removed, say 4.6 then you would not be able to select it as a framework anymore. The fact that the runtime is the same is not relevant here. As with the SDKs I'd use the VS installer to try and remove any frameworks that you don't support anymore. However some will be required by workloads so if you remove them they may fail in VS.

    For the Help Viewer 1.x and 2.x are different beasts so you need both. Personally I would leave them all.

    The difference between Targeting Pack and Targeting Pack ENU is discussed here. The targeting pack allows you to target the framework in VS. The language pack contains the culture-specific resources for that version of the framework. You need both.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. WoodBurking 1 Reputation point
    2021-03-05T16:29:30.73+00:00

    @JayGee

    From what I can tell, the ENU stands for Error Notification Utility, (Edit: this is incorrect. My Bad!).

    I would caution against removal of any .NET framework, as if the older programs require it, it could cause improper initialization, and along with this possibly cause data loss.

    Often times, programs that I deal with not only require 4.5, but also 4.1 and even back to 3.5, so there are most likely specific aspects of specific framework versions that are needed.

    Granted, if the program needs a certain version of the .NET, it will trigger a download of the needed component at the next launch.

    Hope this helps!

    0 comments No comments

  2. JayGee 181 Reputation points
    2021-03-05T17:37:34.44+00:00

    Thanks guys. @Michael Taylor that was very helpful. Exactly what I needed to know.

    0 comments No comments