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...
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.
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
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?
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!
@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
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
Are the "SSU" (servicing stack update) the "Security Only" updates that you refer to that can be installed in lieu of the rollup update to avoid reinstalling telemetry? Thanks
@abbodi1406 thanks for your great work. How do you no Checking for updates to quickly hide KB in W10-Hide.cmd? Because the detection update is too long, I look forward to getting your answer
@abbodi1406 I do not have any previous experience working with Scripts or Scheduling Tasks. Could you please review and confirm my detailed steps below and let me know if these steps are the right and accurate (correct) way to use your W10-Block Script and Schedule Task processes??? W10-Block.cmd Script Step 1: Click and Drag to highlight (select) and Copy the Script Code found inside the Spoiler in Post #1 to the clipboard Step 2: Open the Notepad application and Paste from the clipboard the Script Code in a new file Step 3: Save the file as: - File Name: W10-Block.cmd - Change File Save as type: from Text Documents (*txt) to All Files (*.*) Note: (or alternately, save the script as a .txt file, then change the file extension to .cmd) Step 4 Run the Script: - Right Click on the File Name W10-Block.cmd - In the pop-up window, Click Run as administrator This will automatically and immediately start and run the Script and it will Disable the following: - DiagTrack Service - WMI AutoLogger Diagtrack Listener - Compatibility Appraiser-tasks - Customer Experience Improvement Program _______________________________________ Schedule Task for W10-Block.cmd Step 1 Make sure the W10-Block.cmd file is saved/located inside the Windows Folder in Drive C: (To check this, Click Start > Click Computer > Click C: > Double Click Windows Folder) Step 2 Copy the Schedule Task Code from Post #1 to the clipboard SCHTASKS /Create /F /RU "SYSTEM" /RL HIGHEST /SC ONSTART /TN BlockW10 /TR "cmd /c %windir%\W10-Block.cmd” Step 3 Open Command Prompt window as administrator Start > All programs > Accessories > Right Click Command Prompt A pop-up window will appear: Click Run as administrator A pop-up User Account Control window will appear: Do you want to allow the following program to make changes to this computer? Click Yes button The Administrator: Command Prompt window will open The last line in the window will be: C:\windows\system32>_ Step 4 At the blinking cursor, Paste from the clipboard (or type) the Schedule Task Code It should look like this: C:\windows\system32>SCHTASKS /Create /F /RU "SYSTEM" /RL HIGHEST /SC ONSTART /TN BlockW10 /TR "cmd /c %windir%\W10-Block.cmd” Press Enter key Now each time the computer is restarted/rebooted the W10-Block script will run to make sure anything that may have been re-enabled will be Disabled again. __________________________________________ Once you let me know I am doing this right, I will finally feel confident in being able actually proceed with Updating my Windows 7 machine as outlined in my Post #7439/7441 in the "Bypass Windows 7 Extended Security Updates Eligibility" thread that you so kindly helped me with.