Microsoft visual studio 2017 has stopped working

You are trying to launch another process, and the process you want to launch is an administrator. You want to attach to processes running as another user (such as when debugging IIS), or You want to run the remote debugger as an administrator in several scenarios: If you are trying to attach to your own non-elevated process (such as a normal application), it doesn't matter if you are running the remote debugger as an administrator. When running the remote debugger as an application (normal mode) Visual Studio Express was supplanted by the Visual Studio Community edition, which is also available for free, but with a different license. The built-in accounts have elevated security privileges that can present a security risk. Microsoft Visual Studio Express is a set of integrated development environments (IDEs) developed by Microsoft as a freeware and registerware function-limited version of the non-free Microsoft Visual Studio.Express editions started with Visual Studio 2005.

On a domain, it is easier to connect back if the remote debugger is running under the built-in Local System or Network Service accounts, or a domain account. The account must be able to connect back to (that is, authenticate with) the Visual Studio computer over the network. (The easier alternative is to run the service as an administrator.) To get these rights, you must run the remote debugger under the same account as the process to be debugged. The account must have rights to debug the target process. See the steps under 'To add logon as a service' in the cannot connect back error article. The account you are using on the remote machine must have the logon as service privilege. While it's possible to debug without running the remote debugger as an administrator, there are several requirements to make this work correctly and they often require more advanced service configuration steps. To simplify the setup and configuration of the remote debugger. It can prevent errors that result when the Visual Studio user has more rights to debug a process than the remote debugger itself does. The remote debugger service only allows connections from administrators, so there are no new security risks introduced by running it as an administrator. When running the remote debugger as s service, we recommend running it as an administrator for several reasons: When running the remote debugger as a service

For example, you may see the following error: 'The Visual Studio Remote Debugger (MSVSMON.EXE) has insufficient privileges to debug this process.' If you are running the remote debugger as an application (not a service), you may see the different user account error. You may come across issues if you don't run the remote debugger as an administrator. Run the remote debugger as an administrator Unable to Connect to the Microsoft Visual Studio Remote Debugging MonitorД®rror: Remote machine does not appear in a Remote Connections dialog You may come across the following errors when attempting to debug remotely.Д®rror: Unable to Automatically Step Into the ServerД®rror: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.

Microsoft visual studio 2017 has stopped working