NET 4.6.1 is installed and again to confirm it's removed when we're done. NET Framework Setup Verification Utility from Microsoft employee Aaron Stebner's WebLog. NET Framework 4.6.1 from reinstalling once we have it removed.īefore we uninstall. Simply download the BlockNetFramework461.reg file on the computer you need to fix and double-click it to configure the Registry. Or if you've got several computers that you need to uninstall it from, use the REG file I created that does it for you. I'm documenting the process here for others who find themselves in the same predicament.īegin by following the article, How to temporarily block the installation of the. So now I was faced with uninstalling the NET Framework 4.6.1 which, as it turns out, is not exactly a trivial thing. My lab computers are all configured to install updates automatically, so two of my four Exchange servers had already installed the update before I realized what was happening. NET Framework 4.6.1 as an important update to all computers. That article was posted Februthe day after Microsoft pushed. NET Framework 4.6.1 from installing via Windows Update.

The Exchange team even posted a handy article about it with a link to a TechNet page that explains how to temporarily block. Later, the Skype for Business Team followed suit in their own article.

NET Framework 4.6.1 on any of your Exchange servers because it's not supported. You've probably heard by now NOT to install the Microsoft. NET Framework 4.6.1, for the steps required to install and support this. Please see my article, Exchange 2016 CU2 and Exchange 2013 CU13 now supports.

UPDATE: Exchange Server 2013 CU13 and Exchange Server 2016 CU2 now support.

Dotnetfx cleanup tool windows 7