Attaching the Graphics debugger to process failed


I’ve just downloaded and installed Nsight Visual Studio Edition 4.0. However, when I tried to start Graphics Debugging, a window popped-up said that “Attaching the Graphics debugger to process ‘XXX’ on machine ‘YYY’ failed” (XXX and YYY are my application and machine’s name).
I’m not sure if I didn’t do the setting properly, but I think I did everything as the document written.

Is there anyone know what I should do? I’m using Visual Studio 2012.


On my tablet, under settings and developer, I had to tick the setting to allow debugging via usb.

Thank you for your answer. Could I ask where is that settings and developer?
FYI, I’m using PC.

I am very new to this, so cannot help much.
These are settings on an Android tablet which is attached via USB to my PC. I think it is the case that the package/program has to be downloaded to a tablet, or phone, and run from there - and that the debugger is expecting that kind of scenario.

If using the emulator, try:

Hi Noi,

This is a visual studio error we are getting sometimes - and the team is trying to better root cause/qualify what may cause this. It seems like running the following command has helped in some cases (but not all the time) - can you please give it a shot and let us know if it helps?

regsvr32.exe "%ProgramFiles(x86)%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll

Thanks, -s

Hi sdomine,

I gave it a try. Unfortunately, it didn’t help.

When I start Graphics Debugging, it seems like the debugger tries to open a lot of files. After a while (less than 20 files), it stops, then that window appears.

Anyway, thank you for your answer. I’m looking forward to hearing from you again.

Hi Noi,

We have just updated the Nsight 4.0 build with a fix for this issue. Please try this new version out.

Thank you

Hi Rafi,

It seems to work. Thank you so much :)


For anyone else with the same problem, running visual studio as admin also fixes this issue.