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.
The .NET Framework setup team has released an updated version of the .NET Framework Repair Tool that adds support for diagnosing and repairing issues with .NET Framework 4.5 and 4.5.1. This repair tool can identify and fix issues with the installation of MSI-based versions of the .NET Framework, but it cannot fix issues related to versions of the .NET Framework that are installed as a part of Windows.
If you run into installation issues with the MSI-based versions of the .NET Framework 2.0 SP2, 3.0 SP2, 3.5 SP1, 4, 4.5 or 4.5.1, 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:
Hey,Your content is just so wonderful regarding the updated version of .NET Framework. I went through your blog when I was searching for .Net Framework in Google.I must say your blog is so mush helpful.
I have used both of these on occasion for years, Thank You for the heads up. I don't need them right now but I am now on W 8.1.1 Pro.
The question is, how will they both work on my current OS? I don't see anything beyond W 7 or W 8.0.
Hi Phantom of the Mobile - The .NET Framework Repair Tool only fixes issues with redistributable versions of the .NET Framework 2.0 SP2 or higher. On Windows 8.1, the only versions of the .NET Framework 2.0 or higher that are possible to install are OS components and you can't install the redistributable versions on Windows 8.1. As a result, there currently isn't any value in running the .NET Framework Repair Tool on Windows 8.1.
I'm on Windows 8.1 Pro (64 bit). I know it doesn't have much to do with the subject, but what should I do (without have to reinstall Windows) if I've accidentally deleted the Microsoft .Net folder from Program Files (x86) and now I can't reinstall .Net 4.5.1 because it says it's already installed as part of the OS, and that I have only to activate it on "Turn on Programs and Features", but when I go there, there isn't any .Net listed but 3.5?
I tried installing both 4.5.1 and 4.5.2 Developer Packs, but in the end it installs only the Multi-Targeting Pack, and not the framework itself for the same reason.
Also, I'm trying to install VS 2013 Ultimate but it says it needs .Net 4.5.1 and then it gives the option to install it, but it ends up with the same error, exactly because it uses the same package. I mean, it's curious that it recognizes .Net 4.5.1 is not there, and not that "it's already part of the system".
I'm starting thinking there is no way of bypassing this assumption from the system, even if .Net 4.5.1 is actually not there and so can't be the later versions, but by reinstalling Windows. But I'm wondering what you think and what advices would you give for me.
Hi Vitor - The .NET Framework 4.5.1 is included as a part of the OS on Windows 8.1, and there isn't a way to install or uninstall it on its own, even via the Programs and Features control panel.
There isn't typically a Microsoft.NET folder in Program Files (x86) - do you mean that you deleted the one in c:\windows? If so, the following steps might help restore it - blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.
Alternatively, if you have another Windows 8.1 computer, you can try to copy the contents of the folder you deleted from the other computer.
After spending 2 days working with Microsoft support, I gave up and found this tool. Thanks a lot. After putting in a lot of work on a Windows 7 upgrade, we couldn’t bill the customer until we fixed this problem. Thanks again.
Is there a repair tool for version 4.5.2? I keep getting the unhandled exception error message every time I try to open my Outlook 2007. I'm using Windows 7. I have run the setupverifier tool which resulted in the following error file:
[05/03/15,16:35:19] Beginning of new SetupVerifier error logging session
[05/03/15,16:35:19] Build created on June 24, 2014
[05/03/15,16:35:19] For more information about repairing the .NET Framework, see support.microsoft.com/.../2698555 and go.microsoft.com/fwlink
[05/03/15,16:35:19] Activity log file location: C:\Users\Jack\AppData\Local\Temp\setupverifier_main_05-03-15_16.35.19.txt
[05/03/15,16:35:19] Error log file location: C:\Users\Jack\AppData\Local\Temp\setupverifier_errors_05-03-15_16.35.19.txt
[05/03/15,16:35:19] Detected operating system: Windows 7 (x64)
[05/03/15,16:35:19] Windows directory: C:\Windows
[05/03/15,16:35:19] System directory: C:\Windows\system32
[05/03/15,16:35:19] Program Files directory: C:\Program Files (x86)
[05/03/15,16:35:19] Common Files directory: C:\Program Files (x86)\Common Files
[05/03/15,16:36:23] SetupVerifier exiting with return value 0
Unfortunately, I have no clue what this file is trying to tell me. Do I need a repair tool? Right now I can't send or receive any messages, so this is pretty urgent.
Thank you for your help!
Hi Jack - It looks like the latest version of the repair tool supports the .NET Framework 4.5.1, not 4.5.2. However, Outlook 2007 was released long before the .NET Framework 4 family shipped, so I don't think that it is very likely that the error you're seeing is related to the .NET Framework 4.5.2. What is the exact error that you see? You might want to post a question on the Microsoft Office forums at answers.microsoft.com/.../office to see if someone there has any suggestions too.