Should you’ve already put in some (or all) of the September patches, you’ve watched a parade of issues go by. The primary stab at September’s Home windows 10 Creators Replace, model 1703, patch introduced all kinds of issues to Edge — crashes, stalls and worse. It additionally introduced some unfortunate HP pc homeowners 5 to 10 minutes of black screens each time Home windows restarted. These issues have been fastened earlier this week.
The Home windows eight.1 patch made it not possible to go online with a Microsoft account. (I do know, a few of you suppose that’s a characteristic.) The Home windows 7 patch made Web Explorer sprout a brand new search field. We had a report of the Home windows 7 patch breaking activation on sure Dell machines, however it seems that’s an remoted drawback. The .NET Safety and High quality Rollup makes sure customized pictures flip black. None of these bugs have fixes, however a minimum of you’ll be ready earlier than putting in the patch — and you may know the place to search for issues.
[ Additionally on Computerworld: eight steps to put in Home windows 10 patches like a professional ]
Workplace, oy! Relying on which model of Workplace you utilize, and which Registry settings you’ve flipped, the present spherical of Workplace safety patches could have left you with Swedish menus within the unsuitable locations, and/or with (deliberately) damaged VBScript issues. Günter Born additionally studies an issue with Outlook syncing with iCloud. The August drawback with merged cells in Phrase and Outlook continues to be round, though Microsoft says it is going to repair that bug on October three. The issues with buggy Outlook patches are nonetheless there. (Recall that the dangerous August Outlook patch was launched, partially, to repair a spell test drawback attributable to a buggy July Outlook patch. And so it goes.)
As at all times, I strongly advocate you keep away from putting in the Preview Rollups on supply, similar to KB 4038803. That’s simple — it's important to test the fitting field to put in the Preview, and also you shouldn’t be checking any containers!
Listed below are my suggestions:
Most of you utilize .NET — a few of you've many various variations put in — and this month there’s a very devilish drawback with .NET Safety and High quality Rollup patches. Whenever you set up this month’s .NET patches utilizing Home windows Replace, should you begin seeing black containers the place there needs to be textual content or an image, it's best to uninstall the Safety and High quality Rollup and set up the Safety-Solely replace.
Sound sophisticated? Yeah, it's. For starters, it's important to work out which model(s) of .NET are in your machine. The simplest means I’ve discovered is to make use of the Raymondcc .NET Detector. (Thx, @MrBrian!) As soon as you already know which model(s) of .NET are in your machine, you possibly can uninstall the Rollup and set up the High quality-only patch by following these directions on the Microsoft Assist website.
You probably have Workplace 2016 put in and you utilize merged cells in tables in both Phrase or Outlook, don’t set up KB 3213656 (the August non-security patch for Phrase 2016) or KB 4011039 (the September non-security patch). Microsoft nonetheless hasn’t fastened the issue. Should you see an entry in Home windows Replace for KB 3213656 or KB 4011039, uncheck the field so it gained’t be put in.
Outlook patches are an unmitigated catastrophe. I like to recommend you chorus from putting in any of the Outlook patches, KB 4011110 (Outlook 2007), KB 4011089 (2010), KB 4011090 (2013) or KB 4011091 (Outlook 2017). Microsoft lists all of these as "Protection in Depth" patches, with no speedy threats.
Home windows 7 and eight.1 patches
Should you’re very involved about Microsoft’s snooping on you and wish to set up simply safety patches, notice that the trail’s getting harder. The previous “Group B” — safety patches solely — isn’t useless, nevertheless it’s now not throughout the grasp of typical Home windows prospects. Should you insist on putting in safety patches solely, observe the directions in @PKCano’s AKB 2000003.
Microsoft continues to be blocking updates to Home windows 7 and eight.1 on latest computer systems. In case you are working Home windows 7 or eight.1 on a PC that’s a 12 months previous or newer, observe the directions in AKB 2000006 or @MrBrian’s abstract of @radosuaf’s methodology to verify you should utilize Home windows Replace to get updates utilized.
If you wish to reduce Microsoft’s snooping however nonetheless set up the entire provided patches, flip off the Buyer Expertise Enchancment Program (Step 1 of AKB 2000007: Turning off the worst Home windows 7 and eight.1 snooping) prior to installing any patches. (Thx, @MrBrian).
You probably have Home windows eight.1, be sure you have a Native account (Microsoft now calls them “Offline accounts” however they’re the identical factor) with full administrator privileges earlier than you apply the September updates. That means should you get locked out of your Microsoft account, you've easy accessibility to a Native account. Microsoft has directions.
Should you’re working quantity licensed Home windows 7 on Dell computer systems, there’s a tiny probability that the September Month-to-month Rollup and/or Safety-only patch will change folder names, thus invalidating your license. If that’s a potential concern, see this AskWoody thread for directions on backing up (i.e., copying) and presumably re-installing the c:WindowsSystem32oem folder.
After all, backing up your machine earlier than making use of updates is at all times a good suggestion. Even (particularly) Home windows and Workplace updates.
For many Home windows 7 and eight.1 customers, I like to recommend following AKB 2000004: The right way to apply the Win7 and eight.1 Month-to-month Rollups. Uncheck the Workplace patches talked about above. Be careful for driver updates — you’re much better off getting them from the producer’s web site.
After you’ve put in the most recent Month-to-month Rollup:
- Should you’re intent on minimizing Microsoft’s snooping, run by way of the steps in AKB 2000007: Turning off the worst Win7 and eight.1 snooping. Notice that we don’t know what data Microsoft collects on Window 7 and eight.1 machines.
- In Outlook, if you could use customized type (VBScript) printing or hook up with iCloud, observe Diane Poremsky’s directions on the Slipstick Techniques website to deliver again VBScript.
- If Web Explorer immediately sprouts a Search field, see these directions on the AskWoody website for assist. (Thx, @PKCano) Whilst you’re at it, critically contemplate why you’re utilizing IE. Except you’re hopelessly hooked into an out of date web site, go for higher safety , much less buggy snooping, and fewer complications with Chrome or Firefox.
Home windows 10 patches
Final month, I beneficial that Anniversary Replace prospects (model 1607) improve to the Creators Replace (model 1703) merely as a result of the patches for 1607 had turned very bitter. Putrid. Now I’m regretting that advice. The patches for 1703 this month are simply as dangerous because the patches final month for 1607. Unsure what to let you know. The one benefit I see to 1703 is that Professional and Enterprise customers can simply block updates — and folk with House who run on Ethernet (not Wi-Fi) can extra readily swap to a metered connection.
Should you run Home windows Replace in 1703 (you will have to show the “Defer updates” setting to zero, see the directions in "eight steps to put in Home windows 10 patches like a professional"), you’ll get the Sept. 25 patch KB 4034674, which has fewer bugs than the Sept. 12 patch. For these with 1607, you’ll get the Sept. 12 patch KB 4038782. Whereas it’s potential to manually obtain and set up the most recent 1607 patch, KB 4038801, launched Sept. 28, I don’t see any good cause to leap by way of these hoops.
These of you continue to on 1511, the Fall Replace (later renamed to “November Replace”), want to maneuver on to 1703 now. The final 1511 safety patches will arrive Oct. 10. Might as nicely swallow your medication now.
To get Home windows 10 patched, run the steps in "eight steps to put in Home windows 10 patches like a professional." You probably have Workplace 2016 put in, and you utilize merged cells in tables in both Phrase or Outlook, use wushowhide as described within the article to “cover” KB 3213656 and/or KB 4011039 and observe the same defense-in-depth technique with the Outlook patches talked about above.You may additionally wish to use wushowhide to cover any driver updates.
The entire different updates needs to be OK, together with Servicing stack updates, Workplace, MSRT, or .NET updates (go forward and use the Month-to-month Rollup if it’s provided).
Should you get little black containers in customized varieties after putting in the most recent patches, see my word above concerning the ongoing bugs in .NET.
As is at all times the case, DON’T CHECK ANYTHING THAT’S UNCHECKED.
Time to get patched. Inform your mates, however be sure that they perceive what’s taking place. And for heaven’s sake, as quickly as you’re patched, flip off computerized updating! Full directions are within the referenced guides to patching.
I simply modified the MS-DEFCON stage on the AskWoody Lounge.