Newsletter Archives

  • Mysterious re-release of KB3150513 – on Windows 10, no less

    This in from DP:

    I just rec’d notification of the above update on my Win10 system yesterday. I am running ver. 1511, build 10586.545. I have searched around the web trying to find out what it’s going to attempt to do to my system if I download and install.

    I found all the articles around May of 2016, but nothing this recent. I found some users at The Windows Club who got the same KB within the last day or two expressing some concern, but no one seems to know what it will do to Win 10 system. I’ve used the Group Policy Editor to control updates and haven’t gotten the AU update notice yet. Could KB3150513 be Microsoft’s attempt to entice the AU on me?

    Thanks for helping. Your Windows 10 book for Dummies is the best, BTW.

    I’m not seeing it on my Win10 1511 machines, but it’s starting to pop up all over the web. The KB article was last updated today.

    Anybody know what’s up?

  • What are the differences between KB2952664, KB3150513 and the naughty KB3035583?

    A very interesting synopsis from our very own ch100:

    What are the differences between KB2952664, KB3150513, and the naughty “Get Windows 10” patch KB3035583?

    KB2952664 (and its equivalents for other OSes and versions) is the baseline pre-requisite for all the others providing the telemetry baseline. It is mostly useful for the upgrading to Windows 10, but not only as it provides telemetry capabilities in a wider sense.

    KB3150513 is not offered unless the previous one is installed and adds further functionality in relation to making Windows 10 upgrade more reliable. It has specific functionality in relation to applications compatibility and this is why is offered as a different KB number.

    KB3035583 is purely adware/nagware, the bad guy which is neutralised by the Group Policies configured to do that or by Josh’s GWX Control Panel, or Steve Gibson’s tool, or Noel’s procedure.

    What I find relevant is that the first 2 patches are offered to medium/large businesses running Enterprise Version or Enterprise/Pro + WSUS, while the last one KB3035583 is never offered to those businesses. They are the most important customers for Microsoft’s bottom line.

    Which makes me think that, unless overly concerned about the telemetry issues, the other patches are not so damaging or annoying and may actually provide some benefit in certain instances. The larger businesses seem not to pay much attention to the telemetry issues and follow the official line from Microsoft. If anything, the communication back to Microsoft is blocked for network traffic and OS performance reasons and rarely for the content of it. The larger businesses are not typically offered an upgrade in place and are still offered KB2952664 and KB3150513 and maybe there are more to come.

    There is certainly no benefit at all in installing KB3035583 unless and only if interested in doing in-place upgrade to Windows 10.

    Even so, I upgraded long before all those patches mentioned here were released and my upgrade still completed successfully and I did it more than once. The three patches are just risk mitigation patches, not mandatory if upgrading from sources other than Windows Update, like the official ISO image. And it is actually a lot more reliable to use the ISO than Windows Update.

  • Microsoft releases another undocumented Windows 10-enabling patch, KB 3150513

    It took a Polish poster on Microsoft Answers to explain that it’s an update to the Win10 compatibility appraiser.

    InfoWorld Woody on Windows