Posted on April 26th, 2017 at 12:06 Comment on the AskWoody Lounge
A fascinating bug reported by Cave_West on the Microsoft Answers forum:
Word 2016 is crashing when clicking on the File menu when certain (not all) documents are open… if we open a document that works (a fresh .docx or any .doc) and while Word is still open try and open a problematic .docx it works. If we try and open a problematic .docx with Word closed first, accessing the File menu causes Word to crash. What’s interesting is that it doesn’t seem to be all .docx files, only certain ones, but for the moment we haven’t identified any commonality between the problem files, in fact most are simple documents with no embedded pictures, macros etc.
Removing the Update for Word 2016 (KB3178720) resolves the issue.
Anybody else seeing this?
Posted on April 4th, 2017 at 14:04 Comment on the AskWoody Lounge
Don’t install anything!
Posted on April 4th, 2017 at 10:05 Comment on the AskWoody Lounge
It’s the first Tuesday of the month. You no doubt know the drill.
In the next few hours, Microsoft will likely issue a big bunch of “Optional” Office updates. You don’t want to install them. Of course.
If you followed my directions for installing the March patches, your system is already set to block updates. If you didn’t follow those directions, you should make sure Automatic Update is turned off.
In Windows 7 click Start > Control Panel. In Win 8.1, press Win-X and choose Control Panel. Click System and Security. Under Windows Update, click the link marked “Turn automatic updating on or off.” Make sure Windows Update is set to “Never check for updates (not recommended).”
In Windows 10, the situation’s a bit more complex, but I have full details in the InfoWorld article Woody’s Win10Tip: Block forced Windows updates. Short version: With Win10 Pro, bring up gpedit, click Administrative Templates > Windows Components > Windows Update. On the right, double-click Configure Automatic Updates. At the top of the resulting settings box, choose Disabled, click OK, and close out of the Group Policy editor. Reboot and you’re done. With Win10 Home, if you’re on a Wi-Fi connection, set it to metered (see the article). If you’re on Win10 Home and you don’t have a Wi-Fi connection, your options are considerably more complex.
Let’s wait and see what surprises this month will bring.
Posted on March 28th, 2017 at 16:35 Comment on the AskWoody Lounge
The new security patch is KB 3191855.
Have you had a chance to try it? Does it work?
Details: InfoWorld Woody on Windows.
Thanks to GregH for the scoop!
Posted on March 27th, 2017 at 14:55 Comment on the AskWoody Lounge
I just got a report from an old friend, GW:
KB 3114389 may be causing Outlook to crash. We are pulling it now to check, it might be linked to software or an ATI graphics card.
It’s Office 2016 (not 365).
Can you confirm?
Posted on March 20th, 2017 at 07:20 Comment on the AskWoody Lounge
UPDATE: A modified, updated version of this article was just published on InfoWorld Woody on Windows.
I’m seeing lots of reports about Excel 2010 freezing after applying Tuesday’s security patch KB 3178690.
On the Microsoft Answers forum, poster gneJim says:
I have had to remove this update from approx. 4 machines (3x Win7, 1x Win10) this morning as Excel 2010 kept crashing out when trying to update SQL queries.
Further on the cut and paste issue. We tested other excel procedures to see if anything else other than the cut and paste would cause a problem. We discovered that if you use the bottom right black cross in a range of cells and drag it down to copy the range into new cells, excel instantly locked up. No macro involved. These results didn’t happen to all sheets, only very large workbooks (19 mb).
On the TechNet Excel forum poster Steve Stretch says:
Since the update 2 days ago (KB3178690). The following section of code now freezes Excel. I guess the application may be churning over and over… This code has worked for 10 years without a hitch, now all 25 clients still running Excel 2010 have reported this freeze error.
Known issues in this security update
After you install this security update, Excel 2010 may crash or hang (stop responding or freeze) when calculations are performed in a workbook. The calculations may be triggered either by code or by user interaction.
Microsoft is researching this problem and will post more information in this article when the information becomes available.
At this point, the only known solution is to uninstall the security patch.
Posted on March 15th, 2017 at 14:18 Comment on the AskWoody Lounge
For a complete overview, see my just-published InfoWorld post.
DON’T INSTALL ANYTHING. It’s much, much too early to tell if there are any problems.
Link list from PKCano:
Win7 Quality x86
Win7 Quality x64
Win7 Security Only x64
Win7 Security Only x86
Win8.1 Quality x86
Win8.1 Quality x64
Win8.1 Security Only x86
Win8.1 Security Only x64
Win8.1 IE/Edge/Flash x86
Win8.1 IE/Edge/Flash x64
Direct links for the IE 11 cumulative security patches:
Again, I DON’T recommend that you install them. Give ’em a couple of weeks to see if there are any stinkers…
UPDATE: And, sure enough, there were stinkers. For those of you who didn’t follow my advice and installed the original patches, here are the hotfixes, thanks once again to PKCano:Win7 x86
com/c/msdownload/update/ software/updt/2017/03/ie11- windows6.1-kb4016446-x86_ ebbcc1e81f44525eaa22fcaf1ab600 41477b5634.msuOffice Patches/Security, Windows Patches/Security KB 4013418, KB 4013429, KB 4013886, KB 4014329, March 2017 Black Tuesday
Posted on March 7th, 2017 at 13:18 Comment on the AskWoody Lounge
Now that you all can log on with your Microsoft accounts again, the official list is here:
I count five Office 2013 patches, twelve for Office 2016. As always, it’d be a good idea to avoid installing them. I’m changing the MS-DEFCON level as we speak.