I want to manually control the launch the Windows Update service on a Windows 10 Home laptop because it runs too frequently, causing high CPU and draining the battery.
The idea is that the the service will be disabled and the user will launch Windows Updates on demand and then once the service has started and it is under way, set the service immediately to Disabled again. This should ensure that once updates are applied, Windows Update will not launch again by itself.
My question is, considering some updates need to reboot the system to complete their installation, would disabling the service in this way cause issues with these updates?
Alternatively, and unfortunately more complicated, is to
- Set Windows Update service to its own svchost.exe process
- Launch the service & Check for updates
- Monitor CPU usage and disable once found it has settled down.
My plan is for the user to launch the update when they go to sleep and hopefully when they wake, the updates will have been done and the service will be disabled.
EDIT:
What I have done so far is to create two VBS scripts. One to stop and disable the service. It runs automatically at logon with elevated privileges through the Task Scheduler.
The second script enables the service and starts it. Then the GUI is presented to the user to click "Check for Updates". This way they can keep an eye on it. I will have her launch the second script once a week, probably weekends when she goes to sleep. Reboots should occur automatically.
No comments:
Post a Comment