The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.

The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
  • Article
  • 4 minutes to check out

Applies to: yes Visual Studio no Visual Studio for Mac no Visual Studio Code

This mistake message indicates that Visual Studio might not discover the proper circumstances of the Visual Studio Remote Debugging Monitor on the remote computer system. The Visual Studio Remote Debugging Monitor need to be set up for remote debugging to work. For info about downloading and establishing the remote debugger, see Remote Debugging

I got this message while I was debugging in Visual Studio 2010 or earlier

If the variation of Visual Studio that you are utilizing is Visual Studio 2010 or earlier, you may likewise get this mistake if file and printer sharing is not made it possible for. To learn more about this problem, please describe the Visual Studio 2010 variation of this documents: Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not seem working on the remote computer system. – Visual Studio 2010

I got this message while I was debugging in your area

If you are getting this message while you are debugging in your area with Visual Studio 2017 or earlier, your anti-virus software application or a third-party firewall software might be to blame. Visual Studio 2019 and earlier are 32- bit applications. 32- bit variations of Visual Studio utilize the 64- bit variation of the remote debugger to debug 64- bit applications. With Visual Studio 2017 and previously, the 2 procedures interact utilizing the regional network within the regional computer system. No traffic leaves the computer system, however it is possible that 3rd party security software application might obstruct the interaction.

The following areas note some other reasons you may have gotten this message, and what you can do to repair the concern.

The remote device is not obtainable

Try to ping the remote device. If it does not respond to the ping, the remote tools will not have the ability to link either. Attempt restarting the remote device and otherwise making certain that it is properly set up on the network.

The variation of the remote debugger does not match the variation of Visual Studio

The variation of Visual Studio that you are running in your area requires to match the variation of the remote debugging screen that is operating on the remote device. To repair this, download and set up the matching variation of the remote debugging display. Go to the Download Center to discover the ideal variation of the remote debugger.

The regional and remote makers have various authentication modes

The regional and remote devices require to utilize the exact same authentication mode. To repair this, ensure that both devices are utilizing the very same authentication mode. For additional information about authentication modes, see Windows Authentication Overview

The remote debugger is running under a various user account

You can resolve this in among the following methods:

  • You can stop the remote debugger and reboot it with the account you are utilizing on the regional computer system.
Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: