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 ...
Updated Jul 01, 2019
Version 2.0
Blog Post
I have implemented the registry block, but when I go into Windows Update on Server 2016, it still shows up as available. Please advise on this situation. Will it just fail when I go to install the rest of the Windows Updates? Will it disappear the next time the server checks for Windows updates?
On a side note, I find this situation very disturbing. This already occurred with .net framework 4.6 and now on 4.7. Not every organization uses WSUS for their servers. Server 16 makes it very hard to control individual updates without it and unfortunately, due to the lack of support for Server 16/Win10 on WSUS versions running on Server 2008R2, I have clients that have WSUS, but do not have the capability to properly update Server16/WIN10 until I can get a server in place that can run WSUS 4.
Microsoft needs to do a better job here....I forgot, they don't really care about anybody that is not on Office 365....
update....just made the registry mod on Server 2012R2 and after an additional update check, it disappears. I guess I just have to wait for it to disappear on the Server 16 box...