Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
There was a .NET Framework Repair Tool posted on the Microsoft Download Center earlier this summer, and I wanted to post a link here to hopefully make it easier for people to find.
I have seen this new tool successfully identify and fix .NET Framework 4 installation issues that have previously required using more invasive means to solve. Unlike the .NET Framework cleanup tool available via my blog, this new tool performs targeted diagnostics and makes fixes for specific setup issues instead of resorting to forcibly removing the .NET Framework and requiring the user to re-install it.
If you run into a .NET Framework 4 installation issue, 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:
<update date="9/8/2012"> Added a link to the knowledge base article for the .NET Framework Repair Tool. </update>
Great post indeed. I really like that you are providing information on .NET for freshers , Being enrolled at www.wiziq.com/.../57-fresher-training-projects i found your information very helpful indeed. Thanks for it.
It appears that the in place update of net framework 4.5 of Windows 7 is leaving some miscellaneous .net Framework 4.0 about. Any way to clean these files up?
Hi Njmcft - The .NET Framework 4.5 is essentially just a service pack for the .NET Framework 4, which means it needs the files that were originally in the .NET Framework 4 for backwards compatiblity reasons. What are the specific files that you're worried about in this scenario?
Is the repair tool compatible with Windows 8.0, 8.1 or is all of this left up to System Update Readiness Tool (DISM) now? I am not having any problems that I am presently aware of, just getting my ducks in a row ..... or should that be tools :D
Hi Phantom of the Mobile - This repair tool only works for redistributable versions of the .NET Framework. That means it won't work on Windows 8 or 8.1 because the .NET Framework 2.0, 3.0, 3.5 and 4.5 are all included as a part of the OS on Windows 8 and 8.1 (because the redistributable versions cannot be installed when the .NET Framework is included as an OS component). You will need to use the System Update Readiness Tool / DISM to repair the .NET Framework on Windows 8 and 8.1 as a result.
Aaron, can you provide some more specifics about how to use DISM to repair .NET on a 8.1/2012 R2 installation? Is it enough to run "Dism /Online /Cleanup-Image /RestoreHealth"? Or do I need to do
DISM /online /disable-feature /FeatureName:NetFx3 [or :NetFx4?]
DISM /online /enable-feature /FeatureName:NetFx3 /all /Source:X:\sources\sxs /LimitAccess
I recently had a 2012 R2 server become unmanageable because all .NET apps (including Server Manager) were crashing. The next morning, it was working again. So I'm trying to to figure out what was wrong, how it fixed itself, and how I can speed that up next time. Any logs I should be reviewing?
Hi mcbsys - I don't have much expertise using DISM to repair .NET Framework OS components. The manual steps that I typically recommend involve disabling and re-enabling the feature in the Windows Features control panel, so I would lean towards your second set of command lines. That isn't much more than an educated guess on my part though, so I'd recommend that you post a question on the .NET Framework setup forums at social.msdn.microsoft.com/.../home to see if someone there has more in-depth experience with DISM repair scenarios.