My understanding is that to disable the service authentication if the system has Enterprise proxy it's not to disable the whole telemetry
Am I correct in thinking that if I want to be as aggressive as possible with these scripts on a fresh install of win 7 sp1 with office 2010 and the simplix pack I should do the following in this order: 1. Install win 7 sp1 2. Run 'W10-Hide.cmd' to hide the undesirable updates 3. Run 'W10-Block.cmd' to disable telemetry settings before any related updates can be installed or any settings can be established. 4. Install Office 2010 5. Install the simplix pack 6. Run Windows Update and install all the Office 2010 updates 7. Run 'W10-Block.cmd' again to disable any telemetry settings that may have been set after installing the simplix pack or Office updates 8. Run 'W10-Uninstall.cmd' to ensure that if any undesirable updates sneaked through they're uninstalled 9. Run 'W10-Hide.cmd' again to ensure that if any of the undesirable updates have reappeared they are hidden again I want to stop as many telemetry updates as I can from getting on my system in the first place, that's why I'm thinking I should run them in this order with both the hide and block cmd first. Is this the correct order for doing this? I assume I need to run the block.cmd again after installing the simplix pack and office 2010 updates but before the uninstall.cmd to ensure the settings are applied to any telemetry updates after they're installed but before they're removed? My reasoning for this order could well be flawed as I've either read a lot of conflicting info around the web or I just don't understand the whole telemetry update issue enough, so any help offered in getting this in the correct order is greatly appreciated. Thanks!
Heyho, At first, good job for this very nice thing! I have just waited to see something like this and recommending the thread to friends now. Iv got a problem right now. Im doing this in a VM, first try all was successfully and quick. But right now, another installed one (with latest simplex) suddenly hang forever at "checking for updates"(by hide.cmd). Any Ideas?
Yea, after I tried manual installing few updates and this throw me a Window "searching for updates" (which is also hanging), I decided to start new again now. I had to do anyway because the new December-Simplix, I integrating it and try again the scripts then, hopefully working well again. My way: 1. Integrating Simplix in install.wim and installing in a VM. 2. KUC for new updates (maybe unneeded after the new december release) 3. The Scripts: 3.1 W10-Uninstall.cmd and W10-Uninstall2.cmd (I included some other [probably superseded] spy-related updates) 3.2 W10-Hide.cmd and W10-Hide2.cmd (same as 3.2.) 3.3 W10-Block.cmd and W10-Block2.cmd (included some extra tasks) 4. Prepare other few things and do sysprep/dism for recapture install.wim. 5. Use NTLite to remove any spy/remote-related stuff (and some other personal prefer) Done. I'm looking for ways to do all these automatic without user actions, maybe 1 big script for dism.
Where are W10-Uninstall2.cmd, W10-Hide2.cmd, and W10-Block2.cmd from? As far as I know they aren't included in the first post.
installed GWX in Control Panel to deal with the Win10 as well as install fiasco and you will seet that it will be working nicely.
afaik windows 10 free update has ended, so i still need to run these scripts related to windows 10 telemetry? Is microsoft still diving deep into windows 7? i just completed a fresh win 7 installation and installed convenience rollup update, should i run this script now?
Yes, you need the block script, because telemetry diagtrack service is included in the Security Monthly Quality Rollup, which you can't/do'nt need to avoid just for that