Two different things, really: MysTikAL3 has 2 scripts - a CMD and a VBS script (in his link); that is essentially the only way to hide the updates via script. His CMD script does more than just remove the updates - it also edits the hosts file and calls upon the VBS script to then hide the updates (after they've been removed by the CMD portion). My script just removes the updates; it does not hide them in the future, or tweak anything else (hosts file for instance). I prefer to take the more 'surgical' approach myself and pick and choose what I do/remove. I'm familiar enough with the hosts file to be able to do that manually; I'd also prefer to just hide the updates manually. MysTikAL3's scripts are more of a one-stop-shop whereas mine is more 'fine-tooth-comb'. Mine is just for removing all the known/suspicious updates in bulk, with no other tweaking done.
At this point I've ditched Windows Update and the Security Center altogether since the Windows Update Client module is identified as being hostile since at least July 2015. Hiding bad updates was always so shaky in the Security Center also. Now that I've gone over to manual updates, I figure that screening for critical security updates will be the only real effort. I don't expect much in the way of major feature updates for Win7 since it's getting so heavily sidelined. But I wonder what are the prospects for successfully installing future updates since we can no longer trust installing the current Windows Update Client module. Should we expect to encounter failed KB installations at some point?
That's to be expected since it's out of mainstream support now. Consider the possibility that the WU client update (like many others in this thread) being classified "hostile" is BS, and you'll be fine.
Official KB description of most recent WU Client release indicates otherwise: This update enables support for additional upgrade scenarios from Windows 7 to Windows 10, and provides a smoother experience when you have to retry an operating system upgrade because of certain failure conditions. This update also improves the ability of Microsoft to monitor the quality of the upgrade experience. SOURCE: support.microsoft.com/en-us/kb/3112343 (06JAN15) It's plainly identified that WU Client has been converted into a Win10 update mechanism. What I wonder is if subsequent security updates could get roped into requiring latest client version to install properly. Wouldn't think that would be likely given number of commercial entities still using Win7, but incentives for M$ to deploy latest OS may simply be greater than good sense.
That's ridiculous. Of course the WU client got updated to support an OS upgrade through WU, and of course that functionality is going to be in any future version to come. So? Guess what, the new client also comes with GPO templates that make upgrade blocking configurable through group policy. How "evil" is that? The updated client even applies to platforms and SKUs that won't ever see an OS upgrade, such as ARM, IA-64, Server and Embedded. Big deal.
Which thus far has been widely reported & proven to be turned back off by Microsoft despite the user enabling this functionality in GPO. WU Client updates have never been a requirement to install updates; if they were, you wouldn't be able to install per KB, download KB's, or mass install KB via the wusa command without the client update being a prerequisite first. Not saying you need a tinfoil hat, but if it smells like BS and looks like BS, it's BS. They can continue these antics, and I can continue any and all attempts to circumvent the BS and sabotage they're trying to put into their product that I paid good money for in order to use and be supported with for another 4 years.
Thanks for your post. I just wanted to note that KB3035583 was also unhidden & marked as optional on this go-around. (otherwise our lists were the same) ((yes I know it's prob "just" a new version, semantics blah))
Hi, I used the link from your sig. and got rid of the telemetry for the time being but the office 2013 pro/visio pro/project pro has stopped updating too, since Nov 2015. Has the tool used for stopping the windows telemetry caused the office update stopped permanently? Is there any solution to get the office update back to normal? Thank, sid_16.
hi thanks for list i noticed these updates yesterday i allowed KB890830(Malicious Software Removal Tool) &KB3124275(Cumulative Security Update for Internet Explorer 8 for Windows 7)[FONT=wf_segoe-ui_light] [/FONT] also KB2952664 republished 12/1/16 (that in optional tab of WU) any of above is related to telemetry ? safe to install ? my hidden updates Spoiler
error 0x80070057 after removing telemetry Thanks to informations found here, I removed telemetry and W10 related KBs from my W7 computer. However, Windows Update got broken in the process : it now fails to download any further updates and puts a 100% load on the CPU. The Windows Update Troubleshooter (kb2714434) cannot fix it and insistently reports a 0x80070057 error. Various Microsoft "fixit" scripts related to that error failed to solve it too (kb929833; kb947821; kb968003; kb949104; kb2700567). Sorry for not providing links to these KB but the editor of the forum prevents me to do so. What should be my next steps ? Fix Windows Update in order to keep my computer in the mainstream ? That's what I would prefer to do. What is the right place in the forum to ask for support on that issue ? Resign from using Windows Update altogether and start to install manually the next updates ? Is it realistic ? How to check Microsoft repositories for new updates ? Thanks for any guidance.
Pretty sure the log files and/or event log entries have something to say about it. WU client as well as CBS keep logs of everything they do, so I'm sure investigating the logs can help determine where it gets stuck. It just seems the practice of investigating problems this way (as opposed to bitching online about it) is getting more and more uncommon. Hey, I've got nothing against serious discussion that is based on real arguments. My own experience has been that it can take a long time updating from SP1 media, and that installing updates in large batches often leads to failures (though not in way that is breaking the OS), which is why I'd suggest doing it in smaller batches. However, I have not recently had to do any installs from original SP1 media. I keep a customized baseline image for use with sysprep that I occasionally update, so I usually can avoid going through the myriad of updates after install.