- Server 2008R2 “Microsoft .NET Framework 4.7.2”
- Server 2012 = KB4054542
- Server 2012R2 = KB4054566
- Server 2016 = KB4054590
Another potential. However:
Scrolling some more, PieterPretorius came up with the following discovery. KB4338814!! This one had been installed the day I did the updates, and promptly uninstalled it. Head to Control Panel, Programs and Feature and click “View installed Updates” and find KB4338814. This took a little time to remove, and after a reboot the NUC had settled down back to near silent! I’ll be writing another post about keeping an Intel NUC NUC7i7DNHE quiet, as the default Fan settings are a bit… noisy. Follow Up: Keeping KB4338814 at bay. The next day I ran some more updates on the server and noticed that KB4338814 was coming back again! I had not tried to block updates on Server 2016 yet so had a look into it, as the usual methods I’d used in the past weren’t present. Head to: https://support.microsoft.com/en-us/kb/3073930 and download the wushowhide.diagcab file and run it.
his is how I limited Microsoft.Online.Reporting.MonitoringAgent.Startup from eating all the CPUs
Task Manager and right click on the Microsoft.Online.Reporting.MonitoringAgent.Startup process.
Select “Go to details”
Right click on Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe (should be the pre-selected row)
Click set affinity, and uncheck “all Processors”
Select CPU 0
Your CPU usage will drop immediately (mine dropped to 32%)
I can’t tell you if this is a good idea or not, nor do I know what complications or adverse affects in restricting it to CPU 0. So far I haven’t had any further issues. Restarting may revert the setting (not sure).
Hopefully Microsoft will release a update soon.
Awesome thanks for taking the time to post this! That should so a similar thing to removing it so it shouldn’t be a problem.