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:
Excellent, it fixed my problem:
Win 7, VS2010, IE10
Thanks it fixed my problem!!!
gracias amigo
Thanks you!
call to dllregister failed is the new error
@Anonymous with the dllregister failed problem:
Did you run your command prompt as Administrator?
thanks a lot sr
great it works perfectly! many thanks That one developer :)
Problem resolved. Thank you very much.
Regards
Daniel(Singapore)
thnak you so much. Its resolved my problem.
Thank YOU!!!!
Excellent, it fixed my problem:
Thanks, why it happens?
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!
thanks ..it worked for me
Really Excellent ...........
Thank You
thank you, solved my problem
Amazing my friend. It resolved my problem. Thank you so much.
Works like a charm :) thanks poster
Thanks, this works perfect. Can someone explain why we need this? Why this is not done when update is installed on PC?
you are a rock star !!! Thank you so much for the fix :)
Thnx!!
Thanks for taking the time to post this fix.
Thank You. It fixed my problem
This worked. One nag out of the way. I verified the path was correct and ran the registry update.
thanks i fixed my problem
won't work for me. module couldn't load is the new error
@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!
Post a Comment