Disable/Remove Telemetry and Tracking Service

Discussion in 'Windows 7' started by abbodi1406, Feb 10, 2016.

  1. oldsh_t

    oldsh_t MDL Expert

    Dec 23, 2009
    1,076
    529
    60
  2. Logon

    Logon MDL Novice

    May 31, 2008
    10
    3
    0
    Yep, but sorry to say that in the scenario you described then the bat file produces an error and does not run at all (just as other users seem to have already pointed out).
    Creating the exe just as I described indeed it does work like a charm.
    At least here...
     
  3. oldsh_t

    oldsh_t MDL Expert

    Dec 23, 2009
    1,076
    529
    60
    What ever you say.
     
  4. Logon

    Logon MDL Novice

    May 31, 2008
    10
    3
    0
    Just tried again and you're right: the bat file does work the same.
    I don't know why it didn't work this morning.
    However, the exe conversion could still be useful if one wanted to hide the console window creating the exe working in invisible mode.
     
  5. oldsh_t

    oldsh_t MDL Expert

    Dec 23, 2009
    1,076
    529
    60
    Now this will work in both ways, but will it? You may want to check this out and read a few posts onward.
    https://forums.mydigitallife.net/th...nd-tracking-service.68131/page-5#post-1331122
     
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,912
    62,507
    340
    It's the same for both and works for both
     
  7. crypticus

    crypticus MDL Senior Member

    Jun 29, 2015
    286
    95
    10
    does it work for windows 10 and windows 11? can you update the script for new features and updates? also does it disable telemetry that is asked during windows setup's last stage?
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,912
    62,507
    340
    No
    Windows 10 Telemetry is deeply baked in the system
     
  9. bigbudd911

    bigbudd911 MDL Novice

    Jan 15, 2016
    3
    2
    0

    Just hoping for some clarification from anyone who can assist:

    - What is the difference between the 'De-Telemetry Package' posted above (post #266) and the one posted in the OP?? I notice the one in the OP was updated in 2019, while the one in post #266 seems to be from 2020.

    In regards to the guide/tutorial on the OP, I am wishing to do option #1 - disabling/blocking telemetry from working (as opposed to option #2 - outright removing it), so I can get all the newest updates and hopefully leave Windows Update set on 'auto update' (The PC is for a family member who isn't very good with computers so having updates set on auto is a real plus).

    *** Considering I am going to do 'option #1' (disable telemetry), should I be using the script posted in the OP (2019) or should I be using the script in post #266??


    Any clarification would be greatly appreciated,


    Thanks so much!
     
  10. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,912
    62,507
    340
    #311 abbodi1406, Oct 22, 2021
    Last edited: Oct 22, 2021
    (OP)
    @bigbudd911

    The OP method disable telemetry via regular registry values and schedule tasks
    but newer Monthly Rollups could revert some of these changes

    the De-Telemetry Package suppress the telemetry components themselves (i.e. they will never be active)
    but it must be installed from offline session

    as noted, 2) removing telemetry updates is no longer effective
    even some Security Only updates contain telemetry components
     
  11. bigbudd911

    bigbudd911 MDL Novice

    Jan 15, 2016
    3
    2
    0

    Thank you very much! I really appreciate the clarification.


    You the best! :D
     
  12. bigbudd911

    bigbudd911 MDL Novice

    Jan 15, 2016
    3
    2
    0
    #313 bigbudd911, Oct 23, 2021
    Last edited: Oct 23, 2021
    I seem to have figured out (and fixed) why the script doesn't work (startup) on a bunch of our PC's..... for some reason, the "SYSTEM" user doesn't work properly (google search seems to indicate this is a problem for some). Also, it's set to only run when plugged into AC power, so laptop users who aren't plugged in (battery only) probably won't get the script to run either.

    THE FIX:
    Go into the Task Scheduler, and edit the task (after creating it) and change the following:

    - In the 'General' tab, change the user running the script from SYSTEM to ADMINISTRATORS (make sure you don't choose 'administrator' unless you've activated that account)

    - If your PC is a laptop, go to the 'Conditions' tab and Uncheck 'Stop if the computer switches to battery power' and 'Start the task only if the computer is on AC power'

    - In the 'Triggers' tab, click on 'Edit' and make sure 'Begin the task' it's set to 'At Startup' and ONLY the 'Enabled' box is checked. Uncheck ALL other boxes.

    - Click OK to save the changes + Reboot


    Doing this, I was able to run the script with both the 'timeout' line included and not included - and I was able to clearly see the terminal window for both upon login. However, my user account currently auto logs in and I'm using an SSD so there's very little delay - so I might be getting lucky to see it without the 'timeout' line. I set timeout to '1' instead (doesn't stick around as long).


    Hopefully that helps all you guys who also couldn't get it to run! The 'System' user and 'AC Power' options are probably what's screwing with some of us!


    Cheers


    EDIT: Grammar & Spelling