Update 6/15/2017: Added a clarification that .Net Framework 4.7 has shipped and that we are still validating this release with Exchange Server.

We wanted to post a quick note to call out that our friends in .NET have released the .NET Framework 4.7 to Windows Update for client and server operating systems it supports. We are in the process of validating Exchange Server on the .NET Framework 4.7, but the work is not yet complete. We will be sure to release additional information and update the Exchange supportability matrix when .NET Framework 4.7 is supported with Exchange Server. We are working with the .NET team to ensure that Exchange customers have a smooth transition to .NET Framework 4.7, but in the meantime, please delay this particular .NET update on your Exchange servers. Information on how this block can be accomplished can be found in article 4024204, How to temporarily block the installation of the .NET Framework 4.7.

It’s too late, I installed it. What do I do now?

If .NET Framework 4.7 was already installed, we recommend you back to .NET Framework 4.6.2 Here are the steps:

Note: These instructions assume you are running the latest Exchange 2016 Cumulative Update or the latest Exchange 2013 Cumulative Update as well as .NET Framework 4.6.2 prior to the upgrade to .NET Framework 4.7 at the time this article was drafted. If you were running a version of .NET Framework other than 4.6.2 or an older version of Exchange prior to the upgrade of .NET Framework 4.7, then please refer to the Exchange Supportability Matrix to validate what version of .NET Framework you need to roll back to and update the steps below accordingly. This may mean using different offline/web installers or looking for different names in Windows Update based on the version of .NET Framework you are attempting to roll back to if it is something other than .NET Framework 4.6.2.

1. If the server has already updated to .NET Framework 4.7 and has not rebooted yet, then reboot now to allow the installation to complete. 2. Stop all running services related to Exchange.  You can run the following cmdlet from Exchange Management Shell to accomplish this:

(Test-ServiceHealth).ServicesRunning | %{Stop-Service $_ -Force}

3. Depending on your operating system you may be looking for slightly different package names to uninstall .NET Framework 4.7.  Uninstall the appropriate update.  Reboot when prompted.
  • On Windows 7 SP1 / Windows Server 2008 R2 SP1, you will see the Microsoft .NET Framework 4.7 as an installed product under Programs and Features in Control Panel.
  • On Windows Server 2012 you can find this as Update for Microsoft Windows (KB3186505) under Installed Updates in Control Panel.
  • On Windows 8.1 / Windows Server 2012 R2 you can find this as Update for Microsoft Windows (KB3186539) under Installed Updates in Control Panel.
  • On Windows 10 Anniversary Update and Windows Server 2016 you can find this as Update for Microsoft Windows (KB3186568) under Installed Updates in Control Panel.
4. After rebooting check the version of the .NET Framework and verify that it is again showing version 4.6.2.  You may use this method to determine what version of .NET Framework is installed on a machine. If it shows a version prior to 4.6.2 go to Windows Update, check for updates, and install .NET Framework 4.6.2.  If .NET Framework 4.6.2 is no longer being offered via Windows Update, then you may need to use the Offline Installer or the Web Installer. Reboot when prompted.  If the machine does show .NET Framework 4.6.2 proceed to step 5. 5. After confirming .NET Framework 4.6.2 is again installed, stop Exchange services using the command from step 2.  Then, run a repair of .NET 4.6.2 by downloading the offline installer, running setup, and choosing the repair option.  Reboot when setup is complete. 6. Apply any security updates specifically for .NET 4.6.2 by going to Windows update, checking for updates, and installing any security updates found.  Reboot after installation. 7. After reboot verify that the .NET Framework version is 4.6.2 and that all security updates are installed. 8. Follow the steps here to block future automatic installations of .NET Framework 4.7: The Exchange Team
Not applicable
what backup SW do you use ? (windows backup, acronis, backup exec, veeam,... ?)
Not applicable
It is stupid that server would update to 4.7 when exchange is not compatible. exchange/.net teams need to talk.
Not applicable
What about Windows 10 Creators Update? Are we able to remove .net 4.7 from it without an OS rollback?
Not applicable
I only drink milk cold. Net 4.7
Not applicable
you made me chuckle lol
Not applicable
Unbelievable that this still happens, don't the teams within MS talk to each other? What bothers me also is that no one of the Exchange team responses to the numerous complaint about this issue. They just seem to ignore it.
Not applicable
I was hit this issue. I installed .NET 4.7 on W2012 R2 with Exchange 2013 before I want to install the CU16. The servers booting for 30 minutes, then the services don't want to start. No desktop, no network, just TaskManager to run everything. Really awful. Bad boys.
Not applicable

Indeed, i have detected a problem with Exchange Server 2016 and .Net Framework 4.7. When the server reboot, Exchange Services will not start automatically. I start the services manually. The problem also occurs on the CU6 version of Exchange.

Not applicable
At risk of sounding completely ignorant (which I am in these matters), I haven't got an effin clue what any of this is about.

It usually goes like: I get a "recommended/important" update then have a helluva time trying to find out what it's about or for or what It'll do and why I need it (If, indeed, I actually do) and then just leave it or, as is usually the case, install the thing and hope for the best not knowing what to look out for to notice or gauge any improvemants or differences.

Not applicable
do you have a rough estimate as to when you will have 4.7 on the support matrix?
Not applicable
this got installed on 2 Exch 2016 servers. Since this has happened, unable to log in to ECP, powersehll does not connect. So can not get in to change any config.

mail still flows

have removes .net 4.7 but still the same

Lots of asp.net errors relating

Exception message: Could not load file or assembly 'Microsoft.Exchange.Security, Version=, Culture=neutral, PublicKeyToken=NUMBER REMOVED' or one of its dependencies. The system cannot find the file specified. (C:\Windows\System32\RpcProxy\web.config line 38)

Not applicable
After installing this update my emails take about 30 seconds to load, and I have archived my emails.

Still same issue, is anybody else having the same issue?

Not applicable
.net framework 4.6.2 offline or webinstaller doesn't have a repair option. Only displays that the feature is already installed and then stops. I just thrashed a clients exchange-server due to MS's lack of internal communication and my own lack of time to look for caveats.
Not applicable
Good news amidst all the doom and gloom on here.

I have a client that is still running Windows 2008 R2 and Exchange 2010 SP3, both fully updated and .NET Framework 4.7 applied.

Everything seems to be fine. No problems have been reported, OWA still works and no errors in the the Event Viewer have occurred as a result of the 4.7 installation.

Perhaps MS merely made that statement out of an abundance of caution.

Not applicable
Like wise my Exch2010 SP3 environment is fine, and they all have .net 4.7.

But my Exch 2016 environment is screwed

Not applicable
This is probably because Exchange 2010 doesn't use .Net 4. It uses 3.5. So, it shouldn't be impacted by the installation of 4.7 as nothing it uses gets changed by the update.

I checked this article and 2010 is not specifically mentioned. These days Exchange 2010 is an outcast. It doesn't even get mentioned in posts about new patch releases. I think the team is counting down the days until support officially expires.

Not applicable
Is there any update on this? I have not installed 4.7 on our 2008R2/Exchange 2010 servers. Last week, update rollup 18 for Exchange Server came out and the install froze installing through WSUS. An attempt to download and install the update exhibited the same issues. Today, I see KB4032116 which is a quality rollup for the .Net framework including 4.7. Needless to say, I am a bit paranoid about approving the newest updates until this issue is resolved or I need to go back and add an Exchange update to my project plan for this year. Anyone have a clue as to where this issue sits now?
Not applicable

I currently run in project to install a new Exchange 2013 servers for across forest migration old one run CU 10, Can I upgrade .net 4.6.2 on a new server and jump directly to CU17 or do I have to do the install CU15, install new .NET 4.6.2 and then CU17? Trying to figure out the best course before install my Exchange this weekend.


Not applicable
Everyone here thinks MS is stupid, or has a "go to h- -l" attitude, but doesn't seem to appreciate their marketing strategy. See, if they release updates that foul up your computer, the likelihood that you will pay for their support services increases.
Not applicable
Not applicable
Is there any connection to having Microsoft net framework 4.7 and being unable to

Connect to the internet on my computer. Modem is working on ipad.

Not applicable
Well thank you MS for killing my server.

I've done exactly like advised above. Stopped the services, removed .NET 4.7 (and later on 4.6.2). Reinstalled 4.6.2 with all updates (btw. there is no repair mode!). While the .NET verification tool returnes that everything is fine:

[08/23/17,11:24:58] Install state for .NET Framework 1.0: not installed.

[08/23/17,11:24:58] Install state for .NET Framework 1.1: not installed.

[08/23/17,11:24:58] Install state for .NET Framework 2.0: not installed.

[08/23/17,11:24:58] Install state for .NET Framework 3.0: not installed.

[08/23/17,11:24:58] Install state for .NET Framework 3.5: not installed.

[08/23/17,11:24:58] Install state for .NET Framework 4 Client: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4 Full: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.5: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.5.1: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.5.2: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.6: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.6.1: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.6.2: installed with no service packs.

[08/23/17,11:24:58] Install state for .NET Framework 4.7: not installed.


08/23/17,11:25:04] Section [Registry - .NET Framework 4.5 (Wow6432Node)] - stop parsing entries

[08/23/17,11:25:04] Processing custom action 'Custom Action - .NET Framework 4.0 test application'

[08/23/17,11:25:04] ExecutablePath = 'Netfx40TestApplication.exe'

[08/23/17,11:25:04] FriendlyName = '.NET Framework 4 test application'

[08/23/17,11:25:04] TimeoutSeconds = '300'

[08/23/17,11:25:04] WaitOnExit = 'true'

[08/23/17,11:25:04] Silent = 'true'

[08/23/17,11:25:04] Launching process 'Netfx40TestApplication.exe' now

[08/23/17,11:25:04] Process successfully launched. Waiting 300 seconds for it to complete.

[08/23/17,11:25:04] Process 'Netfx40TestApplication.exe' exited with return code 0

[08/23/17,11:25:04] Verification succeeded for product .NET Framework 4.6.2

and .NET 4.6.2 is installed the CU6 setup.exe still insists that there is no .NET on the system:

C:\temp\Exchange 2016 CU6>setup.exe /PrepareSchema /IAcceptExchangeServerLicense


Für Exchange Server 2016 ist .NET Framework 4.5 oder höher erforderlich. Laden S

ie die Software von "http://go.microsoft.com/fwlink/?LinkId=260991" herunter.

Thank you very much.

Not applicable
Can we PLEASE get an update on this situation? June is so so long ago, surely by now the Exchange team has gotten their act together?
Not applicable
When .NET Framework 4.7 will be supported?

Please let us know

Not applicable
i am trying to install Autocad software, but it is showing need to install .net framework 4.5, but i am already having 4.7 and not able to edit client value to 4.5 in regedit. Pls help to edit the client value.


Not applicable
I can no longer open MAIL, Calendar or People APPS since the down load of this update; KB3186539. I now have all the indications of a damaged hard drive. The scan will not work. I cant restore to an earlier date. I cant uninstall this update. I thought Microsoft was so much better than this professionally. Lorna Gemmell, ldoone@cox.net for my father, Allan Gemmell.
Not applicable
I see an update to this post 6/15/2017 and mentions they are still testing it. Does anyone know if this has been officially approved by the Exchange Team yet?
Not applicable
I have Windows 2012R2 and KB3186539 is not showing up in installed updates. Has it been superseded?
Not applicable
I do not have it on mine either. I know it was installed on my 2012R2 server as well.
Not applicable
FYI - there's no repair option on server 2016 with the offline installer
Not applicable
Hello, I uninstalled .NET 4.7 and repaired .NET 4.6.2 using /repair option from command line. Unfortunately System.xml.dll did not revert to 4.6 version still 4.7.2102.0. Exchange UM services does not start anymore and refer to this dll. Can one help ? Thanks in advance
Not applicable
As Cumulative Update 7 for Microsoft Exchange Server 2016 was released on September 19, 2017, is .NET Framework 4.7 supported already?
Not applicable
In our Environment pushing this update KB3186539 caused SCVMM console to crash. System Center Virtual Machine Manager crashes when some features of the console are used for example, VM properties etc.

Previously KB4040972 caused the same issue and now this .NET update.

But we have to remove these to updates to continue working with VMM console.

Thank you.

Not applicable
We've installed .net 4.7 yesterday. Since then external Mails bounced with message:

"<<< 530 5.7.1 Client was not authenticated

554 5.0.0 Service unavailable"

Our Version: Exchange 2013 CU18

Not applicable
Hi there guys. Is there any development on this issue? Last update is over three month ago. I see there has not been any change on the supportability matrix ( https://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx ) either.
Not applicable
Guys, these are exe files. Ever thought about triing /? ;)

Just use "NDP462-KB3151800-x86-x64-AllOS-ENU /repair" and it will do this job even on Server 2016...

Not applicable
Microsoft Stated they are skipping support for 4.7 in exchange 2013 or 2016. They will support 4.7.1 in the December Quarterly Update.