-delete- The message you have entered is too short. Please lengthen your message to at least 10 characters.
I don't care who uses stuff in the script. You're welcome to use the various commands or even the menu system and stuff. I'm actually more interested in the various methods and whether or not they block the telemetry and/or keylogger stuff.
i briefly ran the script yesterday and if i remember ( was tired ) the diagtrack service didn't stop, but i ran it on a VM that i was editing. so installed a fresh copy and will give it another stop. have to see what other evils lurk in the registry. also, a quick note. on the sysprepped administrator system. the upload task in task scheduler wasn't installed, and nothings being created in the C:\Users\All Users\Microsoft\Windows\Sqm folder. have to check if i disabled CEIP in my unnattend file.
No, that will not be the main thread. It will just be the storage thread so I don't have to update multiple threads.
Ok I've synced up both the Powershell Script and Command line script. Also synced up the version numbering to reflect that. It makes it more obvious they are in the prototype phase. I uploaded 0.10 and 0.03 to media fire as well. Please note that the numbers are reflective of the current build they are on.
I have deleted both dmwappushsvc, diagtrack files from System32. Now both services has stopped running . Now I wanna know whether I am free of tracking or not ? here's the screenshot
You knew what to expect when you started Testing Windows 10. This is not about taking extreme actions on a product that is still being developed. It is about taking reasonable actions in order to explore what is being collected. While making an effort to do an analysis of how it is done in order to put something together to take care of it.
O ya we should probably put a build number check in so that it only applies to builds greater than 9651 UPDATE: Scratch that I'm going to use the 6.4 statement. We can use the gmic for the power-shell which is done.
[Edit] Hoping somebody can help me with this. Does anyone know what controls the All Application Packages privilege. If you go into any of the permissions for any of these registry keys and delete it, it rewrites itself. Not sure but i believe that's the only one that does that. Since what i'm doing has to do with the "keylogger" that's why i'm asking here. i wrote a script to disable dmwappushsvc without a restart. Since SMorgan is more knowledgeable i'm gonna use his script, but i started on mine just because i hate when anyone ( MS ) says it can't be done, and i figured why not try it. Anyways, i run the script, and everything works as planned ( the service stops ), but then it restarts. Go into regedit ( HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dmwappushsvc ) and delete the All Applications Packages privilege, and it rewrites itself. Kill the service, it restarts, and go back to regedit, delete the privilege, it restarts. blah blah blah. On the fourth attempt ( always the fourth ) killing the service sticks. My question, if anyone knows, is why the fourth attempt and not the the third, or sixth, or whatever. I think it might be because dmwappushsvc is part of a grouped service in svchost, but i'm not sure. I've got to play around some more. If anyone could shed some light on this it would be greatly appreciated.
Actually now that you mention it I have heard of this happening. When I was playing around with the licensing for various Microsoft Products some of them actually do what you mentioned. A perfect example of this is actually the WPA registry keys. If you try to delete them they are rewritten over and over again. The fun part is that most of the time Microsoft's Beta products have a bunch of loop holes in them in terms of stopping the stuff that does this. MY advise would be to kill the dmwappushsvc then additionally write into the start entry the number 4. This will effectively tinker with the Service start information making it disabled. I would not worry about the service host all that much as its just the man that makes it all run. I imagine if you kill the service while modifying the start settings immediately there after it will not start again. I actually like tinkering with the registry as its funny how many settings are stored there.