The Visual Studio 2017 debugger worker process (msvsmon.exe) quits unexpectedly when debugging terminates

Original: Worker process for Visual Studio 2017 debugger (msvsmon.exe) Quit debugging unexpectedly terminates

Development environment:

• Windows Ten in Parallels Desktop
• Visual Studio 15.6

Scene Restore:
To create a new ASP. NET Core MVC project using Visual Studio 15.6 (that is, Visual Studio 2017), start debugging, prompting:

The debugger's worker process (msvsmon.exe) quits unexpectedly. Debugging will terminate

In fact, this problem has been encountered many times, but did not record, resulting in every time to re-search the solution.

Open Event Viewer, and then click "windows Log"-"application to see two error level logs:

The log with the source "Application Error" is shown below:

description:
Wrong application name: msvsmon.exe, version: 15.0.27428.2043, timestamp: 0x5adf7e7a
Error module name: unknown, version: 0.0.0.0, timestamp: 0x00000000
Exception code: 0xc0000005
Error offset: 0x0000000000000000
Error Process ID: 0x1518
Bad application startup time: 0x01d3de90a8d1c526
Incorrect application path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Remote Debugger\x64\msvsmon.exe
Error module path: unknown 

The logs from "Visual Studio Remote Debugger" are displayed as follows:

description:
Could not find a description of event ID 1002 from the source Visual Studio Remote Debugger. The component that caused this event is not installed on the local machine, or the installation is corrupt. You can install or repair components on your local computer.

If the event originated on another computer, the display information must be saved in the event.

The following is the information contained in the event:

The remote debugger encountered a serious internal error and must abort the remote debugging session. Please restart debugging. 

Then Google to this article annoying visual Studio 2010 crash Restart problem, see the author finally shut down the firewall to solve the problem, I immediately try to turn off the firewall retry, and really start the debugger normally.

Then I thought, last night on Windows Server to build NGINX, encountered an external network can not access the problem, because in the firewall settings, there is nongingx.exeadded to允许应用通过防火墙进行通信the list.

Lenovo to this, I reopened the firewall and thenmsvsmon.exeadded to允许应用通过防火墙进行通信the list and ticked on and on专用公用.

Start debugging again, success!

Look carefully atmsvsmon.exethe path that isRemote Debuggerunder the folder, meaning remote debugging? So need to communicate through firewalls and external networks?
We know that vs can debug the code of another machine remotely, but should not involve the external network communication in local debugging, is it related to my virtual machine environment? However, it has been encountered in a non-virtual machine environment before.
Hope to have a friend to understand the doubts!

Update :
The above solution, only succeeded once, then the second time is not ...

No way, continue to find solutions, try to use English keywords Google
the debugger‘s worker process (msvsmon.exe) unexpectedly exited. debugging will be aborted
Find this article msvsmon.exe crashed when debugging, summarizes a number of solutions to the problem, one of which caught my attention:

I too have Astrill installed. Completely uninstalling Astrill fixed the issue.

Yes! I was installed Astrill, a burst of joy inside, the original is this fellow caused!
Uninstall Astrill After restarting the computer, repeatedly start debugging no problem, perfect!

The Visual Studio 2017 debugger worker process (msvsmon.exe) quits unexpectedly when debugging terminates