Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • August 2018 Office non-Security updates are available

    Posted on August 7th, 2018 at 14:03 PKCano Comment on the AskWoody Lounge

    August 2018 Office non-security updates have been released by Microsoft on August 7, 2018.

    Just a reminder – these updates are NOT covered under the July DEFCON setting. Unless you have a specific need to install them, you should wait until Susan Bradley (Patch Lady) approves them and any problems have been reported. They are still untried and untested. Don’t be a Guinea Pig.

    Office 2013

    Update for Microsoft Office 2013 (KB3172506)
    Update for Microsoft Office 2013 (KB4011155)
    Update for Microsoft Office 2013 (KB4022212)
    Update for Microsoft OneDrive for Business (KB4022226)
    Update for Microsoft PowerPoint 2013 (KB4018374)
    Update for Skype for Business 2015 (KB4032250)

    Office 2016

    Update for Microsoft Office 2016 (KB4032234)
    Update for Microsoft Office 2016 Language Interface Pack (KB4032232)
    Update for Microsoft OneNote 2016 (KB4022216)
    Update for Microsoft PowerPoint 2016 (KB4018368)
    Update for Microsoft Project 2016 (KB4032238)
    Update for Microsoft Word 2016 (KB4032258)
    Update for Skype for Business 2016 (KB4032255)
    Update for Microsoft OneDrive for Business (KB4022219)

    There were no non-security listings this month for Office 2010 and no listings for Office 2007 (which is out of support).
    Office 365 and C2R are not included.
    Security updates for all supported versions of Microsoft Office are released on the second Tuesday of the month (Patch Tuesday).

  • Patch Lady – my response

    Posted on August 4th, 2018 at 11:55 Susan Bradley Comment on the AskWoody Lounge

    To keep everyone in the loop:

    As I said in my response… I know this has to be better and I honestly trust in that process.

    And this is what I sent back to the customer support response I got as well as once again ccing and emailing Mr. Nadella, Mr. Picoto and Mr. Guthrie below:

    Thank you ____ for reaching out to me. Just so that you are aware I actually have bugged into the feedback venue on this same issue a few months ago – see here: In fact it’s because of this earlier feedback posting that I went to the broader patching community to get their viewpoints and then reached out to Microsoft in the form of emailing Mr. Nadella, Mr. Picoto, and Mr. Guthrie as I saw things getting worse, not better after I entered my feedback into the Windows feedback process.

    My apologies if I didn’t make all of you aware of this before but I am fully aware of how Windows 10 updating model works. I have in fact given courses on Windows 10 updating at several technology conferences, I write on the topic and give guidance to IT professionals, consultants and consumers as to patching processes and side effects. A recent blog post points out what I think is the disconnect between what the goals of Microsoft are and the reality of Windows servicing today.

    It indicates that Microsoft uses the principles of being simple and predictable, agile and transparent. But that’s the thing, it hasn’t been in the past few months. It’s been chaotic, we’ve had a lack of clear communication, nor has it been as agile as it could have been with updates not being released to all platforms (we’ve had to import updates into WSUS, or the C and D patches aren’t offered on the WU channel for example).

    We in the patching community would love it if you followed those principles. Please do so.

    We in the patching community would request one agility change: that in the cadence of feature releases. Twice a year is causing too much disruption in the management of technology. It’s causing firms to not be fluid in their updates. It’s causing too many firms to consider LTSB as a means to slow down the cadence.

    Since I didn’t open this service request, it is not my place to close it. I once again am emailing the individuals on my initial email to follow up that they better understand my ask: Please be simple. Please be predictable. Please be transparent. Please don’t compromise quality or compatibility. Finally please do understand the feature release cadence is too disruptive to your customer base.

    Thank you for your anticipated follow up to my letter. I know as a shareholder and customer of your software that you HAVE to be just as concerned as I am about the quality issues of Windows patches. I urge you to go back to my letter where I have several recommendations and consider ways to improve. This has to get better and I anticipate that you are just as concerned as I am about this issue.

    Thanking you again, Susan Bradley

    Moderator at

    Writer on the topic of patches for
    August 3, 2018

  • CCleaner 5.45 removed

    Posted on August 3rd, 2018 at 22:17 Kirsty Comment on the AskWoody Lounge

    A couple of days ago, Martin Brinkmann (on wrote:

    Don’t install or upgrade to CCleaner 5.45

    Piriform/Avast released CCleaner 5.45 recently to the public that Windows users may not want to install or upgrade to.

    Today, Lawrence Abrams (on wrote:

    CCleaner v5.45 Pulled Due to Anger Over Usage Data Collection

    It has not been a good week for Piriform’s PC cleaning tool CCleaner. With the release of CCleaner version 5.45, it was quickly discovered that the program’s “Active Monitoring” component, which is utilized to send anonymous usage data back to Piriform, could no longer be disabled.
    First discovered by, users of version 5.45 discovered that unlike previous versions there was no privacy setting that allowed you to disable the sending of anonymous usage information to Piriform.

    This was discussed here on Piriform CCleaner & Speccy

    Now, feedback has resulted in changes, as noted on today:

    Today we have removed v5.45 and reverted to v5.44 as the main download for CCleaner while we work on a new version with several key improvements. You can grab version 5.44 from one of the links [below]:

    (You can find those download links here)

    It’s nice to know that feedback can make a difference, while they go back to their drawing boards, trying to keep their customers happier.

  • The official response from Microsoft about Susan Bradley’s questionnaire results and open letter

    Posted on August 3rd, 2018 at 10:32 woody Comment on the AskWoody Lounge

    I’ve seen some condescending, white-washed pablum coming out of Redmond before, but this just about takes the cake.

    Computerworld Woody on Windows.

  • Update in the browser wars: If you ain’t Chrome, you ain’t jack

    Posted on August 3rd, 2018 at 07:10 woody Comment on the AskWoody Lounge

    Gregg Keizer has his usual monthly report in Computerworld, with some unusual findings:

    Chrome added nearly 4 percentage points to its user share in July (per Net Applications), ending at 64.7%. The last time a browser owned that large a chunk of the world’s browser market was in late 2009, when IE accounted for two-thirds of the total… Edge remains a flop. In July, just 11.5% of all Windows 10 users relied on Edge, a record low for the long-struggling browser.

    Remember that Windows 10 in S Mode only runs Edge. No other choice. And the new, fawned-over Surface Go starts with Win10 Home in S Mode.

  • Patch Lady – Office 365 eula is due to update

    Posted on August 2nd, 2018 at 15:06 Susan Bradley Comment on the AskWoody Lounge

    If you recently got that, it’s just due to click to run update as noted in an Office KB.  Bottom line, click through the accept it should be just fine afterwards.



    You may receive an unexpected pop-up message regarding the Office license agreement and may also be unable to access Office.


    We’ve identified that a recent feature update has modified the storage location of the End User Licensing Agreement (EULA) acceptance information and is causing users to receive a pop-up message prompting them to accept the user agreement. We’ve initiated the process of reverting this update to mitigate impact.

    In the meantime, if you receive a pop-up regarding the End User Licensing Agreement (EULA), clicking Accept should enable access to Office. Dismissing the pop-up may result in Office closing.

  • Patch Lady – guiding principles on patching

    Posted on August 2nd, 2018 at 14:51 Susan Bradley Comment on the AskWoody Lounge

    Today on the Windows IT blog there is a post about patching.  No, it’s not a response to my open letter, rather it’s an explanation of terms and guiding principles.  In it, it talks about …

    We use the following principles for the monthly Windows servicing process:

    • Be simple and predictable. IT managers should be able to plan for a simple, regular and consistent patching cadence. You shouldn’t need to stop what you’re doing to test and deploy an update. You should be able to plan a time, well in advance, to work on new updates. You also shouldn’t have to memorize multiple release schedules; the Windows release cadence should align with that of other Microsoft products.

    • Be agile. In today’s security landscape, we must be able to respond to threats quickly when required. We should also provide you with updates quickly without compromising quality or compatibility.

    • Be transparent. To simplify the deployment of Windows 10 in large enterprises or small businesses, you should have access to as much information as you need, and you should be able to understand and prepare for updates in advance. This includes guides for common servicing tools, simple release notes, and access to assistance or a feedback system to provide input.

    As I just realized that I’m behind on my master patch list for the month of July because I didn’t note the catalog only 1607 release for the .NET July side effects – I deeply question if July showcases simplicity, predictability or transparency.

    I mean no disrespect to Mr. Wilcox but July was not a stellar month in my book.

    For the record the .NET side effects appear to impact server side applications more than workstation side which is why Microsoft put an agility push to fix Server 2016 asap.  It’s also why these updates are only on the catalog site, not on Windows update nor on WSUS.  It takes less red tape to post them to the catalog site.  The rest of the .NET updates for Windows 10 will be out with the regular updating process expected (at this time anyway) to be on the 14th of August.

    For anyone wondering if I’ve been contacted by Microsoft:  I have been assigned a support number and a customer relationship manager has contacted me.  I’m still keeping the faith.  I know that these issues have to be fixed — ESPECIALLY if someday we all end up with machines in the cloud and nothing else.

  • What are YOUR favorite free Windows 10 programs?

    Posted on August 2nd, 2018 at 14:16 woody Comment on the AskWoody Lounge

    Every time a new edition of Win10 All-In-One For Dummies ships, there’s a lot of attention devoted to the list of my favorite free Win10 programs, near the back of the book. I usually stick to about 10 free programs (or should I say “apps”?), give or take a couple. I still think that those freebies, plus the admonitions about the things you don’t need, pay for the price of the book, all by themselves, ignoring the other thousand-or-so pages.

    When writing for Computerworld, I don’t have the same space constraints, so I expand the list to 30 or so of the “best” using criteria that are entirely personal.

    I’m going to update that list in CW shortly, and I’d like your help.

    Tell me about your favorite free Windows 10 apps. I’m not looking for snazzy. I want meat ‘n taters apps that really make a difference in how you get things done. Only two requirements:

    • They have to be free, or perhaps have a free version
    • They have to run on Win10. Why? The universe of great free Win7 programs has been largely stagnant. Don’t shoot the messenger.

    What do you use? Why do you like it? What are the downsides? Tell me about them here – and include links if you have them….