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
  • June 2018 Office Non-security updates have been released

    Posted on June 5th, 2018 at 15:24 PKCano Comment on the AskWoody Lounge

    June 2018 Office non-security Updates have been released by Microsoft on June 5, 2018.

    Just a reminder – these updates are NOT covered under May DEFCON-3. 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 will still be here tomorrow, and next week (and next month, for that matter). Don’t be a Guinea pig!

    Office 2013

    Update for Microsoft OneDrive for Business (KB3178712)
    Update for Microsoft Project 2013 (KB4022171)
    Update for Microsoft Word 2013 (KB4022186)
    Update for Skype for Business 2015 (KB4022170)

    Office 2016

    Update for Microsoft Office 2016 (KB4022156)
    Update for Microsoft Office 2016 (KB4022158)
    Update for Microsoft Office 2016 (KB4022159)
    Update for Microsoft Office 2016 (KB4022193)
    Update for Microsoft Office 2016 Language Interface Pack (KB4018370)
    Update for Microsoft OneDrive for Business (KB4011100)
    Update for Microsoft OneNote 2016 (KB4022163)
    Update for Microsoft Project 2016 (KB4022164)
    Update for Microsoft Word 2016 (KB4022175)
    Update for Skype for Business 2016 (KB4022155)

    There were no non-security listings this month for Office 2010.
    There were no non-security listings this month 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).

  • What’s an SAC-T? What’s going to happen to the old SBB? And why should you care?

    Posted on June 5th, 2018 at 13:39 woody Comment on the AskWoody Lounge

    Microsoft’s terminology for Windows 10 releases is so infernally screwed up it’s hard to imagine the official terms could get any worse.

    Don’t hold your breath.

    Late last week, we got word that “Semi-Annual Channel (SAC) – Targeted” gobbledygook is going away – to be replaced by what, we don’t know.

    There’s been so much turmoil in the terminology that you might (rightfully) assume that the people in charge don’t have a clue what they’re doing. And, in my humble opinion, you’d be right.

    I think it’s likely that Microsoft will move farther toward the “we’ll update/upgrade your Win10 machine whenever we feel like it” end of the spectrum. Chances are good they’ll use this new terminology change to mask the process.

    We’ve already seen a move in that direction. In Win10 1703 and 1709, we (delightfully!) got an easy-to-use interface for Win10 Pro update deferral settings. The settings were never precisely explained, but such is life in Microsoft land.

    Then, in 1803, things changed. Arguably the worst “feature” in 1803 is its hiding of those deferral settings, pushing them back into the Group Policies whence they came. You can still defer cumulative updates and “feature enhancements” (better understood as version changes), but only on Pro and Enterprise, and only by using the arcane Group Policy interface.

    Now we’re looking forward to yet another change. Oh boy.

    Look, folks. All I want is a simple “Off” switch – let me decide when you can apply updates. That’s what we had in Win7 and 8.1. That’s what we need right now.

    Our own @Zero2dash put it this way:

    “I am altering the deal. Pray I don’t alter it any further.” How many times has the deal been altered at this point? I’ve lost count. This is no bueno. I foresee a whole lot more “accidental” upgrades in the future for everyone.

    (I’ve moved the comments on his topic over to this one.)

  • Patch Lady – Not all patches make it to WSUS

    Posted on June 5th, 2018 at 10:54 Susan Bradley Comment on the AskWoody Lounge

    WSUS – or Windows Server Update Services – is what many corporate/business patchers use to update machines.  Larger firms use SCCM – System Center configuration manager.  But recently many of us have noticed something unusual.  The updates that come out here:  Don’t always make it on this list:

    The second link is a master listing of what is released to the WSUS platform (which ultimately impacts SCCM as well).  And here’s the head scratcher…… recently updates like https://support.microsoft.com/en-us/help/4103714 – the second 1709 update released during May and https://support.microsoft.com/en-us/help/4103722 the second 1703 update released during May didn’t end up on WSUS.  Why?  I’m honestly not sure.  Granted they include no new security updates.  Granted they are just bug fixes, but clearly someone at Microsoft deems them not important enough to deliver them to the business patching platform.  If an administrator wants them you can manually import them from the catalog into WSUS BUTTTTTTTT make sure you also match up these updates with the corresponding Servicing stack update.

    1703 needs https://support.microsoft.com/en-us/help/4132649/servicing-stack-update-for-windows-10-1703-may-17-2018

    1709 needs https://support.microsoft.com/en-us/help/4132650/servicing-stack-update-for-windows-10-version-1709-may-21-2018

    Windows 10 has to have the servicing stack update installed before the cumulative update.  When you update via windows update this is automatic.  When you patch via WSUS make sure your manual approval (or automatic approvals) includes approving both.  The Servicing stack update (or SSU) is deemed a critical update so if you have a rule set to approve critical updates, it will be approved accordingly.  Once you approve it, the operating system is smart enough to install the SSU first and then the Cumulative update (CU) second.

    But bottom line for those of you that patch with WSUS, if you are looking for certain bug fixes, they may not be up on your patching platform.

    P.S. and update – interestingly enough https://support.microsoft.com/en-us/help/4100403/windows-10-update-kb4100403 the second release for the month of May for 1803 IS in WSUS.  Still scratching my head as to why some of the second of the monthly updates are and are not in WSUS.  The SSUs of KB4132649 (1703) and KB4132650 (1709) are up in WSUS.  Man I have an itchy head.