VS2010 and IE10 Attaching the Script debugger to p

Question

So I am using Win7 x64 with VS2010 and have installed the IE10 Win7 Preview and ReSharper 6.1.

When I attempt to Start Debugging, I receive the following:

"Attaching the Script debugger to process '[1111] iexplore.exe' on machine 'MINE' failed. A debugger is already attached."

I can click OK and look at attached debug sessions - [1111] is grayed out and there is another instance of iexplore.exe with my solution title. I can attach manually and it works fine.

I thought maybe since there were two iexplore.exe pids there would be something wrong, there are not two tabs or windows open and I disabled automatic crash recovery.

Tried this: Attaching the Script debugger to process '[XXXX] IEXPLORE.EXE' on machine 'NAME' failed

Did not work.

Any ideas?

Answer 1

I've got VS2010 & 12 and IE10, Win 7 x64.

I tried all of the above (except downgrading to IE9, obviously) to no avail.

I had a hunch that VS2012 Update 2 might fix the issue, and I was right.

No cmd, no re-installs, no re-boots. It fixed it for VS2010 & 12.

I hope it helps someone else too.

Answer 2

Even with the newly released IE10 for Win 7, the problem persisted. However, got the hint that installing VS2012 SP1 fixed this issue so I installed Visual Studio 2012 Express via Web Platform Installer (v4.5) -- seems to be fixed!

Answer 3

I had a similar problem (using VS2012 RC) after updating IE9 to IE10 - I fixed it repairing the VS2012 installation - I got there since I had a suspect Internet Explorer duplicate in the debug dropdown list and, even if the debugger was being launched, I could not find the symbols loaded.

In VS2010 for sure there is not that dropdown, but maybe trying to repair could be a fix.

Answer 4

I have had this same problem with VS2010 and VS2012 on WIN7 + IE10 CTP back in December last year. I hoped this problem was solved in the RTM version of IE10, today I found out it was not.

I have tried every solution in this post, even installing VS2012 update 2 CTP 4, but nothing fixed the problem.

I decided to revert back to IE9. I didn't use the correct steps which are described in the answer by MonteChristo.

I uninstalled IE10 by doing:

1. Win + R
2. appwiz.cpl
3. Turn Windows features on or off.
4. Uncheck Internet Explorer 10
5. Reboot

Now this doesn't revert to IE9. Is just removes IE10. Not what I intended. So I installed IE10 again by using the same steps as above.

After that I couldn't help myself to test it one more time and surprisingly it worked I got my Javascript debugging back. What I noticed is the following. Before I uninstalled IE10, the run / browse with (see image below) listed Internet Explorer twice.

After uninstalling, installing IE10 it's listed only once. I don't know if it's related but I wanted to mention it.

Answer 5

I was having the same problem with VS2010 & IE10 (Win7). After weeks of trying to resolve this issue I finally decided to fire up VS2012 to debug my site. I also updated VS2012 to SP1 and restarted my machine and now VS2010 debugging works fine in IE10.

So try installing VS2012 SP1 to fix compatibility issues with VS2010 & IE10.

Answer 6

There is a simpler fix for the JavaScript debugging issue in IE10:

1. Close IE

2. In elevated cmd prompt run this command:

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

(or %ProgramFiles% on a 32-bit OS)