Huh?
The point was simply that Windows is an application in itself, it will use a good deal of RAM and won’t show up as an application in Task Manager.
svchost is an essential process. Shutting it down will break a lot of things,
Not necessarily, but it might. If you task-kill an svchost instance you’re going to get, literally, “unexpected” results by nature of what svchost is and what it’s actually running. We’d need to drill into it to find out, that’s the only way you’re going to fix the issue properly.
though I’d expect it will start up again anyway.
Quite possibly. Again, it depends what’s running it.
Googled it and it’s a common problem Followed the help to shut it down. It’s like a new machine now.
It’s a common problem is so far as “sometimes programs consume excessive memory,” as someone else said earlier it could be a memory leak or a whole host of other causes. There’s nothing inherently wrong or broken with svchost, it’s like blaming roads for a car fire.
TBH though, if you’re going to ask for advice and then ignore it completely in favour of Google, we’re both wasting our time here.