![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security3-100734732-large.3x2.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Wed, 27 Jun 2018 13:23:00 -0700<\/strong><\/p>\n Microsoft’s patches in June took on some unexpected twists.<\/p>\n Windows 7 owners with older, 2002-era Pentium III machines got their patching privileges revoked<\/a> without warning or explanation (and a documentation cover-up to boot), but there\u2019s little sympathy in the blogosphere for elderly PCs.<\/p>\n Win10 1803 was declared fully fit for business<\/a>, a pronouncement that was followed weeks later by fixes for a few glaring, acknowledged bugs \u2014 and stony silence for other known problems.<\/p>\n We\u2019re continuing the two-big-cumulative-updates-a-month pace for all supported versions of Windows 10. The second cumulative update frequently fixes bugs introduced by the first cumulative update.<\/p>\n Microsoft may think that Win10 (1803) is ready for widespread deployment, but there are a few folks who would take issue with that stance.<\/p>\n Yesterday, Microsoft finally released a fix for two big bugs<\/a> that have dogged Win10 1803 since its inception. In theory, patch KB 4284848 fixes these acknowledged bugs:<\/p>\n In practice, life isn\u2019t so simple. WSUS (the Windows Update Server software) isn\u2019t \u201cseeing\u201d KB 4284848, as of late Wednesday afternoon \u2013 \u00a0which may be a good thing.<\/p>\n Along with the second cumulative update this month, there are additional releases to fix the Servicing Stack<\/a>, and a new \u201cCompatibility update<\/a>\u201d that, per the documentation, is designed to make it easier to upgrade Win10 1803 Enterprise to Win10 1803 Enterprise (not a typo).<\/p>\n Old problems remain in abundance. There are many reports of munged Intel NICs and VLAN problems<\/a> after installing 1803. Josh Mayfield (whom you may recall from GWX days<\/a>) reports that you\u2019re forced to set up a PIN<\/a> during fresh installs. The ancient problem with restore partitions getting assigned drive letters on install remains. Chrome continues its indigestion with 1803, although Microsoft claims the latest patch cures all ills. None of this is acknowledged anywhere I can see.<\/p>\n One problem that has been acknowledged \u2013 but only by a Microsoft Agent on an Answers Forum post<\/a> \u2013 says that installing 1803 can clobber your peer-to-peer network. That certainly matches my experience. With earlier versions of Win10, I\u2019d fire up the Homegroup Troubleshooter and that usually solved the problem. Unfortunately, Microsoft discontinued Homegroups in version 1803.<\/p>\n On the positive side, WindowsCentral\u2019s Zac Bowden reports<\/a> that yesterday\u2019s 1803 patch fixes lagging\/stuttering issues on his Surface Book 2 \u2013 a problem that\u2019s neither acknowledged, nor described in the list of fixes.<\/p>\n If you think Win10 1803 is ready for prime time, you\u2019re welcome to give it a try.<\/p>\n Multiple patches for supported versions of Win10<\/strong><\/p>\n We still have an acknowledged bug, introduced by the Win7 patches in March:<\/p>\n There is an issue with Windows and a 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.<\/p>\n As noted by an anonymous poster<\/a> last month:<\/p>\n It\u2019s not only KB4103718 (May 8, 2018\u2014KB4103718 (Monthly Rollup)) that has been updated with the missing oem<number>.inf issue. The problem seems to date back to the March 2018 Security-Only and Monthly Rollup updates.<\/p>\n All of the following knowledge base articles were updated with similar warnings on May 25, 2018:<\/p>\n Microsoft won\u2019t say which vendor(s) and\/or which network card(s) are getting cracked by the patch. There\u2019s speculation that the bad card is from Intel<\/a>, but we really don\u2019t know. Your only real recourse is to create a full backup prior to applying this month\u2019s patches, or to accept the possibility that you\u2019ll have to manually re-install them. Susan Bradley has detailed instructions<\/a>.<\/p>\n The bottom line<\/strong><\/p>\n Windows 8.1 continues to hold the title as the most stable version of Windows. Hard to believe.<\/p>\n This month\u2019s Office patches seem to be working, although there are many individual problems listed in the Office Fixes or Workarounds list<\/a>.<\/p>\n Stay tuned.<\/p>\n Thx to @sb and @PKCano<\/em><\/p>\n Struggling with other problems? Join us on the AskWoody Lounge<\/a>.<\/em><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Wed, 27 Jun 2018 13:23:00 -0700<\/strong><\/p>\n Microsoft’s patches in June took on some unexpected twists.<\/p>\n Windows 7 owners with older, 2002-era Pentium III machines got their patching privileges revoked<\/a> without warning or explanation (and a documentation cover-up to boot), but there\u2019s little sympathy in the blogosphere for elderly PCs.<\/p>\n<\/p>\n