There are times when the .NET Framework can get corrupted on a computer. There are a number of reasons why one should repair the .NET Framework but the simplest of them is the fact that it is corrupt.
To repair .NET Framework 3.5 refer to the instructions below. It is suggested that you log into the problem computer to repair. This way you can get some good feedback on whether the repair actually worked.
Please note this has only been tested on Windows 7 and Windows Server 2008 R2.
.NET Framework 3.5 SP1 is included in these two OSs and cannot be installed, repaired or uninstalled via the .NET Framework setup file. They need to be enabled or disabled as Windows Features. In Windows 7 and Windows Server 2008 R2 disabling .NET 3.5 SP1 is the same thing as uninstalling it or removing it.
Note: Neither of the above actually worked for me so I had to repair it from the command line prompt.
Open cmd.exe in an Elevated session (needed if UAC is implemented) by going to Start and typing in cmd in the 'Search Programs and files' box and then right-clicking and choosing 'Run as Administrator'.
The next step is to disable the .NET 3 Windows Feature.
Run the following command at your command line:
(note that when using DISM all Feature Names are Case Sensitive. Using "netfx3" will result in a failure)
After you successfully disable the NetFx3 feature you can now re-enable it. Re-enabling is the same thing as Installing.
The screenshot below shows the results of both commands run in sequence.
To repair .NET Framework 3.5 refer to the instructions below. It is suggested that you log into the problem computer to repair. This way you can get some good feedback on whether the repair actually worked.
Please note this has only been tested on Windows 7 and Windows Server 2008 R2.
.NET Framework 3.5 SP1 is included in these two OSs and cannot be installed, repaired or uninstalled via the .NET Framework setup file. They need to be enabled or disabled as Windows Features. In Windows 7 and Windows Server 2008 R2 disabling .NET 3.5 SP1 is the same thing as uninstalling it or removing it.
Note: Neither of the above actually worked for me so I had to repair it from the command line prompt.
Open cmd.exe in an Elevated session (needed if UAC is implemented) by going to Start and typing in cmd in the 'Search Programs and files' box and then right-clicking and choosing 'Run as Administrator'.
The next step is to disable the .NET 3 Windows Feature.
Run the following command at your command line:
DISM /online /disable-feature /FeatureName:NetFx3(note that when using DISM all Feature Names are Case Sensitive. Using "netfx3" will result in a failure)
After you successfully disable the NetFx3 feature you can now re-enable it. Re-enabling is the same thing as Installing.
DISM /online /enable-feature /FeatureName:NetFx3The screenshot below shows the results of both commands run in sequence.
No comments:
Post a Comment