Can I delete ServiceHub.* in Visual Studio 2017?

Question

In VS2015 there was various stuff running in the background, like \"VsHub\", etc. It connected to MS servers, and possibly leaked stuff. So the common approach was to delete tho

Answer 1

Stumbled upon this question while looking for a similar fix myself. In my case ServiceHub.Host.CLR.x86.exe alone was consuming ~50% CPU even when Visual Studio was not running anything.

I was able to kill the process without any side effects, mid-running a project too, and was happy to note that it didn't come back up. ServiceHub.IdentityHost.exe appeared to be impervious to me trying to end the process, but it wasn't consuming any CPU.

The other processes listed above also did not consume much CPU (~0%), so I let them be.

Tl;dr: It may depend on what you're running on Visual Studio (I was running a C# project), but ServiceHub.Host.CLR.x86.exe can be killed without any side effects.