2013-04-02

[SOLVED] "Attaching the Script debugger to process iexplore.exe failed" message after upgrading to Internet Explorer 10

HUGE thanks going out to Dmitri Leonov - MSFT in a stackoverflow article about the same message.
After updating to Internet Explorer 10, I started receiving the error when debugging with Visual Studio 2010:

"Attaching the Script debugger to process [####] iexplore.exe failed.  Another debugger may already be attached to the process."

The fix:

  • Close all instances of Internet Explorer.  (I will add you can leave Visual Studio open)
  • Run a command prompt as Administrator and paste this little gem into the command line:

 
It worked like a champ for me (and apparently others from comments on the stackoverflow post.)

Good riddance to an annoying message!  Happy coding.

27 comments:

Anonymous said...

Excellent, it fixed my problem:
Win 7, VS2010, IE10

Jesús Cerezuela said...

Thanks it fixed my problem!!!

gracias amigo

Anonymous said...

Thanks you!

Anonymous said...

call to dllregister failed is the new error

That One Guy said...

@Anonymous with the dllregister failed problem:

Did you run your command prompt as Administrator?

saikumar said...

thanks a lot sr

Zubair said...

great it works perfectly! many thanks That one developer :)

Daniel Tan said...

Problem resolved. Thank you very much.
Regards
Daniel(Singapore)

Anonymous said...

thnak you so much. Its resolved my problem.

Anonymous said...

Thank YOU!!!!

Anonymous said...

Excellent, it fixed my problem:

Cobaia said...

Thanks, why it happens?

That One Guy said...

I'm not sure why it happens, but I think it is because the msdbg2.dll file is unregistered when Internet Explorer 10 is installed, and since it was probably initially registered with the installation of Visual Studio, it never gets re-registered.

Someone correct me if I'm mistaken.

I'm so glad it is working for many of you!

Anonymous said...

thanks ..it worked for me

Anonymous said...

Really Excellent ...........
Thank You

Anonymous said...

thank you, solved my problem

Kiran said...

Amazing my friend. It resolved my problem. Thank you so much.

Anonymous said...

Works like a charm :) thanks poster

Anonymous said...

Thanks, this works perfect. Can someone explain why we need this? Why this is not done when update is installed on PC?

Anonymous said...

you are a rock star !!! Thank you so much for the fix :)

Anonymous said...

Thnx!!

Shalu said...

Thanks for taking the time to post this fix.

Anonymous said...

Thank You. It fixed my problem

Anonymous said...

This worked. One nag out of the way. I verified the path was correct and ran the registry update.

Anonymous said...

thanks i fixed my problem

Anonymous said...

won't work for me. module couldn't load is the new error

That One Guy said...

@Anonymous:
"Module could not load" or "Module could not be found?" Can you give us more specifics? We may be able to point you in the right direction.

It sounds like this fix did work for you as far as the script debugger error goes, though.

Best of luck!