New
#11
The tool is making the changes you can manuallly make at the registry level. How does it keep and enforce the services stay disabled after reboot? I've also questioned if Windows Installer is needed to be disabled, seems like it would cause more trouble than it is worth and if the update can't be downloaded it can't be installed. Renaming of the installer files will cause boot errors from past experimentation.
I don't think this will work unless it is constant running in the background. I'm not a fan of this solution when a simple startup script will disable the services run once and not use any resources.
- - - Updated - - -
The second link with the CMD and VBScript is not valid can you please check the link. Curious here what those scripts entail. I have a script but would like to avoid having to use it each time on startup
- - - Updated - - -
Hi Denis,
I would perfer to just not have it run period in the background. On some of the older machines it just sucks up resources and i manually update as I see fit.
- - - Updated - - -
This doesn't work, it needs to be applied again after a reboot. It doesn't run in the background unlike some other 3rd part tools that wait for a trigger of the service changing state. Even in the comments section you can see it was reported. You might not even know it is happening.