I ended up getting that update on my G3258 Win 7 machine and had to roll back the update using System Restore because my machine would not boot. I couldn't install 10 because the MC update is built-in to 10 until I found the info out, then disabled my OC and turned off 1 CPU core so I could install, and then I renamed that MC DLL and turned back on my OC & 2nd core and it worked fine afterwards. I've lost some faith in Intel with these shenanigans, because G3258 was supposed to be an OC-friendly CPU, but they MC update disables most motherboards' abilities to OC that CPU short of maybe a Z97 which is garbage. All along, H series dating back to even older chipsets (ie H81) could OC the G3258; my H97 Performance can now but if I update the BIOS, it can't anymore (due to the MC update). Again, that's garbage. This shouldn't be an issue and it should never have happened. You sold a CPU with OC merits and then you pull the rope back? Very shady bait and switch.
So on my Windows 7 PC today, I restarted it to play with a Linux Mint DVD and noticed that there were updates configuring. I know that I had set updates to never check. When I checked the settings, it was set to automatic download and install. I had to remove about 5 unwanted updates that I had previously already uninstalled. That's it, I'm completely done with Windows. I will try to keep this thread updated going off of info provided by members.
I had that happen to me a month ago. Somehow, the updates settings had changed themselves. Crazy. This is an important thread, IMHO - I hope it does stay updated or someone else makes one to continue this important information portal for this topic. Thanks for all of your hard work.
That's bad. I ran hide updates script and then installed rest of updates. KB3035583 installed even if it was hidden. The KB3035583 just show up twice, so needs to be hidden twice too... Not sure if to install KB3083710. //installed UninstallUpdates.cmd Code: @echo on wusa /uninstall /kb:xxxxxxx /quiet /norestart wusa /uninstall /kb:xxxxxxx /quiet /norestart pause
Windows Update Client updates has nothing to do with telemetry the only "negative" affect they provide is facilitating the upgrade to Windows 10 it's msft itself that announced that KB3075249 (as example) adds telemetry points to UAC, or we wouldn't even know that what i mean is, nothing prevent them from announcing the same with WU clients if they actually telemetry-related
I created empty GWX folder in C:\Windows\system32\ and set permissions to Deny Everyone. The GWX update should fail to install
The update didn't change anything for me, both disable gwx and upgrade policies stands still people should stop setting auto updates if they don't know how to handle it