It's the only version that have any of those stupid metro apps or cortana, but that's just my reason for not bothering with any other version. Others are sure have different reasons.
many thanks for the new version and all your good work. i ran into a couple of issues running the script. 1. it couldn't access hosts file so i had to do that manually.. not a problem. 2. i removed all apps (option P). there was an error message on restart that windows had encountered a problem and needed to restart.. which it did with no other obvious problems. 3. i couldn't remove onedrive (option F) but the previous version worked fine. everything else went ok. (options U, W and D)
@slave77. Great job with latest update. How can I send Milk-Bones? Do have one request. [P] POWERSHELL PROVISIONED APPS ONLINE REMOVAL --> Manual. Be nice to see a list of what can be removed. An idea of what to manually type in. Too bad a select-able list control isn't part of DOS but I hope you get the idea. Koodoos to the pooch.
I've got a clean install of Win10 on a spare drive waiting to be configured so I'll be giving this a try out.
did all this info gathering or stealing info begin with 8 or has it always existed since windows 7? did it exist back in the day before sp1 for 7? anyone know anything about this?
From what I've read about this in threads & links. It went really bad on W7 SP1. But the level that they've gone on W10 is not tolerable by any means. Even if the OS is "free". Free by data slavery is still slavery.
I found the following lines trying to phone home using fiddler and I already have Metro completely disabled and am using Classic Shell, not sure where these were poking through. 127.0.0.1 blogs.msdn.com 127.0.0.1 msstomsdnblogs.112.2o7.net 127.0.0.1 i1.social.s-msft.com 127.0.0.1 i1.blogs.msdn.com 127.0.0.1 msstomsdnblogs.112.2o7.net I've ran nummerok's program and also have cortana, edge and runtimebroker completely killed (not able to run in the background at all, renamed) runtimebroker.exe (runtimebroke.bak) renaming prevents any metroapps from functioning. If you disable runtimebroker, have a replacement shell installed and in use, this will disable the 10 start menu altogether! disabling runtimebroker introduces a delayed startup, but from what I can tell, If you rename all of the SystemApps folders (C:\Windows\SystemApps) and make sure none are running, it reduces the startup time to where its a non existant delay. All privacy switches have been flipped as well. I've been keeping notes as well of my methodology and it also doesn't look like nummeroks prog didn't remove sc delete dmwappushservice (found this in reddit disable data guide) echo "" > C:\ProgramData\Microsoft\Diagnosis\ETLLogs\AutoLogger\AutoLogger-Diagtrack-Listener.etl (this line from the reddit guide was also shown as in use when trying to execute long after nummerok prog use. Had to log out, log in windows user account and try this line again before it took.) I apologize in advance for my nigh on illiterate notes, I wasn't planning on writing today. If you require any clarification, feel free to ask.
@s1ave77 Hi, nice coding... I have 2 suggestions: 1) Add to the host list a comment, so it is easier to find other stuff, for example: Code: # MS HOSTS 0.0.0.0 vortex.data.microsoft.com 0.0.0.0 vortex-win.data.microsoft.com 0.0.0.0 telecommand.telemetry.microsoft.com ... # END MS HOSTS Telemetry 2) Add a duplicate warning, for example (something like this) : Code: if hosts have "# MS HOSTS" then alert: "Hosts already there, do you want to add them again?" Cheers!
Nummerok's program does not kill cortana from running in the background (searchui.exe), I also have not tried powershell package removal. I killed Cortana in my first go around by going through linux and renaming Cortanas app folder to: (C:\Windows\SystemApps\[backup]Microsoft.Windows.Cortana_cw5n1h2txyewy) This can also be achieved by using the Take Ownership tweak, killing searchui.exe and renaming the folder, it will not able to run then. I personally do not have any use for any metro apps, so I have renamed every single folder inside of SystemApps dir to contain starting with [backup] in the filename. When it comes to runtimebroker, I originally started talking about it here (forums.mydigitallife[d0t]info/threads/63874-REPO-Windows-10-TELEMETRY-REPOSITORY/page28) (Located at C:\Windows\System32\) When I first discovered the runtimebroker option, I did not have all those folders in SystemApps renamed. I was hit with a longer start up time after typing my password. I noticed right about the time when i renamed all of the folders, I am not hit with that startup delay any longer. Please be sure you have an alternate shell installed like classic shell before renaming, killing and restarting. Do note that runtimebroker does sink its teeth in a little deeper than most modifications, minor functionality is lost but its not crippling and the extra added safety is worth having it this way imo. For example you can view the calendar by left clicking on the time, you would need to right click and go through a series of sub options through adjust time and date. It's whatever, I have a phone for that. Also, if for some reason you need to access the metro settings section, could right click on the clock > adjust date/time > and then just navigate to the gear icon in the upper left of the new window. Disabling runtimebroker is stable. When it comes to echo "" > C:\ProgramData\Microsoft\Diagnosis\ETLLogs\AutoLogger\AutoLogger-Diagtrack-Listener.etl - I am running a clean 10 Pro install, I used customized settings upon initial boot and i have a local account. I am not sure why I got a message along the lines of "that it was currently in use" but yes, I logged off the user account / restarted (can't remember) and then tried running the command again, it then worked.
Went through the guide, there's a lot of redundancy in the sub links it references to, but there's some minor unique material from those links, thank you for sharing. Fatboys host list looks a little too complete, it looks like it blocks out also Windows Update. I suppose if you're going to use a list like that, you're going to need a separate install to nab the Windows Updates and install manually. I highly recommend people try out the runtimebroker fix and straying away from the stock shell for extra added security. Also intrigued to hear peoples responses with that find. At some point in time, I want to do a Virtual Machine clean install and rewrite all of this information into one huge guide so its easier to thumb through. I'm also hoping that projects like nummerok's or something like TNBT could become more complete so that way the program is one touch solution and the guide is a mere checklist to confirm everything is disabling. Or, to test out software like NTLite or manually modifying the Retail ISO to automatically have all this taken care of so we can just focus on manually updating windows through offline installer files from there. Just tried removing cortana through powershell now, as far as I can tell, there's elevated packages that are not able to be removed through this method, or atleast the command I used. imgur[DOT]com/kdDRhAU