High CPU usage - svchost[dot]exe

My computer has started "playing" up reporting a high CPU usage when nothing is happening. Looking at Processes when Task Manager is open shows the responsible process is svchost[dot]exe. Does anyone have a suggestion as to how I solve this. I've looked online but find "answers" to be confusing to me.

OK I'm still scratching my head with this one. The above exe file shows up in Processes in Task Manager and so when you right click on it and then left click on Go To Service(s) you get this screen. I believe the problem relates to the first highlighted item, namely wuauserv:-

I'm now back to my earlier confused state, and will once again search the net for some answers that I can understand! Unless someone with better knowledge can point me in the right direction?

I should have added the following screenshot highlighting the process that has the high usage!

It's right clicking on the highlighted line that takes you to the services associated with that process!
I tried stopping it and this initially reduced the usage but it did start to increase again! I then restarted the computer and the stopped service was active once again with the consequential high CPU usage!

Hi Alec,
Regarding wuauserv, see : http://superuser.com/questions/821032/svchost-exe-high-memory-usage-wuauserv

It's the Windows Update Service and I've also found that my PC is affected by it, but, usually, not for very long.

Cheers,
Ged

Thanks for the reply Ged. I've found a suggested method on Youtube, which I'll watch again before attempting the solution. As suggested in that thread, this would appear to be quite a common problem affecting W7, W8.1 and even W10!

Mmm . . . I followed the recommended procedure but not at all sure what I have done or achieved? It is still showing high usage for the svchost/wuauserv?

Once again my head is aching.

I have now tried an alternative solution in which I disabled the Window Update service. This appears to have resolved the problem. However it means that Windows updating now needs to be done manually I believe.