7/23 UpdateMicrosoft released new patches/updates to fix the issues in the current month patch release. The fixes appears to be working and safe to install. It is important to note that while Exchange server issue is resolved with the updated patches, the Azure ADConnect service issue is still not fixed (listed below in known issues) . Here is the link with details for exchange patch issue:

https://blogs.technet.microsoft.com/exchange/2018/07/16/issue-with-july-updates-for-windows-on-an-exchange-server/

Update: There were number of issues reported in this month cumulative/roll up patches. Microsoft pulled then re-released a number of patches. We recommend delaying patch installation until Monday July 23rd.

 

All patches are approved as per our patch testing procedure.

 

Impacted Products:

 

Please note the following information regarding the security updates:

 

Microsoft Security Advisories:

          https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180017

          https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002

          https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8289

 

Known Issues:

KB4338825, KB4338818

 

KB4338825 Applies to: Windows 10, version 1709

https://support.microsoft.com/en-us/help/4338825/windows-10-update-kb4338825

Symptoms: Some non-English platforms may display the following string in English instead of the localized language: “Reading scheduled jobs from file is not supported in this language mode.” This error appears when you try to read the scheduled jobs you’ve created and Device Guard is enabled.

Resolution: Microsoft is working on a resolution and will provide an update in an upcoming release.

Prerequisite: The servicing stack update (SSU) (KB4339420) must be installed before installing the latest cumulative update (LCU) (KB4338825). The LCU will not be reported as applicable until the SSU is installed.

 

KB4338818 Applies to: Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1

https://support.microsoft.com/en-us/help/4338818/windows-7-update-kb4338818

Symptoms: There is an issue with Windows and third-party software related to a missing file (oem<number>.inf). After you apply this update, the network interface controller will stop working.

Workaround:

  1. To locate the network device, launch devmgmt.msc; it may appear under Other Devices.
  2. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu

Alternatively, install the drivers for the network device by right-clicking the device and selecting Update. Then select Search automatically for updated driver software or Browse my computer for driver software.

 

How to Fix microsoft.online.reporting.monitoringagent.startup High CPU

After installing the latest cumulative Windows Update patch, some people are experiencing high CPU issues being used by the “Azure AD Connect Health Sync Monitor” (microsoft.online.reporting.monitoringagent.startup) (AzureADConnectHealthSyncMonitor) version 1.1.819.0.

If you have the Azure AD Connect utility installed on a server, this is a service that goes along with it. According to Microsoft, they will be releasing an update to the Azure AD Connect Utility to resolve this issue, but there is no ETA yet for this update. There are two options you have to temporarily resolve the high CPU issues. The first option is to stop the Azure AD Connect Health Sync Monitor service and set it to manual until the updated utility is released. The second option is to remove the latest patches you installed on the server.