News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Daily Archives: September 9, 2018

  • I’shanah tovah!

    Posted on September 9th, 2018 at 16:21 woody Comment on the AskWoody Lounge

  • Once again, KB 4023057 gets pushed out to all Win10 versions — and you don’t want it

    Posted on September 9th, 2018 at 09:32 woody Comment on the AskWoody Lounge

    I just switched off the metered connection on my production machine, and what to my wondering eyes should appear…

    KB 4023057 “Update to Windows 10, versions 1507, 1511, 1607, 1703, and 1709 for update reliability” isn’t available in the Microsoft Update Catalog.  Per the KB article

    Only certain builds of Windows 10, versions 1507, 1511, 1607, 1703, and 1709 require this update. Devices that are running those builds automatically get the update downloaded and installed through Windows Update.

    This update is also offered directly to Windows Update Client for some devices that have not installed the most recent updates. This update is not offered through the Microsoft Update Catalog.

    We’ve seen a patch with the same KB number numerous times in the history of Win10. @ch100 explained it thusly:

    KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it meant for unmanaged end-users and unmanaged small business users…

    This patch may be harmless, but why it was released and where it actually applies, it is still a mystery.

    The KB article was updated on Sept 6.

    My recommendation: Fuhgeddaboutit. When you’re good and ready to upgrade to 1803 (or 1809, or — in my case — 1709), let Windows figure out what it needs to pull you into the borg.

    UPDATE: Günter Born has a detailed description.

  • No, Microsoft has NOT “confirmed” a new monthly charge for Win7

    Posted on September 9th, 2018 at 06:36 woody Comment on the AskWoody Lounge

    I can’t believe the FUD.

    If you had a volume license for Windows XP, and you wanted to continue to get XP security patches after it reached end of life, you could pay Microsoft to extend the support. It was (and, I believe, still is) a monthly charge that gets larger over time.

    MS announced that they’re doing the same thing with Windows 7. Which shouldn’t surprise anybody.

    Windows 7 Extended Security Updates

    As previously announced, Windows 7 extended support is ending January 14, 2020. While many of you are already well on your way in deploying Windows 10, we understand that everyone is at a different point in the upgrade process.

    With that in mind, today we are announcing that we will offer paid Windows 7 Extended Security Updates (ESU) through January 2023. The Windows 7 ESU will be sold on a per-device basis and the price will increase each year. Windows 7 ESUs will be available to all Windows 7 Professional and Windows 7 Enterprise customers in Volume Licensing, with a discount to customers with Windows software assurance, Windows 10 Enterprise or Windows 10 Education subscriptions. In addition, Office 365 ProPlus will be supported on devices with active Windows 7 Extended Security Updates (ESU) through January 2023. This means that customers who purchase the Windows 7 ESU will be able to continue to run Office 365 ProPlus.

    The security patches will only be offered to organizations with increasingly deep pockets.

    Microsoft didn’t “relent.” It isn’t a “new monthly charge.” They didn’t “change software update strategy.”

    Sound and fury.

    UPDATE: Gregg Keizer has the whole, accurate story on Computerworld.