Schtasks /Change /DISABLE /TN "Microsoft\Windows\End Of Support\Notify2" Schtasks /Change /DISABLE /TN "Microsoft\Windows\End Of Support\Notify1" Reg add HKCU\Software\Microsoft\Windows\CurrentVersion\SipNotify /f /v LastShown /t REG_QWORD /d 0x0 Reg add HKCU\Software\Microsoft\Windows\CurrentVersion\SipNotify /f /v DateModified /t REG_QWORD /d 0x0 Reg add HKCU\Software\Microsoft\Windows\CurrentVersion\SipNotify /f /v DontRemindMe /t REG_DWORD /d 1 %windir%\system32\reg.exe query "HKU\S-1-5-19" 1>nul 2>nul || (Įcho This script require administrator privileges.Įcho To do so, right click on this script and select 'Run as administrator'įor /f "tokens=6 delims=. – copy or download the contents from this paste bin, and save as. This can be done officially with few manual steps, or a simple batch script (with exra little-aggressive setings) – the actual telemetry controller and runner, handles the compatibility evaluation and collecting, and device inventoryĭespite the infamous reputation and some exaggeration, these Telemetry components in Windows 7/8.1 updates are not deeply implemented into OS and can be easily disabled or eliminated – represented by the “Application Experience” schedule tasks (Microsoft Compatibility Appraiser, ProgramDataUpdater, AitAgent) – introduced in KB2952664/KB2976978, and now become part of the Monthly Rollup staring September 2018 preview rollup – handle the diagnosis tracking and logging, and the online telemetry reporting endpoints – represented by the Diagnostics Tracking Service (DiagTrack) and the event trace session (AutoLogger-Diagtrack-Listener) – introduced in updates KB3068708/KB3080149, and became part of the Monthly Rollup since October 2016 preview rollup Microsoft had backported two main parts of Windows 10 Telemetry system to Windows 7 and 8.1 In addition to the info below, I would prefer not having the Spectre/Meltdown updates installed, along with the usual updates we've always left out, but that's just me.ĪKB 2000012: How To Neutralize Telemetry and Sustain Windows 7 and 8.1 Monthly Rollup Model I HAVE INCLUDED WHAT I THOUGHT WAS MOST PERTINENT. I KNOW THIS IS LONG, BUT THIS IS VERY MUCH WORTH THE READ, EVEN THE COMMENTS TO THE ORIGINAL POST. It' s recommended that you reboot as soon as possible for the full effect.This is from a post abbodi86 (from MSFN, WinCert, MDL, AskWoody, etc fame) made over at AskWoody. etl was successful 22: 17: 33 INFO: DiagTrack: Successfully cleared and locked DiagTrack log.Ģ2: 17: 43 INFO: Registry: Successfully modified dmwappushsvc key.Ģ2: 17: 54 INFO: Registry: Successfully modified DiagTrack key.Ģ2: 17: 54 INFO: Registry: Successfully modified AllowTelemetry key.Ģ2: 17: 59 INFO: Registry: Successfully modified WifiSense Open - ness key.Ģ2: 17: 59 INFO: Registry: Successfully modified WifiSense Credential Share key.Ģ2: 17: 59 INFO: Registry: Successfully modified ListPin key.Ģ2: 17: 59 INFO: Registry: Successfully modified FileSync key.Ģ2: 17: 59 INFO: OneDrive: unable to uninstall 22: 17: 59 INFO: Done. etl for writing Traceback ( most recent call last):įile "dwt_util.py", line 105, in clear_diagtrack IOError: Permission denied: 'C: \\ProgramData \\Microsoft \\Diagnosis \\ETLLogs \\AutoLogger \\AutoLogger-Diagtrack-Listener.etl' 22: 17: 33 INFO: DiagTrack: Deny System Privilege of AutoLogger - Diagtrack - Listener. etl was successful 22: 17: 33 ERROR: DiagTrack: Couldn' t open AutoLogger - Diagtrack - Listener. etl was successful 22: 17: 33 INFO: DiagTrack: Grant Admin Privilege of AutoLogger - Diagtrack - Listener. 108.23 was successfully blocked.Ģ2: 17: 33 INFO: DiagTrack: Take Ownership of AutoLogger - Diagtrack - Listener. 108.33 was successfully blocked.Ģ2: 17: 32 INFO: IP Blocker: The IP 65.55. 54.254 was successfully blocked.Ģ2: 17: 29 INFO: IP Blocker: The IP 65.39. 212.69 was successfully blocked.Ģ2: 17: 27 INFO: IP Blocker: The IP 64.4. 61.66 was successfully blocked.Ģ2: 17: 24 INFO: IP Blocker: The IP 204.79. 61.43 was successfully blocked.Ģ2: 17: 22 INFO: IP Blocker: The IP 2.22. 106.189 was successfully blocked.Ģ2: 17: 20 INFO: IP Blocker: The IP 2.22. 81.24 was successfully blocked.Ģ2: 17: 18 INFO: IP Blocker: The IP 157.56.
0 Comments
Leave a Reply. |