.NET Framework setup verification tool and cleanup tool now support .NET Framework 4.5.1


I have posted updated versions of the .NET Framework setup verification tool and the .NET Framework cleanup tool that support verifying and cleaning up the .NET Framework 4.5.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 the .NET Framework setup verification tool or the .NET Framework cleanup tool, please let me know by posting a comment on one of my blog posts.

Comments (6)

  1. John says:

    Is there any plan to support version 4.6

  2. Hi John – I posted updated versions of these tools a couple of weeks ago that support the .NET Framework 4.6.  See the post at blogs.msdn.com/…/10632281.aspx for more details.

  3. sriram says:

    thanks

  4. Matt says:

    Hi Aaron
    I’m not sure if you recall but I contacted you almost a year ago about this kind of issue. I’m still having problems with a .Net debugger app error occurring which occurs after server slowness. Please help if you can :-
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/50a230fd-4a58-4aad-9ad1-1276df696cde/net-runtime-version-20507274253-no-debugger-foundno-registered-jit-debugger-was-specified-on?forum=winservergen

    Also the blog contact form link above doesn’t work anymore :-
    https://blogs.msdn.microsoft.com/astebner/contact/

    Kind Regards
    Matthew

    1. Hi Matt – The error described in that forum post sounds like an application error as opposed to a problem with the .NET Framework itself. I think the event log message you quoted there just means that the application is built with the .NET Framework.

      Your comment about having the .NET Framework 3.5 installed but not the .NET Framework 2.0 is not possible. The .NET Framework 3.5 requires both the .NET Framework 2.0 and 3.0 behind the scenes, and you can’t have 3.5 installed without also having 2.0 and 3.0 installed.

      Thanks for letting me know about the broken contact link. They migrated the MSDN blogs to a new blog host a few months ago, and it looks like they don’t offer direct contact links like that anymore, so I’ve removed the link from this blog post and I’ll remove it from other posts in my archive as I run across them in the future.

Skip to main content