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.
Posted on March 2nd, 2017 at 10:22 Comment on the AskWoody Lounge
With few outstanding patches, and all but one well-behaved, now’s an excellent time to get caught up.
InfoWorld Woody on Windows
Posted on February 15th, 2017 at 10:17 Comment on the AskWoody Lounge
There’s a lot of conjecture. I haven’t seen any Feb “Patch Tuesday” style patches. Have you?
Hard to believe all of the patches – Vista, Win7, 8.1, various 10s, the Offices including Click-to-Run, IE, .NET, and all the weird supporting patches have all gone missing.
The only conclusion I can draw – and it’s 100% speculation – is that Windows Update is broken. Or maybe compromised.
Do you have any better info – or a contrary opinion?
UPDATE: Gregg Keizer at Computerworld just posted an interview with a security expert who, amazingly, seems to say exactly what I’m saying.
Posted on February 14th, 2017 at 09:25 Comment on the AskWoody Lounge
This is a repost of a blog item that got gobbled up when the site went down. Here’s the original post, but the original comments are gone.
Yet another fascinating bit of sleuthing from Günter Born.
Normally, when you install Office 365, Office 2016, or Office 2013, they’re activated automatically. Sometimes automatic activation fails, though, and you need to enter a product key or even contact Microsoft to activate a completely-legitimate copy.
There’s a lengthy, detailed description of how to do that on this Microsoft Office blog page. One problem: The method described there doesn’t always work for the non-365 versions of Office. At the top of the Microsoft blog page there’s a new notice that:
Customers report that when selecting the option to activate Office by telephone, they receive this error: Telephone activation is no longer supported for your product. This issue impacts Office non-subscribers only. We are actively working on fixing this issue. In the meantime, you can call the numbers for your specific country/region listed in this article.
The referenced site asks you to choose your country, provides you with a telephone number. Call that phone number and you should be activated automatically.
There’s another activation method, though, which was recommended last month in one of Born’s comment sections. That comment points to Microsoft’s Self Service for Mobile product activation page. Long story short, that activation option – which requires you to type in your Installation ID – is not on a secure page. Microsoft’s instructions direct you to a third-party web site, and tell you to type your Installation ID into that web site.
Read Born’s exposé to see how he tracked down that page – a page requesting your Office activation details – through GoDaddy and ultimately found the owner.
No, it isn’t Microsoft.
Somebody’s collecting a whole lot of valid Office Installation IDs – and Microsoft’s helping them do it.
Posted on February 11th, 2017 at 06:04 Comment on the AskWoody Lounge
I still haven’t seen many reports, but @learnpowershell has been testing:
— Dave Ackroyd (@learnpowershell) February 11, 2017
Earlier report here.
I’m still looking for corroboration – and a more detailed description of the problems.
Posted on February 8th, 2017 at 12:36 Comment on the AskWoody Lounge
One very short report is here on the FindTime forum.
Can anybody corroborate?