![](\"https:\/\/images.idgesg.net\/images\/article\/2018\/03\/microsoft_windows_updates_cycle_arrows_laptop_mobile_phone_3x2-100751944-large.3x2.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Fri, 31 Aug 2018 05:02:00 -0700<\/strong><\/p>\n Time for the final August patching shoe to drop. <\/span><\/p>\n Late last night Microsoft released a flurry of patches, posting them on the Microsoft Update Catalog. Some are available through Windows Update, some aren’t. <\/span><\/p>\n As of early Friday morning, the Win10 patches are not<\/em> available through WSUS, the update server service. It\u2019s not clear if that\u2019s a mistake, a hesitation \u2014 or if somebody just went home last night and forgot.<\/span><\/p>\n Let\u2019s hear it for patching predictability. And transparency.<\/span><\/p>\n Those of you with Win10 <\/span>1803 <\/strong>get\u00a0<\/span>KB 4346783<\/a>, which brings you up to build 17134.254. I found two of the fixes worthy of note:<\/span><\/p>\n Microsoft still hasn\u2019t fixed the months-old bug:<\/span><\/p>\n Launching Microsoft Edge using the New Application Guard Window may fail<\/span><\/p>\n and its solution is to uninstall the Aug. 14 cumulative update, install the July 24 cumulative update, then reinstall the Aug. 14 cumulative update. Which, in a cumulative world, makes no sense whatsoever.<\/span><\/p>\n Folks who are hanging tight with Win10 <\/span>1709 <\/strong>get<\/span> KB 4343893<\/span><\/a>, which brings you up to build 16299.637. There\u2019s a long list of changes, none of which seem particularly noteworthy.<\/span><\/p>\n If you\u2019re using Win10 <\/span>1703 <\/strong>\u2014\u00a0that\u2019s still my choice for production machines \u2014 the new<\/span> KB 4343889<\/span><\/a> brings you up to build 15063.1292. There\u2019s a shorter list of changes. Note that security patches for 1703 will end in October. In six weeks or so, you\u2019ll have to choose between 1709, 1803, or possibly 1809. As you might imagine, I\u2019ll be watching the aging process astutely.<\/span><\/p>\n @abbodi86 advises that<\/span><\/a>, as of Friday morning:<\/span><\/p>\n Windows 10 Updates did not hit WSUS, although 4346783 (1803) and 4343889 (1703) were delivered as Dynamic Updates (i.e., feature upgrade companions)<\/span><\/p>\n There\u2019s also a cumulative update for Win10 1607\/Server 2016, <\/span>KB 4343884<\/span><\/a>. Same old same old.<\/span><\/p>\n The <\/span>Win7 <\/strong>Monthly Rollup Preview, <\/span>KB 4343894<\/span><\/a>, contains a major bug fix for Internet Explorer 11:<\/span><\/p>\n Addresses an issue in Internet Explorer 11 that may cause a blank page to appear for some redirects. Additionally, if you open a site that uses Active Directory Federation Services (AD FS) or Single sign-on (SSO), the site may be unresponsive.<\/span><\/p>\n Which is a wonderful way to describe a bug that Microsoft introduced in the Aug. 14 Monthly Rollup, <\/span>KB 4343900<\/span><\/a>, and in the Aug. 14 Internet Explorer Security-only update, <\/span>KB 4343205<\/span><\/a>. As long as you\u2019re installing Monthly Rollups, the sequencing works out al lright, but if you\u2019re manually installing Security-only updates, the only way to fix the bug in the Aug. 14 Security-only patch is to install this Monthly Rollup Preview. Which, again, makes no sense at all. Thx,\u00a0<\/span>@DrBonzo<\/span><\/a>.<\/span><\/p>\n In addition, the ancient bug with network interface controller drivers is still there:<\/span><\/p>\n There is an issue with Windows and third-party software related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working.<\/span><\/p>\n Not unexpectedly, the Win8.1 Monthly Rollup Preview, <\/span>KB 4343891<\/span><\/a>, looks clean as a hound\u2019s tooth.<\/span><\/p>\n We were, uh, blessed in the middle of the night with three new .Net Previews:<\/span><\/p>\n There are subsidiary KB articles that provide more detailed explanations of the changes in these KBs. Again, I don’t see anything earth-shattering.<\/span><\/p>\n While you were sleeping \u2014 or intentionally ignoring the increasingly dismal news \u2014 Microsoft has also been piling on Intel microcode updates, directed at Meltdown and Spectre (versions 1, 2, 3, 3a, 4, n for n >=4). There continues to be confusion about why the Intel microcode updates get installed on AMD machines, what bits need to be flipped in which registries, and whether firmware updates trump Windows patches. It\u2019s a mess par excellence<\/em>, with little documentation, and nothing official that\u2019s reliable. We have two active threads on the topic(s) on AskWoody, <\/span>here <\/span><\/a>and <\/span>here<\/span><\/a>.<\/span><\/p>\n Don\u2019t know about you, but I can\u2019t download the key Win10 1803 Intel microcode patch, <\/span>KB 4100347<\/span><\/a>. Susan Bradley has been asking Microsoft whether they\u2019ve pulled the patch, and so far <\/span>the only response is crickets<\/span><\/a>. <\/span><\/p>\n Of course, we still haven\u2019t seen any in-the-wild Meltdown or Spectre infections. When we do, the whole exercise will no doubt turn into a delightful marketing opportunity for a couple of hardware manufacturers.<\/span><\/p>\n Sit tight. The cumulative updates are still too young. And I never recommend that you install Previews. There are no significant security exploits that are patched by the July or August crop of fixes (unless you\u2019re using IE in a Chinese company that\u2019s become a target for North Korea). Let\u2019s see if any undead arise over the long weekend.<\/span><\/p>\n Most of Microsoft should be back to work by next week anyway. We missed ya.<\/span><\/p>\n Thx, @abbodi86, @sb, @DrBonzo, @PKCano, @Kirsty.<\/span><\/i><\/p>\n Join the long march to WinOblivion on the <\/span><\/i>AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n