Microsoft.VsHub.Server.HttpHostx64.exe and Microsoft.VsHub.Server.HttpHost.exe crash when you debug code in Visual Studio 2015
When you use Microsoft Visual Studio 2015, Windows repeatedly reports that one of the following applications stopped working:
Microsoft.VsHub.Server.HttpHostx64.exe
Microsoft.VsHub.Server.HttpHost.exe
This article contains steps to diagnose the issuse and a workaround.
This issue occurs because Microsoft.VsHub.Server.HttpHostx64.exe and Microsoft.VsHub.Server.HttpHost.exe provide services and additional information to Visual Studio through an external process when you debug code. These processes communicate over HTTP through the local host. Applications that detour network activity can cause compatibility issues that cause these processes to crash.
Applications that monitor malware and create VPNs are examples of applications that are likely to cause this issue.
To determine whether this is the problem, create a simple console program by using the following code, build the code as a 32-bit .exe program for 32-bit Windows or as a 64-bit .exe program for 64-bit Windows, and then try to run this program. If the program crashes, you have an incompatible program installed on your computer.
using System;
using System.Net;
namespace HttpListenerTest
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine("Running as {0}",Environment.GetEnvironmentVariable("PROCESSOR_ARCHITECTURE"));
using (HttpListener s = new HttpListener())
{
s.Prefixes.Add("http://localhost:49154/vshub/418f29b9cebf4d6bae64d16162f56832/");
s.Start();
Console.WriteLine("Server started");
}
Console.WriteLine("Server stopped");
}
}
}
To work around this issue, uninstall the software that detours network activity. Or, contact the application vendor for additional support.
The information and the solution in this document represent the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or a third-party provider. We do not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because we must respond to changing market conditions, this information should not be interpreted as a commitment by Microsoft. We cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.