Newsletter Archives
-
Fix released for the botched Excel 2010 security patch KB 3178690
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!
-
Microsoft’s month of badly botched patches
They just keep rolling in.
See InfoWorld Woody on Windows
-
Excel security patch MS17-014 for Excel 2010, KB 3178690, triggering crashes
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.
(D-N) says:
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.
Microsoft acknowledges the problem, both in the KB article, and on the Office support forum.
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.