Question: I have installed VS 2015 RTM (nothing else) and I'm unable to debug any solution, not matter if it's an existing one or a brand new one (created with VS 2015 and compiled against .Net Framework 4.6), it only opens a new tab in VS which is called Break Mode with the following text:
The application is in break mode
Your app has entered a break state, but no code is executing that is supported by the selected debug engine (for e.g. only native runtime code is executing).
And if I check the Debug --> Module Window:
VS2015Test.vshost.exe no symbols loaded (even if I click load symbol it does not work)
VS2015Test.exe symbols loaded

And it also doesn't show the output on the console(it's a console application that just has the following lines of code:

```
class Program
{
        static void Main(string[] args)
        {
            Console.WriteLine("TEST");
            Console.ReadKey();
        }
    }

```

I tried to reinstall VS 2015, restarted the computer, deleted all files in %temp%/AppData/Microsoft/Visual Studio/14, started VS in Admin Mode but nothing seems to work.

One thing which makes debugging working is this option:
Tools --> Options --> Debugging --> Use Managed Compability Mode

^^But that can't be the solution to use an old/legacy mode.

BTW: Debugging in VS 2013 is working fine.

Any help would be appreciated.

Answer: 
I had a very similar issue recently, related to debugging settings. 

Firstly have you tried resetting all your settings? I think it may be related to that as you say it is project independent and you've deleted all application data.

> 
> Tools-> Import and Export Settings Wizard -> Reset all settings
> 
> 
> 

*Don't worry, it gives you the option to save current settings.* 

Secondly if this fails, I would suggest looking at the event log. 

Entering break mode would suggest that the DE (debug engine) is sending a synchronised stop event to visual studio like [IDebugExceptionEvent2](https://msdn.microsoft.com/en-us/library/vstudio/bb146157(v=vs.100).aspx). I would take a look at the event log for exceptions like failures in loading referenced assemblies (like .NET runtimes, etc) or environment access restrictions. 

Something is telling the debugger to stop your running application, its just a case of finding it.
We had this issue, after trying all other options such as deleting .vs folder, Renaming IISExpress folder name, Updating various setting on properties etc it did not work. What worked though, was uninstalling IISExpress 10.0, and Reinstalling it along with turning all IIS related features on from Windows Features. Hope this helps someone.