Microsoft released security updates for Windows, Office, and other company products on the August 2018 Patch Tuesday (Update Tuesday).
Last month's Patch Day was not the the smoothest of them all as it had issues that affected all supported versions of Windows. Microsoft released three cumulative updates for Windows 10, one designed solely to fix issues caused by another. The Windows 7 and Windows 8.1 updates had bugs, and the .Net Framework patches caused issues on some systems they were installed on.
We recommend to wait with the installation of the updates for at least a couple of days to monitor reports about issues. If you have to install the updates, make sure you back up the system before you do so.
The overview covers updates for client and server versions of Windows, Microsoft Office, and other company products. It links to security advisories and support pages, lists direct downloads, and other information that is important for home users and system administrators alike.
You can download an Excel spreadsheet that contains all security updates that Microsoft released today. Just click on the following link to download it: (Download Removed)
Windows Server products
Other Microsoft Products
KB4343909 -- Windows 10 version 1803
KB4343897 -- Windows 10 version 1709
KB4343885 -- Windows 10 version 1703
KB4343887 -- Windows 10 version 1607 and Server 2016
KB4343898 -- Windows 8.1 Monthly Rollup Update
KB4343888 -- Windows 8.1 Security-only
KB4343900 -- Windows 7 SP1 Monthly Rollup Update
KB4343899 -- Windows 7 SP1 Security-only
KB4343205 -- Cumulative Update for Internet Explorer
KB4338380 -- Windows Server 2008 -- An information disclosure vulnerability exists when the Windows kernel improperly handles objects in memory.
KB4340937 -- Windows Server 2008, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009 -- A remote code execution vulnerability exists in "Microsoft COM for Windows" when it fails to properly handle serialized objects.
KB4340939 -- Windows Server 2008 -- A remote code execution vulnerability exists in Microsoft Windows that could allow remote code execution if a .LNK file is processed.
KB4341832 -- Windows Server 2008 -- L1TF variant vulnerabilities update.
KB4343674 -- Windows Server 2008, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009 -- fixes remote code execution vulnerability and information disclosure vulnerability in GDI.
KB4343902 -- Security update for Adobe Flash Player
KB4344104 -- Windows Server 2008, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009 -- Remote code execution vulnerability in the Windows font library.
KB4344159 -- Security Only Update for .NET Framework 4.0 on WES09 and POSReady 2009
KB4344180 -- Security Only Update for .NET Framework 2.0 on WES09 and POSReady 2009
KB4345590 --Security and Quality Rollup for .NET Framework 3.5.1 on Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2
KB4345591 -- Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded 8 Standard and Windows Server 2012
KB4345592 -- Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2
KB4345593 -- Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008
KB4345679 -- Security Only Update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2
KB4345680 -- Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded 8 Standard and Windows Server 2012
KB4345681 -- Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Windows Server 2012 R2
KB4345682 -- Security Only Update for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008
The following CVEs have FAQs that offer additional information and may also list additional steps required to update.
Windows 10 version 1803
Windows 10 version 1703
Windows 10 version 1709
Windows 7 SP1
Microsoft Exchange Server 2013
ADV180017 -- July 2018 Adobe Flash Security Update
ADV180018 -- Microsoft Guidance to mitigate L1TF variant
ADV180020 -- August 2018 Adobe Flash Security Update
ADV180021 | Microsoft Office Defense in Depth Update
KB4339284 -- Time zone and DST changes in Windows for North Korea
KB4340689 -- Dynamic Update for Windows 10 Version 1709
KB890830 -- Windows Malicious Software Removal Tool - August 2018
KB4346877 -- Update for Windows 10 version 1607 and Server 2016 -- Fixes the .Net Framework update issues introduced by the July 2018 .Net updates.
KB4340917 -- Update for Windows 10 version 1803 -- See our coverage of KB4340917 here.
KB4338817 -- Update for Windows 10 version 1709 -- Lots of bug fixes.
KB4338827 -- Update for Windows 10 version 1703 -- Lots of bug fixes.
KB4338822 -- Update for Windows 10 version 1607 and Server 2016 -- Lots of bug fixes.
KB4345421 -- Update for Windows 10 version 1803 -- See our coverage of KB4345421 here.
KB4345420 -- Update for Windows 10 version 1709 -- attempts to fix issues caused by the July 2018 updates.
KB4345419 -- Update for Windows 10 version 1703 -- attempts to fix issues caused by the July 2018 updates.
KB4345418 -- Update for Windows 10 version 1607 and Server 2016 -- attempts to fix issues caused by the July 2018 updates.
Check out our coverage of all released non-security updates for Office in August 2018 here.
Office 2016
KB4032233 -- Security update for Office 2016 that patches an information disclosure vulnerability.
KB4032235 -- Security update for Outlook 2016 detailed in ADV180021. Includes a number of improvements as well:
KB4032229 -- Security update for Excel 2016 that resolves a remote code execution vulnerability. Also includes improvements:
Office 2013
KB4032239 -- Resolves information disclosure vulnerability. Enables People Picker control in the Office Document Information Panel.
KB4032241 --Resolves various security vulnerabilities in Excel 2013.
KB4032240 -- Fixes security issues in Outlook 2013. Includes the following improvements:
Office 2010
KB3213636 -- Fixes vulnerabilities in Microsoft Office 2010 - CVE-2018-8378.
KB4022198 -- Fixes vulnerabilities in Microsoft Office 2010 - CVE-2018-8378.
KB4032223 -- Excel 2010 update that addresses CVE-2018-8375, CVE-2018-8379 and CVE-2018-8382.
KB4018310 -- PowerPoint 2010 security update that addresses CVE-2018-8376.
KB4032222 -- Outlook 2010 security update. See ADV180021
Other Office products
KB4092433 -- Word Viewer
KB4092434 -- Word Viewer
KB4032213 -- Excel Viewer 2007
KB4032212 -- Microsoft Office Compatibility Pack Service Pack 3
KB4022195 - Microsoft Office Viewers and Office Compatibility Pack
Also: SharePoint Server 2016, 2013 and 2010.
Most home PCs that run Windows use Windows Update for update checks, downloads, and installs. Organizations use Enterprise-specific update tools usually to download and deploy updates.
The Microsoft Update Catalog website offers a third-option to download and install updates.
Windows users who use Windows Update can run manual checks for updates to get updates installed immediately when they are released.
While it is recommended that you wait before you install updates, as updates may break things (and have numerous times in the past), you may do the following to install them when they are available:
Note: We recommend that you create a backup of the system partition and important data before you install Windows updates.
All cumulative updates for supported versions of Windows are also provided as direct downloads from Microsoft's Download Center site.
Just click on the direct links below to do so.
Windows 7 SP1 and Windows Server 2008 R2 SP
Windows 8.1 and Windows Server 2012 R2
Windows 10 and Windows Server 2016 (version 1607)
Windows 10 (version 1703)
Windows 10 (version 1709)
Windows 10 (version 1803)
This last round of updates (Windows 7) has essentially locked me out of any ability to control Windows Update settings. First thing I noticed that happened, was that I could not change update settings. It had changed itself to ‘always automatically download and install’, and I could not change this. Said I didn’t have Administrator privileges, even though I was logged into Admin account.
After deleting AU subkey in RegEdit, I had control again. Or so I thought! Even with Updates turned off, the system will still automatically download and install. So, Windows has now decided to completely bypass any command related to Updates, and it now does as it wants.
Not very impressed. To me, this is a huge problem. More than likely the first of many problems Microsoft will ‘introduce’ to push people away from Windows 7. Wonder what they’ll gimp next?
Just a quick side note re: Intel CPUs firmware. On the Intel site at https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00161.html it mentions that they released a microcode update three days ago on 14 August to address the issue.
I checked with Acer a few minutes ago, but they’re still working on their version of respective firmware and will publish the results on their site a.s.a.p. But you might want to check with your own OEM as to when they’re likely to release a patch.
Hi Martin
it seems the August 2018 updates for Windows 10 versions 1703, 1709 & 1803 do resolve the July 2018 .NET problems.
This note was recently added onto the MS KB articles for the KB4343909, KB4343897 & KB4343885 updates:
-Addresses an issue that was introduced in the July 2018 .NET Framework update. Applications that rely on COM components were failing to load or run correctly because of “access denied,†“class not registered,†or “internal failure occurred for unknown reasons†errors.
M$ is getting pretty cagey designating their KB numbers for .NET Framework updates these days it seems. I went to the Catalog site for the security only updates for Windows 8.1 (x64) and KB4345681 is the appropriate version for my system.
However, I haven’t installed any upgrades beyond 4.5.2 which means I have to separate the two that I do want from the three available. These are KB4344166, KB4344178 and KB4344171.
Now then, logic would tell me that the first one would be for .NET Framework 3.5 and the last one, for 4.5.2, but this is where the cagey bit comes in. Microsoft is so keen to persuade users to install all the upgrades (currently up to 4.7.2 I believe) so now they designate them in reverse order presumably to catch the unwary to install the latest versions.
So if your like me and only want the patches for up to 4.5.2, you can dispense with KB4344166 because that’s intended for the 4.7.1 and 4.7.2. Here’s the info links to the other two:
https://support.microsoft.com/en-in/help/4344178/description-of-the-security-only-update-for-net-framework-3-5-for-wind
https://support.microsoft.com/en-au/help/4344171/description-of-the-security-only-update-for-net-framework-4-5-2-for-wi
I could not agree more with how Micrcosoft Organizes that listing for .NET. I know there are alot of versions but then to bundle all three together on the catalog with little explanation can be frustrating.
Completely agree. This is becoming madness, one friend of mine is unable the update .NET whatever the version with Windows Update, however he always can update installed versions downloading the package at Windows download web. Everything he downloaded through this way is installed with no advertisement but Windows Update never shows “own” updates. :(
Re: KB4343888: in the following article at https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in it states in the “Warning” (pink background) that a CPU firmware upgrade is required. Does this mean the patch won’t do provide any protection if no such firmware has been installed?
In tha respect, there isn’t any CPU firmware available for my system (it’s out of warranty).
Windows 10 1803 64 bit update installed without any problems. See no difference in performance either, and with the state of things lately I am calling this win.
I wonder why so many updates, because in one month we will have a complete new Windows 10 1809 upgrade ISO. So wasted time updating for upgrading, for God’s sake. Thank you Martin.
First time it failed install after re-start. Ran Windows update troubleshooter and ran update again. Installed properly second time. Really getting tired of this stuff, two months in a row. Only one of my Windows 10 PC’s got the update. I am running Windows 10 1803.
Thanks !
looks like just now hit wsus. sync 2 hrs ago had nothing.
yay time to test breaking shit.