Time to install Microsoft patches, except KB 4054517 for Win10 Fall Creators Update

December 22, 2017 brianradio2016 No comments exist

December has brought a few surprises in Windows PatchLand, but by and large, the coast is clear. “Clear,” that is, unless you made the mistake of installing the Win10 Fall Creators Update, version 1709 (or got pushed into it), before the nominal four-month testing period lapsed.

In broad terms, it’s safe to install this month’s Windows and Office patches, unless you’re using Win10 1709, although there are a few obscure gotchas that may bite you if you’re using Win7 with encrypted fileshares, or Active Directory app login. For those who installed Win10 1709 before letting the unpaid beta testers skate out on Crait, there’s very little reason to install this month’s security patches, as long as you don’t use Internet Explorer or Edge. Which, if the statistics are to be believed, you probably don’t.

Office atches

Microsoft has a catch-all web page for known (which is to say, officially acknowledged) bugs in Office patches. In it, you’ll find entries for known Outlook problems (“After updating to Win10 1709, the Outlook People Pane no longer shows any results”), Excel problems (“You may experience problems loading the Excel Solver add-in if you have WPS Office installed on your machine”), and OneNote (“Can’t rename sections in OneNote for Windows”). There’s also a general warning that if you’re having crashes upon opening files located in OneDrive, you need to install the latest version of OneDrive.

I don’t know why, but there’s no mention on that page of the major change in the way Word blocks DDEAUTO fields after installing this month’s Word security patches. I talked about that earlier this week. Bottom line: You should install this month’s Word security patch — KB 4011575, 4011590, 4011608, 4011612, and/or 4011614 — but be aware of the potential problem. If you subsequently open a Word doc, and it no longer responds correctly (by, say, pulling data from an Excel spreadsheet and putting the data in the doc), you need to slog through the manual workarounds, edit the registry, and put DDE right again.

Leave a Reply

Your email address will not be published. Required fields are marked *