{"id":12466,"date":"2018-06-02T20:30:02","date_gmt":"2018-06-03T04:30:02","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/06\/02\/news-6235\/"},"modified":"2018-06-02T20:30:02","modified_gmt":"2018-06-03T04:30:02","slug":"news-6235","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2018\/06\/02\/news-6235\/","title":{"rendered":"May Windows and Office patches are now relatively stable, but Win7 NIC problems persist"},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Sat, 02 Jun 2018 19:34:00 -0700<\/strong><\/p>\n

At least the really bad bugs, introduced by \u201csecurity\u201d patches earlier this month, have been fixed. The problems that remain reside in the dregs \u2014 not likely to bite, but worth knowing about in case something suddenly goes bump in the night. <\/span><\/p>\n

And if you\u2019re using Win10 1803, you should definitely ask Microsoft for an increase in combat-duty pay.\u00a0<\/span><\/p>\n

Remember when Win7 was relatively stable? OK, OK; \u201cstable\u201d is a relative term that\u2019s unlikely to apply to any version of Windows, but you know what I mean. Win7 and Server 2008 R2 have gone through months of problems with networking in general, and apoplectic network interface cards in particular. <\/span><\/p>\n

This month\u2019s problem (which is different from the previous two months\u2019 bugs) involves a <\/span>bad .inf file<\/span><\/a>. If you get bit, you don\u2019t see one of those completely inscrutable error messages (\u201c<\/span>CredSSP encryption oracle remediation<\/span><\/a>\u201d anyone?). Instead, your network card just dies. Kerplop.<\/span><\/p>\n

Microsoft says it\u2019s a problem in the May Win7 Monthly Rollup doc, <\/span>KB 4103718<\/span><\/a>:<\/span><\/p>\n

Symptom: There is an issue with Windows and a third-party software that is related to a missing file (<\/span>oem<number>.inf<\/span><\/i>). Because of this issue, after you apply this update, the network interface controller will stop working.<\/span><\/p>\n

Workaround: <\/span><\/p>\n

Which must rank as one of the most convoluted instructions Microsoft has ever published. At least, one of the most convoluted instructions this month. Note that Microsoft tells us there\u2019s an issue with third-party software, but doesn\u2019t deign to tell us which third-party software.<\/span><\/p>\n

If, after installing this month\u2019s Win7\/Server 2008 R2 Monthly Rollup KB 4103718 (or possibly the Security-only patch KB 4103712), your network interface card stops working, you can use Microsoft\u2019s steps to get going again. Once you\u2019re back online, take <\/span>Susan Bradley\u2019s advice<\/span><\/a>:<\/span><\/p>\n

visit the vendor of your computer or the vendor of your network card and update both your bios and network drivers from the vendor\u2019s web site.<\/span><\/p>\n

If you\u2019re stuck in Win10 April 2018 Update \u2014 the <\/span>notoriously buggy<\/span><\/a> version 1803 \u2014 you need to get the latest cumulative update applied, <\/span>KB 4100403<\/span><\/a>. But before you do that, think. If you \u201cup\u201dgraded to 1803 fewer than 10 days ago, it\u2019s still easy to roll back to your previous version: Start > Settings > Update & security, on the left choose Recovery. Under Go back to the previous version of Windows, click Get started. Click through Microsoft\u2019s warnings again (and again and again) and finally click Buzz Off, I want my old Windows back. Or the functional equivalent. Once you\u2019ve rolled back, be sure you <\/span>take the necessary precautions <\/span><\/a>to keep Microsoft from forcing you back to 1803 again.<\/span><\/p>\n

Speaking of forced upgrades, Microsoft is <\/span>actively looking for folks<\/span><\/a> who were upgraded to 1803 even though t<\/span>hey had Win10 1709 set to defer updates<\/span><\/a>. Those of you with the temerity to click \u201cCheck for updates\u201d \u2014 you <\/span>seekers \u2014<\/span><\/a>\u00a0need not apply.<\/span><\/p>\n

By the way \u2026 those of you who are convinced that 1803 now runs on half of all Win10 PCs need a lesson in lies, damn lies and statistics. Ed Bott over on ZDNet has <\/span>a great takedown<\/span><\/a> of the AdDuplex numbers that fueled the clearly ridiculous assertion. 1803 hasn\u2019t taken over the Win10 universe. At least, not yet.<\/span><\/p>\n

The bugs introduced earlier in the month are fixed. I think.<\/span><\/p>\n

My production machines are still on 1703, but when I get a spare couple of hours, I\u2019ll probably move to 1709. (Yes, I downloaded and <\/span>saved a copy<\/span><\/a> of the Win10 1709 ISO file back while it was available. If you need one, check out<\/span> Ed Tittel and Kari Paajolahti\u2019s article<\/span><\/a> in Computerworld<\/em>.)<\/span><\/p>\n

I think it\u2019s quite remarkable that Windows 8.1 continues to stand out as the most stable version of Windows available.<\/span><\/p>\n

Susan Bradley\u2019s <\/span>Master Patchlist<\/span><\/a> shows we\u2019re basically ready to roll, although the official <\/span>Fixes or workarounds articles <\/span><\/a>for Office include many specific problems and a few possible solutions.<\/span><\/p>\n

Ready to take a chance on messing up your NIC? Here\u2019s how to proceed. The patching pattern should be familiar to many of you.<\/span><\/p>\n

There\u2019s a non-zero chance that the patches \u2014 even the latest, greatest patches of patches of patches \u2014 will hose your machine. Best to have a backup that you can reinstall even if your machine refuses to boot. This, in addition to the usual need for System Restore points.<\/span><\/p>\n

There are plenty of full-image backup products, including at least two good free ones:<\/span> Macrium Reflect Free<\/span><\/a> and<\/span> EaseUS Todo Backup<\/span><\/a>.<\/span><\/p>\n

Microsoft is blocking updates to Windows 7 and 8.1 on recent computers. If you are running Windows 7 or 8.1 on a PC that\u2019s a year old or less, follow the instructions in<\/span> AKB 2000006<\/span><\/a> or<\/span> @MrBrian\u2019s summary of @radosuaf\u2019s method<\/span><\/a> to make sure you can use Windows Update to get updates applied.<\/span><\/p>\n

If you\u2019re very concerned about Microsoft\u2019s snooping on you and want to install just security patches, realize that the privacy path\u2019s getting more difficult. The old \u201cGroup B\u201d \u2014 security patches only \u2014 isn\u2019t dead, but it\u2019s no longer within the grasp of typical Windows customers. If you insist on manually installing security patches only, follow the instructions in @PKCano\u2019s<\/span> AKB 2000003<\/span><\/a> and be aware of<\/span> @MrBrian\u2019s recommendations<\/span><\/a> for hiding any unwanted patches.<\/span><\/p>\n

For most Windows 7 and 8.1 users, I recommend following<\/span> AKB 2000004: How to apply the Win7 and 8.1 Monthly Rollups<\/span><\/a>. Realize that some or all of the expected patches for April may not show up or, if they do show up, may not be checked. DON’T CHECK any unchecked patches. Unless you’re very sure of yourself, DON’T GO LOOKING for additional patches. That way thar be tygers. If you’re going to install the May patches, accept your lot in life, and don’t mess with Mother Microsoft.<\/span><\/p>\n

If you want to minimize Microsoft\u2019s snooping but still install all of the offered patches, turn off the Customer Experience Improvement Program (Step 1 of<\/span> AKB 2000007: Turning off the worst Windows 7 and 8.1 snooping<\/span><\/a>) before you install any patches. (Thx, @MrBrian.) If you see KB 2952664 (for Win7) or its Win8.1 cohort, KB 2976978 \u2014 the patches that so helpfully make it easier to upgrade to Win10 \u2014 uncheck them and spread your machine with garlic. Watch out for driver updates \u2014 you\u2019re far better off getting them from a manufacturer\u2019s website.<\/span><\/p>\n

After you\u2019ve installed the latest Monthly Rollup, if you\u2019re intent on minimizing Microsoft\u2019s snooping, run through the steps in<\/span> AKB 2000007: Turning off the worst Win7 and 8.1 snooping<\/span><\/a>. Realize that <\/span>we don\u2019t know <\/i><\/strong>what information Microsoft collects on Window 7 and 8.1 machines. But I\u2019m starting to believe that information pushed to Microsoft\u2019s servers for Win7 owners is nearing equal to that pushed in Win10.<\/span><\/p>\n

If you\u2019re running Win10 Creators Update, <\/span>version 1703<\/strong> (my current preference), or <\/span>version 1709<\/strong>, the Fall Creators Update, and you want to stay on 1703 or 1709 and not get sucked into the 1803 pre-release vortex, follow the<\/span> instructions here<\/span><\/a> to ward off the upgrade. Of course, all bets are off if Microsoft, uh, <\/span>forgets to honor<\/span><\/a> its own settings. <\/span><\/p>\n

Remember: If you want to avoid 1803, don\u2019t click \u201cCheck for Updates\u201d until you\u2019ve gone through all the precautions <\/span>listed in this article<\/span><\/a>, including running wushowhide. If you forget, you may be <\/span>tossed in the seeker heap<\/span><\/a> and shuffled off to 1803 land.<\/span><\/p>\n

If you\u2019re running an earlier version of Win10, you\u2019re basically on your own. Microsoft doesn’t support you anymore.<\/span><\/p>\n

If you have trouble getting the latest cumulative update installed, make sure you\u2019ve checked your antivirus settings and, if all is well, run the<\/span> newly refurbished<\/span><\/a> Windows Update Troubleshooter<\/span><\/a> before inventing new epithets.<\/span><\/p>\n

To get Windows 10 patched, go through the steps in “<\/span>8 steps to install Windows 10 patches like a pro<\/span><\/a>.”<\/span><\/p>\n

Thanks to the dozens of volunteers on AskWoody who contribute mightily, especially @sb, @PKCano and @MrBrian.<\/span><\/i><\/p>\n

We\u2019ve moved to MS-DEFCON 3 on the<\/span><\/i> AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Sat, 02 Jun 2018 19:34:00 -0700<\/strong><\/p>\n

\n
\n

At least the really bad bugs, introduced by \u201csecurity\u201d patches earlier this month, have been fixed. The problems that remain reside in the dregs \u2014 not likely to bite, but worth knowing about in case something suddenly goes bump in the night. <\/span><\/p>\n

And if you\u2019re using Win10 1803, you should definitely ask Microsoft for an increase in combat-duty pay.\u00a0<\/span><\/p>\n

The ongoing Win7\/Server 2008 R2 patching threat<\/strong><\/h2>\n

Remember when Win7 was relatively stable? OK, OK; \u201cstable\u201d is a relative term that\u2019s unlikely to apply to any version of Windows, but you know what I mean. Win7 and Server 2008 R2 have gone through months of problems with networking in general, and apoplectic network interface cards in particular. <\/span><\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[714,10525],"class_list":["post-12466","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-security","tag-windows"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/12466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=12466"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/12466\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=12466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=12466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=12466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}