Skip to main content
Visual Studio Debugger
Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.

When you try to do remote debugging, you might receive this error message. It means that Visual Studio could not find an instance of the Visual Studio Remote Debugging Monitor on the remote computer. The Visual Studio Remote Debugging Monitor is required for remote debugging to work.

If you are trying to connect to an instance of the Visual Studio Remote Debugging Monitor running under a different user account, you have to tell the debugger the name of the instance of the debugging monitor (msvsmon.exe) to connect to, for example, user_name@computer.

If the version of Visual Studio that you are using is Visual Studio 2010 or earlier, you might also receive this error if file and printer sharing is not enabled. To find out more about this issue, please refer to the Visual Studio 2010 version of this documentation: Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. - Visual Studio 2010

To run the Visual Studio Remote Debugging Monitor on the remote computer

  1. Make sure that the remote computer has access to the Visual Studio Remote Debugging Monitor.

    1. If you are debugging a Windows client application, create a file share on the Visual Studio computer and run the remote debugger off this file share. Make sure that the remote computer has access to the file share.

    2. If you are debugging an ASP.NET application or other server application, run Visual Studio Remote Debugger setup on the remote computer and use the Visual Studio Remote Debugger Configuration wizard to enable the remote debugger service.

    For more information, see Set Up the Remote Tools on the Device.

  2. Start the Visual Studio Remote Debugging Monitor on the remote computer. For more information, see Start the Remote Debugging Monitor.

Common causes for this error

  • The most common causes for this error are the following:

    1. The remote machine is not reachable. To see if you can resolve this, try pinging the remote machine. If it doesn’t reply to the ping, the remote tools won’t be able to connect either. Try rebooting the remote machine and otherwise making sure that it is correctly configured on the network.

    2. The version of Visual Studio that you are running locally does not match the version of Visual Studio running on the remote machine. To fix this, make sure the two instances of Visual Studio have the same version.

    3. The local and remote machines are not set to use the same authentication mode. To fix this, make sure that both machines are using the same authentication mode.

    4. The firewall is not correctly configured on the remote machine to allow incoming connections to msvsmon.exe (the remote debugger). To fix this, Make sure all firewalls are configured to allow communication between Visual Studio and the remote debugger.

    5. Anti-virus software is blocking the communication. To fix this, make sure your anti-virus software allows the communication.

    6. Network security policy is blocking communication between the remote machine and Visual Studio. To fix this, review your network security to make sure that it is not blocking communication.

    7. The network is too busy to support remote debugging. To fix this, try doing remote debugging at a different time, or reschedule work on the network for a different time.