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
  • MS-DEFCON 2: Time to temporarily block Windows Update – and ignore KB 3008923

    Posted on May 8th, 2017 at 14:32 woody Comment on the AskWoody Lounge

    Check to make sure you have automatic update turned off.

    InfoWorld Woody on Windows

  • “Invoke” to challenge Amazon Echo, Google Home?

    Posted on May 8th, 2017 at 09:11 woody Comment on the AskWoody Lounge

    I’ll reserve judgment until I’ve had a chance to play with Cortana on the new Harmon Kardon speaker.

    But “Invoke”? Gawd. Is that the best Microsoft marketing could come up with?

    I just asked my Google phone “What is invoke?” and the answer is… “the antiquated defense of insanity is rarely invoked today…”

  • “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again

    Posted on May 8th, 2017 at 06:27 woody Comment on the AskWoody Lounge

    UPDATE: InfoWorld Woody on Windows

    I’m seeing it on my main production machine, too. It shows up on the list of installed updates (installed 2 May), but also appeared this morning on the list of updates ready to install.

    Poster Neil Hobbs on the Microsoft Answers forum says:

    If you have a look at the update in the Microsoft Update Catalog at the following URL, you’ll notice that it has been updated – the name and the KB reference has been updated;

    https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=a9262201-26d9-464b-ab32-106e4652db0c

    Therefore the reinstall is due to this.

    Sure enough, the Microsoft Update Catalog shows it was last modified on May 4. If you go to the usual Update Catalog URL, you can see three different versions of the update, for 32-bit and 64-bit Win10 1607, and one for Server 2016 64-bit.

    On April 24, I wrote in InfoWorld about the new version of 3150513 being pushed onto all versions of Windows.

    Then on May 2 I talked about Günter Born’s discovery that there was a re-issue of KB 3150513 for 1607 only. A look at the KB page turned up key files dated April 27.

    Now, when I look at the KB page, I see that the key files were updated again, this time on May 3.

    The weird terminology — starting with “2017-05 Update …” throws off alphabetized lists of patches, as noted by NetDef yesterday.

    Günter Born has a rundown of more problems with KB 3150513 and KB 4015219 (the Win10 1511 cumulative update). According to the Update Catalog, both were re-issued on May 4. The last official cumulative update for 1511 appeared on April 11. This new one’s undocumented, as best I can tell.

    It would be interesting to know if this latest cumulative update for 1511, dated May 4, increments the build number above 10586.873 (which is the official build number for the release on April 11). If the number has been incremented, I don’t see any reference to it, anywhere, official or unofficial. If the number has NOT been incremented, somebody is playing fast and loose with the build numbering system.

    Sounds to me like somebody screwed this one up big-time.