Newsletter Archives

  • Patch Lady – new releases for Windows 10

    Patch Lady here – if you were a “seeker” or were offered up the updates on or around September 20th and caught KB4458469 for Windows 10 1803 earlier this month, there’s a rerelease of that update due to… and I quote “because of a missing solution.

    Also rereleased today is KB4457136  for Windows 10 1709 … also rereleased due to a missing solution.  None of the other platforms have received these rereleased updates.

    Note it doesn’t go into detail what the “missing solution is”.

    It would be nice if there was a teensy weeny bit more clarity and a better explanation of what solution was missed so we know if we need it.

    Definitely we need more clarity and transparency.

    UPDATE: There’s a summary and a few new details at Computerworld Woody on Windows.

  • Help us unravel the Win10 updating Gordian knot

    For those of you running Win10 version 1709 and 1803… I’m trying to figure out under what circumstances people are getting upgraded to the latest versions, 17134.319 and 16299.697 respectively.

    It looks like “seekers” — those who manually clicked on “Check for updates” — were upgraded, but only if they “seeked” (sought?) on Thursday, and (?) they had defer quality upgrades set to 0.

    If you manually downloaded and installed the cumulative update, well, you got what you asked for. If you’re attached to an update server, your admin gets to tear their hair out. I’m interested in knowing what’s happening to everybody else.

    Computerworld Woody on Windows.

  • More WSUS Sync failures

    Those of you working on update servers over the weekend have my sympathy.

    There’s a lot of confusion over last Thursday’s KB 4458469 cumulative update for Win10 1803, KB 4457136 for 1709, KB 4457141 for 1703, and KB 4457127 for 1607. As best I can tell, all of those patches have been pulled — except they’re still in the Update Catalog.

    To add to the mayhem, we have this report from @nazzy:

    Getting intermittent sync failures again starting 9/17 for both scheduled AND manual syncs.  Can anyone else confirm?

    and from an anonymous poster:

    I can confirm that It was working up until 9/21/2018 then all day today (22 Sept) fails WSUS sync

    Of course, a big chunk of Microsoft staff is in Orlando, getting ready for Ignite. Are we going to see any sort of resolution on this in the near term?

    Great way to treat your corporate customers….

  • Massive bug fixes for Win10 1803, 1709, 1703 and 1607

    A bunch of cumulative updates for Win10 just hit:

    • KB 4458469 takes Win10 version 1803 to build 17134.319
    • KB 4457136 turns Win10 1709 into build 16299.697
    • KB 4457141 moves 1703 to build 15063.1358
    • KB 4457127 transforms Win10 1607 and Server 2016 to build 14393.2517

    Each of the cumulative updates includes dozens of patches for what appear to be minor bugs.

    We were also graced with the Preview Monthly Rollups for Win7 and 8.1:

    • KB 4457139 Win7 Preview of next month’s Monthly Rollup
    • KB 4457133 Win8.1 Preview of next month’s Monthly Rollup

    All of them — which is to say, all of the Win10 cumulative updates and the Win7/8.1 Monthly Rollup Previews — include this little telemetry gem:

    Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.

    Let’s see. This is “C Week” Patch Thursday, right?

    There’s a reason why we’re still at MS-DEFCON 2.

    Looks like the regular team got back from vacation….