title: WinIot Core v.10.0.16299.15 - RP3 - Microsoft Visual Studio Remote Debugger, MSVSMON not running
body: <p>This isnt my first project with WinIoT on a Pi. I have been using the WinIot image since its first version.  I decided to update all my Pis to the latest WinIoT image. My VS is updated to the latest version 2017 15.15.2.  </p>
  
  <p>When I go to remote debug my application, It fails during the deploy process with this error:</p>
  
  <pre><code>1&gt;Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '[iphere]'.  The Visual Studio 2017 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
  </code></pre>
  
  <p>So I go onto the WinIot image, and click on the "Start Remote debugger" and it returns this text:</p>
  
  <p><a href="https://i.stack.imgur.com/O8WIW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/O8WIW.png" alt="enter image description here"></a></p>
  
  <pre><code>Failed to start the Visual Studio Remote Debugger. The Remote Debugger needs to be copied to the device. This can be done by deploying an application to the device using Visual Studio.
  </code></pre>
  
  <p>So, then I follow the link listed, and its basically just instructions on how to do what I am doing... exactly. <a href="https://docs.microsoft.com/en-us/windows/iot-core/develop-your-app/AppDeployment" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/windows/iot-core/develop-your-app/AppDeployment</a></p>
  
  <p>I have spent hours on this and am getting nowhere. It seems that MS now has VS put up its remote debugger, but for some reason its not working.  </p>
  
  <p>Debug Profile:
  <a href="https://i.stack.imgur.com/IzAz8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/IzAz8.png" alt="enter image description here"></a></p>
  
  <p>Things I have checked:</p>
  
  <ul>
  <li>Windows Firewall off</li>
  <li>Reinstalled the WinIot Image to start fresh</li>
  <li>Started a fresh UWP project with no code in it</li>
  <li>Set build verbosity high, but did not have issues on the build, only the deploy</li>
  <li>Added the WinIoT image to my trusted hosts with the windows powershell commands</li>
  <li>Was able to remote in with PowerShell, no issue there.</li>
  <li>Disabled IPv6 on my PC (pings were showing IPv6 when pinging the host name)</li>
  </ul>
  
  <p>Things I have noticed:</p>
  
  <ul>
  <li>When I first was able to get this to work, I saw that the instructions on MSDN are showing "Universal" for Authentication - When I select from the list of available Pi3, it moves it back to 'None' at one point, I was able to deploy and debug with 'None', but now even now that does not work.</li>
  <li>MSDN Instructions online seem to be dated with commands that are no longer available to run such as how to start the remote debugger -</li>
  <li>Cant seem to find a way to put the remote debugger on and manually start it (if that would even work)</li>
  </ul>
  
  <p>I feel that because I was able to do this before, in the last week on this image version, that there must be something environmental, but I have exhausted my time trying to figure it out I would rather be coding instead of debugging the debugging process. </p>
  
  <p>Any assistance is greatly appreciated. </p>