VS2012 RC - Debugging Tools for Windows not working - by Fuxi

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 746576 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 6/5/2012 3:55:30 AM
Access Restriction Public


When choosing "Debugging Tools for Windows - Local Debugger" (the "Windows Debugger") as debugging engine, I am unable to run/debug a program. It used to work with the Beta, but not with the RC.

I upgraded from the Beta to the RC (as the MSDN page stated that upgrading is possible). I don't know if it works with a fresh install of the RC, and I cannot compare it to a Beta install because I don't have them (anymore) and cannot really reinstall because of time constraints.

I ran Process Monitor alongside and could not find anything accessing any Windows Debugger files. It looks as if VS2012 treats the Windows Debugger as not being present (although as said, the Process Monitor doesn't show anything accessing/checking any Windows Debugger files).
Sign in to post a comment.
Posted by Chris Calzaretta on 12/17/2012 at 1:09 PM
I am having this same issue
I have a machine running windows 2008 R2
I have Visual Studio 2012 ultimate installed
I left my machine in the middle of a debug Friday. I come in to work on Monday and i now get this error

Everything builds fine
Once it trys to launch

"Operation taking longer than expected"
"A 64-bit debugging operation is taking longer than expected

This may be caused by incompatibilities with 3rd party networking software"

I have not been able to fix..
I tried a repair.. Deleted all roming/local appdata files also delete all stuff under the "My documents'

I have created a new VM and copied over my project and everything is working fine
Posted by Microsoft on 7/20/2012 at 11:20 AM
Hey Fuxi,

Thanks for reporting this issue. It appears you're trying to use the windows debugger rather than the VS debugger. We'll email that team about this issue but windows debugger issues should be filed through the windows support website. Additionally, we encourage people to use the VS debugger for VS win32 applications. I will be resolving this bug after I send the mail to notify them.

Marc Paine
Visual Studio Debugger QA Lead
Posted by Microsoft on 6/5/2012 at 10:43 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 6/5/2012 at 4:43 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)