VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed

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 have VS2010 and VS2012 on the PC. It was ASP.NET project and it didn't work for JS debugging. I try both version results was the same. Everything I did was out of success:

1. regsvr32.exe "%ProgramFiles(x86)%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll" - didn't help
2. Checked/Unchecked "Silverlight" checkbox at the Property Page - no
3. Downgrade from IE 10 -> IE 9 -> IE 8 - no luck
4. Repair VS 2010 - doesn't work for me
5. In IE "Advanced settings" unchecked "Disable script debugging (Internet Explorer)" and "Disable script debugging (Other)" - no

Finally, I have installed "Remote Tools for Visual Studio 2012 Update" and "VS2012 Update 4". I'm not sure what is fixed issue but it gone. And VS2010 and VS2012 started debugging JavaScript. Therefore, it seems some components were corrupted. Today, I think, best choice to fix this should be re-install IE, I mean downgrade it and install again, further you can install Update 4 for VS2012.

Please note:

"In Property Page window check box “Silverlight” must be unchecked"

Answer 2

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 3

Someone suggested that running this in an elevated command prompt would do the trick:

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

I tried it and it reported the dll was not found. I searched for the msdbg2.dll and it was not found. It is, apparently, hidden.

I ran:

regsvr32.exe "C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"

and it worked.

This was on Windows 7, 64 bit, VS2010 Premium

Answer 4

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 5

The IE10 upgrade resets a whole bunch of stuff. I followed 2 steps to fix this.

1. In IE Advanced settings, under browsing remove the tick on "Disable script debugging (Internet Explorer)"

2. Running this in command prompt (with administrator rights): -

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

The combination of these 2 and a browser restart of course fixed it for me.

I also agree, the marked solution above of un-installing is hardly a proper solution.

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)

Answer 7

Try to reset your IE settings and then uncheck "Disable Script Debugger (internet Explorer)" under Tools->Internet Options->Advanced and reset your computer.

Answer 8

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 9

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 10

I have had the same problem since updating to IE 10 on a Win 7 Pro machine running VS 2010 SP1.

I tried numerous suggestions, but none worked. I finally fixed it by downgrading to IE 9, to wit:

1. Type "appwiz.cpl" in the Win 7 Search Box under the start orb and hit .
2. Click on "View installed updates"
3. Search for "Internet Explorer 10"
4. Right-click "Internet Explorer 10" and select "Uninstall"
5. Reboot.

Debugging works again.

Answer 11

I have exactly the same problem .. I found a temporary solution but I have to execute each time the same sequence is as follows.

1. Click on the menu "Debug"
2. Click on the "Window" menu
3. Click on the menu "Processes"
4. And right click on iexplorer.exe and "detach the process"

The problem is that every time I have to repeat this procedure every compilation of my project ...

Answer 12

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.