.NET Framework setup verification tool, cleanup tool and detection sample code now support .NET Framework 4.7.1

I have posted updated versions of the .NET Framework setup verification tool, the .NET Framework cleanup tool, and the sample code to detect .NET Framework install states that support detecting, verifying, and cleaning up the .NET Framework 4.7.1. You can find more information about how to download and use these tools at the following locations:

As always, if you run into any issues or have any feedback about these tools or samples, please let me know by posting a comment on one of my blog posts.

Comments (8)

  1. Judy - Phoenix says:


    1. Hi Judy – Phoenix – What exactly are you doing when you see this access denied error?

      If it is happening during .NET Framework setup, then can you please use the tool described at http://blogs.msdn.com/astebner/archive/2007/11/21/6458047.aspx to collect all of your setup log files, upload the file named %temp%\vslogs.zip that this tool will create to a file server (such as http://onedrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?

  2. برامج نت says:

    thank you for NET Framework 4.7.1

  3. D.Ecke says:

    hi Aarron,
    thank you very much for the update
    However, you are still pointing to the .Net Framework Repair tool when it comes to fixing found issues. That Repair tool was not updated since 2016, can only handle .Net up to 4.6.1 and is not compatible to Windows 10 (according to System info on download site)
    Any chance you can clarify what to do on Windows 10?

    1. Hi D.Ecke – The .NET Framework repair tool is only designed to work for versions of the .NET Framework that are installed via redistributable MSIs, not ones that are installed as OS components. I’m not sure why that tool hasn’t been updated since the .NET Framework 4.6.1 shipped though.

      The answer about what to do on Windows 10 depends on what kind of problem you’re seeing. Can you describe the .NET Framework issue you’re seeing in more detail (what exactly you’re trying to do, what error text you see, etc), and I’ll see if I can help further from there?

      1. D.Ecke says:

        Sure can do, thanks for the fast answer! First of all: I’m a client admin / supporter, and one of the things we try to do is write up work instructions for error cases. When it comes to .Net errors that we do not find an “easy” fix for, we would like to be able to tell agents how to try and repair .Net as in reset it, hoping it might reverse any misconfiguration to the defaults, replace wrong or missing files etc.
        — In my current case we have the issue that on some clients PowerShell ISE is showing a .Net error when being closed. The error message is “unknown software exception occured (0xc000000d)” with title “.NET-BroadcastEventWindow. powershell_ise.exe” on a Windows 10 1607 with installed .Net 4.7. As we do not have a proper .Net coder in our support team, we always struggle with stuff like that :). In addition in that case the user requires some application that does not (yet) work with .Net 4.7.1, so we cannot install that on top.

        1. Hi D.Ecke – There isn’t really a way to “reset” the .NET Framework when it is installed as a part of Windows, similar to how there isn’t really a way to “reset” other Windows components. You can use steps like the ones at http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx to repair the files that are a part of your OS.

          The PowerShell ISE error that you describe sounds like an issue with the application itself as opposed to an issue with the .NET Framework. There might be more useful error information and/or a callstack from the crash in the Application event log on that PC.

Skip to main content