Visual Studio debugger isn't attaching
<p>I'm having two problems which center on the debugger. I'm not sure if they share the same cause but they definitely seem related.</p>

<ol>
<li>When I open my solution in Visual Studio Enterprise 2015, I get this message: <a href="https://imgur.com/JwPiMLy" rel="nofollow noreferrer">Automatically attaching to support this behavior was not completely successful</a></li>
<li>When I start the program directly from the executable and try to attach to the process in visual studio, I get this message: <a href="https://imgur.com/rclklta" rel="nofollow noreferrer">Unable to attach to the process. No more data is available.</a></li>
</ol>

<p>After dismissing the message box I get in step 2, the IDE definitely thinks it's attached to something. The Debug toolbar shows active Break All and Stop Debugging buttons and I can select Debug > Detach All. It's not hitting any of the breakpoints I set.</p>

<p>Per Jeremy's answer, I went to Debug > Windows > Modules and it <a href="https://imgur.com/dqiJ0bC" rel="nofollow noreferrer">showed nothing</a> in the list. The debug output also immediately says the program exited with code 0 (bottom left of that screen cap).</p>

<p><hr />
The following are related questions and answers I've come across. None of the posted solutions worked.</p>

<ul>
<li><a href="https://stackoverflow.com/questions/3996139/unable-to-attach-to-the-process">This question</a> is only kind of similar and I set VS to always run as administrator.

<ul>
<li><a href="https://stackoverflow.com/a/3996333/902940">This answer</a> to that question led me to modify the Debug Programs policy in <a href="https://technet.microsoft.com/en-us/library/dn221969.aspx" rel="nofollow noreferrer">User Rights Assignment</a> to include my account. It previously only included the Administrators group which my account is part of but I took a shot.</li>
</ul></li>
<li><a href="https://stackoverflow.com/questions/6065548/automatically-attaching-to-support-behavior-not-completely-successful">This question</a> is similar to bullet 1 above. My Visual Studio is completely up-to-date. I also tried enabling SQL Server debugging as some of the answers suggested but that didn't do anything.</li>
</ul>