Hey, Master__Shake, coming in from the latest Windows 10 nagware news thread
, I'll repost the first part of my last post there in here for reference's sake so it doesn't get lost in the ever revolving news section:
Thanks for the info, good to have a centralized place to keep track of these things. I only now had time to research into the ones on the list you provided that I hadn't listed. Turns out I have some of them unchecked (thus not installed) and forgot about it (such as the Update for Universal C Runtime in Windows - KB2999226, which may be useful one day, but it's not really needed for now). Anyway, I have observations about five of them:
KB3060746 - You can't open the "Devices" menu in PC Settings in Windows 8.1 or Windows Server 2012 R2
- Not related to Windows 10 or telemetry, it shouldn't appear for Windows 7 users anyway.
KB3083324 - Windows Update Client for Windows 7 and Windows Server 2008 R2: September 2015
- Quite a lackluster description, not directly implicated in this whole get Windows 10 or telemetry business, but yes, it's dubious.
KB3083710 - Windows Update Client for Windows 7 and Windows Server 2008 R2: October 2015
- Same thing.
KB3095649 - Win32k.sys update in Windows: October 2015
- Doesn't seem to have to do with telemetry. Has three fixes, one for Windows 7: Fixes a crash in Win32k.sys in Windows 7 SP1 or Windows Server 2008 R2 SP1.
KB3102810 - Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2
- This one may not be problematic, but the instances it corrects (see below) don't necessarily apply to everyone, so I guess it's optional
When you install updates by using System Center Configuration Manager, the installation
takes a long time, and System Center Configuration Manager becomes overloaded.
The Svchost.exe process occupies 100 percent of CPU usage when you upgrade a Windows Update client to Windows 10.
I couldn't help but notice that strange sentence in the end "when you upgrade a Windows Update client to Windows 10" - what does this mean? Could the two updates mentioned above with a lackluster description have anything to do with it?
As to the rest, no observations or objections, all should be off the system.
Oh, and I just noticed what you also posted in your thread. They re-published the now super infamous KB3035583 GWX nagware. How many times are they going to do this? It's getting ridiculous. Aren't they getting the message? People that hid it once shouldn't be seeing it again. This just aggravates the annoyance and will make people even more upset about their pushy attitude while seeing that they are not addressing people's concerns. It does everything but convince people to install it or Windows 10.
I had already hid it once, I'll have to do it again. Good thing that I unchecked the box about recommended updates being installed the same way as important ones. That is, until the day that they re-issue it again as an important one. I'll want to see the look on their faces the day that they step down to that level. In any case, I already have the updating system on manual, so no problem in the end.
It's just unfortunate that to keep using Windows 7 as we want we have to spend time and effort dealing with this. I don't know if Microsoft realized already the dents this is making in the trust relationship with their customers. Then again, looking on the bright side, we are now more aware of this kind of stuff and taking control, so in an ironic twist I guess we should thank them for that lol.Edited by tpi2007 - 12/21/15 at 6:49pm