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 with symbols, not with visual studio problem itself.

Problem Statement: Visual Studio 2012 (and 2010 for the same matter) will stop attaching to remote process after a period of time with "invalid access to memory location". Restarting Visual Studio fixes the problem.

I am currently on VS2012 update 3, but the issue also occured in RTM, and all intermediate updates.

The referenced thread suggests patching operating system with hotfix 2588507, however I am unable to apply it, because it seems to be not downloadable, possibly because of intermittent issue.

Have anybody successfully addressed this problem and if yes then how?

Answer 1

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 2

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 3

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

Hope this helps out someone.