.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:

• .NET Framework setup verification tool user’s guide – https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/
• .NET Framework cleanup tool user’s guide – https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/
• Sample code to detect .NET Framework install state and service pack level – https://blogs.msdn.microsoft.com/astebner/2009/06/16/sample-code-to-detect-net-framework-install-state-and-service-pack-level/

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

• Anonymous
  November 26, 2017
  Thanks.....
• Anonymous
  December 14, 2017
  I KEEP GETTING ACCESS DENIED - I AM STUMPED. PLEASE HELP!
  • Anonymous
    December 14, 2017
    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?
• Anonymous
  December 18, 2017
  thank you for NET Framework 4.7.1
• Anonymous
  April 11, 2018
  hi Aarron,thank you very much for the updateHowever, 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?regards,Dominik
  • Anonymous
    April 11, 2018
    The comment has been removed
    • Anonymous
      April 12, 2018
      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.4.0.0.0.141b42a.0: 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.
      • Anonymous
        April 16, 2018
        The comment has been removed