It sounds like your Windows Update is afflicted and you are not really fixing the problem but are fixing the symptom of the problem by manipulating Windows Services and you shouldn't have to do that... if you fix the Windows Update process which had been
afflicted for quite some time - but it has been figured out.
Start here to be sure you have the latest parts and pieces for your Windows Update process:
Windows Update Problems? Read this first.
Then here is a little thing I am working on to help understand what is going on with all those svchost.exe Processes you see in Task Manager:
Fixing the problem and fixing the symptom of the problem are not the same thing.
You will see many svchost.exe Processes running in Task Manager and under each of those will be one or more important Windows Services. It is normal to see several svchost.exe Processes running in Task Manager and that does not mean there is a problem.
Important Windows Services run under each svchost.exe Process you see. There might be 6 or 8 or 10 svchost.exe Process running... it depends on how the system is configured.
When you see a svchost.exe process consuming too much CPU the problem is (usually) not with the svchost.exe Process itself - the problem is what is running
under that svchost.exe Process and you can figure out what that is in several ways.
It is alleged that sometimes malicious software can disguise itself as a svchost.exe Process and show up in Task Manager so assuming your system is not afflicted with malicious software you can figure out what is going on.
The Windows Update Service runs under one of the many svchost.exe Processes you see in Task Manager.
You can notice the PID column of the afflicted svchost.exe Service in Task Manager, right click the afflicted Process and choose Services (Process ID PID 1044 is running amok in this bad example):

Then in the Services Tab, click the PID column to sort by PID and you can see all the important Windows Services that are running under that svchost.exe process.
if you see wuauserv.exe (Windows Automatic Update Service) running under the afflicted svcshost PID the Windows Update Service is likely the problem so you need to fix it:

Now visit this discussion to fix your afflicted Windows Update process:
Windows Update Problems? Read this first.