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

    Posted on March 6th, 2018 at 12:34 PKCano Comment on the AskWoody Lounge

    Microsoft has released the March 2018 Office non-secruity updates. These are NOT covered under February’s DEFCON-3 patching. Wait to install them until any potential problems are known and for the Patch Lady’s guidance. If you are following Woody’s DEFCON system, wait for the March DEFCON patching go-ahead.

    Office 2010

    Update for Microsoft Outlook 2010 (KB4018314)

    Office 2013

    Update for Microsoft Office 2013 (KB3172471)
    Update for Microsoft Office 2013 (KB4011152)
    Update for Microsoft Office 2013 (KB4018297)
    Update for Microsoft Project 2013 (KB4018292)
    Update for Microsoft Visio 2013 (KB4011230)
    Update for Skype for Business 2015 (KB4018290)

    Office 2016

    Update for Microsoft Office 2016 (KB4011624)
    Update for Microsoft Office 2016 (KB4011671)
    Update for Microsoft Office 2016 (KB4011728)
    Update for Microsoft Office 2016 (KB4011729)
    Update for Microsoft Office 2016 (KB4011732)
    Update for Microsoft Office 2016 (KB4018295)
    Update for Microsoft Office 2016 Language Interface Pack (KB4011731)
    Update for Microsoft OneNote 2016 (KB4011733)
    Update for Microsoft Outlook 2016 (KB4018296)
    Update for Microsoft Project 2016 (KB4011734)
    Update for Microsoft Visio 2016 (KB4011661)
    Update for Skype for Business 2016 (KB4011725)

    There were no non-security patches for Office 2007.

    [The KBNew list of all new and modified March KB articles has been updated, and now includes the March non-security Office patches. We’re showing more than 300 new and changed KB articles since March 1.]

  • Problems with yesterday’s Win10 1709 patch, KB 4090913, starting to appear

    Posted on March 6th, 2018 at 07:26 woody Comment on the AskWoody Lounge

    I’m seeing some reports of problems with yesterday’s Patch Monday single-purpose cumulative update for Win10 1709.

    Computerworld Woody on Windows.

    UPDATE: We have a report of the “reboot to black” bug in the Win7 Feb. Monthly Rollup KB 4074598.

  • Patch Lady – Servicing Stack Updates

    Posted on March 6th, 2018 at 00:48 Susan Bradley Comment on the AskWoody Lounge

    Patch Lady Susan here:  This will be a post whereby I don’t answer a question, but rather bring up many more questions. Firstly here are some OLD background posts on what is going on with the component based servicing process which is the underlying engine that does the installing and updating on a Windows machine since the Vista era.

    First read part one on Windows servicing from the Joscon blog.

    Then read part two on Windows servicing from the Joscon blog.

    And here another one to read as background material.

    Read all of those first.  It gives you a bit of background in how vastly Windows has changed in updating since the Windows XP era.

    For all of the times I track issues with patching, there is one truth in how we deploy now — assuming a healthy machine and a large enough hard drive, one can go from newly installed to fully patched in a much much shorter time frame than we ever could in Windows 7 era.  With a minimum of rebooting I can get a machine fully operational  – and even better – installed from scratch in less than an hour if the machine is peppy and has a ssd hard drive.

    Now that you have that background (and probably a bit of headache reading all that) I’ve noticed something recently with Windows 10 releases.  We are getting a servicing stack update about each time we get a patch for the platform.  Take today’s release to fix the USB issue in the form of KB4091913.  Concurrently with that release was a servicing stack update in the form of KB4091914.

    The increasing use of servicing stack updates just leads me to have more questions and not a lot of good answers.  Historically such updates were rare, not every release.  They are usually not uninstall-able, and help windows update do a better job.

    My concern is that once upon a time Microsoft mandated that every update could be uninstalled to allow you to roll back from any issue.  There have been some historical scattered reports of issues that occur after a servicing stack update has been installed. Conversely there have been times – especially on Windows 7 – where a servicing stack update has done wonders to speed up the install of updates.

    I’ll see if I can dig into why we’re getting these more often. In the meantime, keep an eye out for this and I’ll let you know if I see any side effects.