ShutUp10 is a very simple and very effective tool against Microsofts spy practices. but to use it efficiently you have to run it more or less every day manually.
Is it possible to create a script that runs the program (portable.exe) and skips the following steps by itself so that you automatically revert the changes of a Windows update back to the original settings?
ShutUp10 Automation
ShutUp10 Automation
- Attachments
-
- Unbenannt.png (79.89 KiB) Viewed 6403 times
-
- Unbenannt2.png (72.32 KiB) Viewed 6403 times
Re: ShutUp10 Automation
No answer... I assume this is not possible then.
Re: ShutUp10 Automation
ShutUp10 only manipulates the Registry. I don't know if automating the ShutUp10 program itself is easily done, but one option is using a program like RegFromApp or a program like RegShot or SysTracer to determine the changes made by ShutUp10 and produce a reg file that you can import at any time. This approach, however, requires you undo everything with ShutUp10 first and selectively re-enable the settings you want again...Thouldre wrote:No answer... I assume this is not possible then.
EDIT: It supports command-line parameters like /quiet and /force. I think you can use them with an exported ShutUp10 cfg file to force reapplying your settings with it from the command-line.
Last edited by qwerty12 on 30 May 2017, 06:16, edited 1 time in total.
Re: ShutUp10 Automation
ShutUp10 is a GUI to the changes made primarily to the registry but also to 'services' and 'scheduled tasks'. It appears to be benign (i.e. I can't see any contra-indications or any 'phone home' functionality) but there's no reason for you not to (re-)create the changes made using AHK, thus staying in complete control yourself rather than trying to automate a third-party product.
For example:
For example:
Code: Select all
; Prompt to 'Run as Admin', i.e. show UAC dialog
If Not A_IsAdmin
{
Run *RunAs "%A_ScriptFullPath%" ; Requires v1.0.92.01+
ExitApp
}
; Allow registry commands in a 32-bit script to access redirected keys in the 64-bit registry view and vice versa.
SetRegView 64
; Section 1 - Amend telemetry-related settings in the registry
; Feedback frequency - Windows should ask for my feedback - NEVER (SIUF = System Initiated User Feedback)
RegWrite, REG_DWORD, HKCU\SOFTWARE\Microsoft\Siuf\Rules, NumberOfSIUFInPeriod, 0
; Diagnostic and usage data - Send your device data to Microsoft - BASIC
RegWrite, REG_DWORD, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection, AllowTelemetry, 1
RegWrite, REG_DWORD, HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection, AllowTelemetry, 0
; Section 2 - Amend telemetry-related services
; Stop and disable DiagTrack
; Note: This used to appear in Services as 'Diagnostics Tracking Service' but MS sneakily renamed it to 'Connected User Experiences and Telemetry'
RunWait,sc stop "DiagTrack",,hide
RunWait,sc config "DiagTrack" start= disabled,,hide
;RunWait,sc delete "DiagTrack",,hide
; Section 3 - Amend telemetry-related scheduled tasks
RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\Consolidator" /Disable,,hide
RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\KernelCeipTask" /Disable,,hide
RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\UsbCeip" /Disable,,hide
RunWait,schtasks /Change /TN "Microsoft\Windows\Feedback\Siuf\DmClient" /Disable,,hide
; Restore normal behaviour for 'Reg' commands
SetRegView default
; Popup message when completed
MsgBox, 64, ET... DON'T phone home!, Telemetry-related settings have been amended to reduce 'phoning home'.`n`nThe registry changes will not take effect until you restart.
ExitApp ; All done so exit
Re: ShutUp10 Automation
I exported the settings as a .cfg file inside the same directory as the exe and created a scheduled task to run the ShutUp10 withqwerty12 wrote:ShutUp10 only manipulates the Registry. I don't know if automating the ShutUp10 program itself is easily done, but one option is using a program like RegFromApp or a program like RegShot or SysTracer to determine the changes made by ShutUp10 and produce a reg file that you can import at any time. This approach, however, requires you undo everything with ShutUp10 first and selectively re-enable the settings you want again...Thouldre wrote:No answer... I assume this is not possible then.
EDIT: It supports command-line parameters like /quiet and /force. I think you can use them with an exported ShutUp10 cfg file to force reapplying your settings with it from the command-line.
Code: Select all
/quiet /force
Re: ShutUp10 Automation
I'd prefer using ShutUp10 because it is dynamic. Every update brings more functions to disable which means I'd have to write a script every time a new functions has been added...RickC wrote:ShutUp10 is a GUI to the changes made primarily to the registry but also to 'services' and 'scheduled tasks'. It appears to be benign (i.e. I can't see any contra-indications or any 'phone home' functionality) but there's no reason for you not to (re-)create the changes made using AHK, thus staying in complete control yourself rather than trying to automate a third-party product.
For example:
Code: Select all
; Prompt to 'Run as Admin', i.e. show UAC dialog If Not A_IsAdmin { Run *RunAs "%A_ScriptFullPath%" ; Requires v1.0.92.01+ ExitApp } ; Allow registry commands in a 32-bit script to access redirected keys in the 64-bit registry view and vice versa. SetRegView 64 ; Section 1 - Amend telemetry-related settings in the registry ; Feedback frequency - Windows should ask for my feedback - NEVER (SIUF = System Initiated User Feedback) RegWrite, REG_DWORD, HKCU\SOFTWARE\Microsoft\Siuf\Rules, NumberOfSIUFInPeriod, 0 ; Diagnostic and usage data - Send your device data to Microsoft - BASIC RegWrite, REG_DWORD, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection, AllowTelemetry, 1 RegWrite, REG_DWORD, HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection, AllowTelemetry, 0 ; Section 2 - Amend telemetry-related services ; Stop and disable DiagTrack ; Note: This used to appear in Services as 'Diagnostics Tracking Service' but MS sneakily renamed it to 'Connected User Experiences and Telemetry' RunWait,sc stop "DiagTrack",,hide RunWait,sc config "DiagTrack" start= disabled,,hide ;RunWait,sc delete "DiagTrack",,hide ; Section 3 - Amend telemetry-related scheduled tasks RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\Consolidator" /Disable,,hide RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\KernelCeipTask" /Disable,,hide RunWait,schtasks /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\UsbCeip" /Disable,,hide RunWait,schtasks /Change /TN "Microsoft\Windows\Feedback\Siuf\DmClient" /Disable,,hide ; Restore normal behaviour for 'Reg' commands SetRegView default ; Popup message when completed MsgBox, 64, ET... DON'T phone home!, Telemetry-related settings have been amended to reduce 'phoning home'.`n`nThe registry changes will not take effect until you restart. ExitApp ; All done so exit
Re: ShutUp10 Automation
Yes. As far as I can tell, you just quote the path to the cfg file and put it on the command line. I think. I haven't actually tried it. Oddly, the only place O&O documents these switches is in the change log...Thouldre wrote:Do I have to specify the path of the .cfg file? If yes, how?
Re: ShutUp10 Automation
Found the solution. Works very nice if used with task scheduler! Put everything inside the same folder and execute script as admin after user logon because some settings are user specific!
Code: Select all
c:\Test\OOSU10.exe ooshutup10.cfg /quiet
Re: ShutUp10 Automation
That's a fantastic idea! Could you share what you wrote in the batch.bat file?Thouldre wrote: ↑04 Jun 2017, 03:00Found the solution. Works very nice if used with task scheduler! Put everything inside the same folder and execute script as admin after user logon because some settings are user specific!
batch.PNGCode: Select all
c:\Test\OOSU10.exe ooshutup10.cfg /quiet
Re: ShutUp10 Automation
Also to confirm, this is what you have in the task scheduler?Thouldre wrote: ↑04 Jun 2017, 03:00Found the solution. Works very nice if used with task scheduler! Put everything inside the same folder and execute script as admin after user logon because some settings are user specific!
batch.PNGCode: Select all
c:\Test\OOSU10.exe ooshutup10.cfg /quiet
Who is online
Users browsing this forum: Descolada, vikasgandhi and 316 guests