Visual Studio remote debugger “invalid access to memory location” feature

Question

This is another attempt to resolve the problem stated here. Unfortunately the topic was closed without adequate resolution found, as apparently the original poster had issues wi

Answer 1

I found a simple workaround for this. Change the debug port on the remote machine (Tools --> Options). I would use something arbitrarily high, like 63342 to avoid colliding with any existing ports but you just need to use any unused one. Once changed, you should be able to connect.

Answer 2

The hotfix 2588507 ended up resolving the issue after all. I am running several instances of visual studio 2012 for several days, and debugging remote processes constantly, and have not seen yet a single "invalid access to memory location"

Answer 3

I came accross this error message in VS2013 and resolved it by running VS with administrator priviledges.

Hope this helps out someone.