Also, can I ask you what is the Convenience Rollup? And, I know it has been said on this thread not to install KB2952664. Where is KB2952664 found? I have my Windows Updates set to Automatic Updates with the "recommended updates option" set to off. Will allowing these updates NOT install KB2952664? By the way, if I manually run W10-Block.cmd, I do see it for a second or two. But, it doesn't look like it is running through the task scheduler as can be seen in my previous post where I uploaded a captured screen of my Task Scheduler and you can see the (0x1) result which I assume means it is not running from the scheduled task?
Yes copy and paste at the end of the code then "Save" the file. It is just a timer to slow down the .cmd so you will notice it. Then run it manually and see how long it takes, then reboot and see if it pops up and takes the same amout of time. If it does not then it is not being executed through the task Scheduler. AS for any bad updates run the W10-Uninstall.cmd and it will get rid of them including KB2952664 if it is on your computer.
abbodi1406, Here is something that maybe you can comment on. I originally downloaded W10-Block.zip and extracted W10-Block.cmd from it which is dated as modified on October 18th, 2016 (size = 3.10 KB). That gave me the error (0x1) when I set it to run in the Task Scheduler. Then, I downloaded PreventW10_20160715.zip and extracted the file W10-Block.cmd from it which is dated as modified on February 19th, 2016 (size = 5.82 KB). This gives me success (0x0) when run through the Task Scheduler. See attached photo. Can abbodi1406 tell me what is the difference between both of these files with the same name of W10-Block.cmd? I have success through the task scheduler every time with the older dated file (February 19, 2016), but the newer dated file (October 18th, 2016) fails every time through the Task Scheduler. Can I just use the older dated W10-Block cmd file, or does one need to be using the newer dated file? I am curious if there is some difference(s) between these two file dates of W10-Block.cmd, and why I only have success with the older dated file version.
I have no issue, both are ran successfully for me through schedule task tested on Windows 8.1, maybe Windows 7 has something different you may change the task trigger to be on system startup Code: SCHTASKS /Create /F /RU "SYSTEM" /RL HIGHEST /SC ONSTART /TN BlockW10 /TR "cmd /c %windir%\W10-Block.cmd" or edit the script and remove these two lines Code: takeown /f %ProgramData%\Microsoft\Diagnosis /A /r /d y >nul 2>&1 icacls %ProgramData%\Microsoft\Diagnosis /grant:r *S-1-5-32-544:F /T /C >nul 2>&1
Wanted to say thanks for this awesome Script! If I understand correctly on a new install of w7 sp1 with updates from the sept 2016 simplix pack, I should be telemetry/spyware free, I should just run the W10-block after the monthly roll up updates?
Abbodi1406, I first tried changing the trigger to be on system startup, but that was unsuccessful. Then, I deleted the two lines of the script as you posted, but no success. Lastly, I tried changing the both - the trigger and the script. No success. I replaced the W10_Block.cmd with the earlier version with the modified date of February 19, 2016 and that was successful. Can I use the older W10-Block.cmd script, or do I need to use the newer version? For some reason I can not get the newer version script to work, but that older version works every time. If it helps, my system is Windows 7 Professional 64-bit. Maybe you can figure out someway for me to use the newer version script? Thanks again abbodi1406 for your suggestions.
One last try, change ControlSet001 to CurrentControlSet if that did not work, then you may use the old one, it's good enough
I tried replacing ControlSet001 with CurrentControlSet in the three lines of the script where it appears. Unfortunately, I still received a message of (0x1) in the Task Scheduler. I will use the older version then of W10-Block.cmd and I hope that will definitely keep Windows 10 off of my system. Thank you again abbodi1406 for your time and suggestions in trying to help me out.
@socrates007 I had the same problem as you and I fix it by adding last few lines from PreventW10_20160715 to W10_Block.cmd : Spoiler @echo off %windir%\system32\reg.exe query "HKU\S-1-5-19" 1>nul 2>nul || goto :eof echo. echo Processing telemetry blocking tweaks reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v DisableOSUpgrade /t REG_DWORD /d 1 /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /f /v IncludeRecommendedUpdates /t REG_DWORD /d 0 >nul 2>&1 reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade" /f >nul 2>&1 reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade /v AllowOSUpgrade /t REG_DWORD /d 0 /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser" /v HaveUploadedForTarget /t REG_DWORD /d 1 /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\AIT" /v AITEnable /t REG_DWORD /d 0 /f >nul 2>&1 reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\ClientTelemetry" /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\ClientTelemetry" /v DontRetryOnError /t REG_DWORD /d 1 /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\ClientTelemetry" /v IsCensusDisabled /t REG_DWORD /d 1 /f >nul 2>&1 reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\ClientTelemetry" /v TaskEnableRun /t REG_DWORD /d 1 /f >nul 2>&1 reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags" /v UpgradeEligible /f >nul 2>&1 reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser" /f >nul 2>&1 reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TelemetryController" /f >nul 2>&1 sc.exe config DiagTrack start= disabled >nul 2>&1 sc.exe stop DiagTrack >nul 2>&1 reg delete HKLM\SYSTEM\ControlSet001\Control\WMI\AutoLogger\AutoLogger-Diagtrack-Listener /f >nul 2>&1 reg delete HKLM\SYSTEM\ControlSet001\Control\WMI\AutoLogger\Diagtrack-Listener /f >nul 2>&1 reg delete HKLM\SYSTEM\ControlSet001\Control\WMI\AutoLogger\SQMLogger /f >nul 2>&1 reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\DiagTrack /f >nul 2>&1 reg delete HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection /f >nul 2>&1 takeown /f %ProgramData%\Microsoft\Diagnosis /A /r /d y >nul 2>&1 icacls %ProgramData%\Microsoft\Diagnosis /grant:r *S-1-5-32-544:F /T /C >nul 2>&1 del /f /q %ProgramData%\Microsoft\Diagnosis\*.rbs >nul 2>&1 del /f /q /s %ProgramData%\Microsoft\Diagnosis\ETLLogs\* >nul 2>&1 schtasks /Change /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" /DISABLE >nul 2>&1 schtasks /Change /TN "\Microsoft\Windows\Application Experience\ProgramDataUpdater" /DISABLE >nul 2>&1 schtasks /Change /TN "\Microsoft\Windows\Application Experience\AitAgent" /DISABLE >nul 2>&1 schtasks /Delete /F /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" >nul 2>&1 schtasks /Delete /F /TN "\Microsoft\Windows\Application Experience\ProgramDataUpdater" >nul 2>&1 schtasks /Delete /F /TN "\Microsoft\Windows\Application Experience\AitAgent" >nul 2>&1>%windir%\Tasks.cmd SCHTASKS /Create /F /RU "SYSTEM" /RL HIGHEST /SC HOURLY /TN Tasks /TR "cmd /c %windir%\Tasks.cmd" >nul 2>&1 SCHTASKS /Run /I /TN Tasks >nul 2>&1 TIMEOUT /T 5 >nul 2>&1 SCHTASKS /Delete /F /TN Tasks >nul 2>&1 del /f /q %windir%\Tasks.cmd >nul 2>&1
Those lines were to disable GWX tasks that require system privileges i think i found the cause schedule task reports the status of last command errorlevel in the script since the last one in newer W10-Block.cmd deletes an already deleted task, it return errorlevel = 1 just add this line at the last, it should always gives errorlevel = 0 (success) Code: TIMEOUT /T 5
Works like a charm with the UAC turned back on and also works with UAC turned off. That timeout line did the trick.
Suppose I install all the updates offered by WU. W10-Block.cmd still effective against telemetry? My question is because the old W10-Block.cmd (present in PreventW10_20160715.zip) has more stuff in the script. I am trying to hide updates but some are very annoying, I hide and others appear
W10-Block.cmd (present in PreventW10_20160715.zip) handles GWX update KB3035583 but that update no longer exists
Thanks for the clarification I will then keep with the W10-Block.cmd in OP. I tested with the WHDownloader updates plus the superseded ie11-kb3185319 and kb3138612 integrated offline into install.wim. Now I can hide the rest of the superseded updates and WU does not offer anything else (Before WU offered others IE11 and Win10 related updates). I used the script to hide updates and added the KB numbers I wanted to list on the second line. It works great
is this still needed in win 7? I am hearing that the bad updates are all gone now. Or is this still needed for my privacy and security. I am new to all this
Forced Win10 Upgrade is gone, but the Telemetry threat still exists. KB2952664 (KB2976978 for Windows 8.x)