Nothing’s perfect, and such is the case for Microsoft’s monthly updates. Each month, Microsoft delivers security updates for its products, and some come with known gotchas. The ‘unknown’ gotchas come later after customers start installing and testing the updates.
So far, here’s what we know to watch out for this month…
August 14, 2018—KB4343900 (Monthly Rollup)
Applies to: Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1
There is an issue with Windows and third-party software that is related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working.
- To locate the network device, launch devmgmt.msc; it may appear under Other Devices.
- To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
a. 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.
August 14, 2018—KB4343897 (OS Build 16299.611)
Applies to: Windows 10, version 1709
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. – Microsoft is working on a resolution and will provide an update in an upcoming release.
When Device Guard is enabled, some non-English platforms may display the following strings in English instead of the localized language:
- “Cannot use ‘&’ or ‘.’ operators to invoke a module scope command across language boundaries.”
- “‘Script’ resource from ‘PSDesiredStateConfiguration’ module is not supported when Device Guard is enabled. Please use ‘Script’ resource published by PSDscResources module from PowerShell Gallery.”
Microsoft is working on a resolution and will provide an update in an upcoming release.
Both Exchange updates come with the same bug…
When you try to manually install this security update in “normal mode” (not running the update as an administrator) and by double-clicking the update file (.msp), some files are not correctly updated. When this issue occurs, you do not receive an error message or any indication that the security update is not correctly installed. Also, Outlook Web Access (OWA) and the Exchange Control Panel (ECP) may stop working. This issue occurs on servers that are using user account control (UAC).
The issue occurs because the security update does not correctly stop certain Exchange-related services. To avoid this issue, run the security update in elevated mode, as an administrator. To do this, right-click the update file, and then click Run as administrator.
This issue does not occur when you install the update from Microsoft Update.
Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!