So far you haven't stated what "the issue" or what "the problem" is.
A fairly common complaint is that there a multiple svchost Processes seen running in Task manager but that is normal to see 6, 8, 10... it depends on your system configuration.
Each svchost Process is "hosting" important Windows Services that run underneath it. Each svchost Process might be hosting one Windows Service or several Windows Services.
So each svchost Processes is hosting services - hence the name.
Another common complaint (and what is abnormal) is for one of the svchost Processes to be running amok consuming large amounts of CPU and memory.
Normally the svchost Processes should be using zero CPU and you might see occasional CPU usage blip once in a while. For the most part they are very quiet.
A popular theory and misconception is that when a svchost Process is running amok is that there is a "memory leak" in svchost.exe but there is no memory leak in svchost.exe.
If there was a memory leak in svchost.exe then systems all over the planet would be malfunctioning - and they're not.
Along with the misconception of a memory leak is plenty of not so good advice about what to do to fix the non existent memory leak and those suggestions usually begin with the word "try".
If a svchost Process is running amok there is always a reason for it and you can figure it out and fix it by doing things and not trying things.
This looks pretty normal for my system when not much is going on:
Edited by joseibarra, 16 June 2018 - 03:21 AM.