Attaching the script debugger to process ‘iexplorer.exe’ failed

By | May 20, 2013
During web application development, sometimes we face strange issues. Applications or code snippets starts behaving abnormally. Same happen to me after installing Internet Explorer 10 on my machine with Windows 7.
“Attaching the script debugger to process ‘[4343] iexplorer.exe’ on machine ‘machine01’ failed. A debugger is already attached”

My development machine has Visual Studio 2010 that was working fine with Internet Explorer 9. After getting the newer version of IE, started facing the issue. I did some R & D online but most of the forum’s posts provided no appropriate solution to my problem.

One of the solution given by most of the forums is to uninstall the newer IE version and install Internet Explorer 9 again.I don’t consider it as a solution to my problem.

Finally, found out that registering “msdbg2.dll” can solve the problem. Simply close all instances of Internet Explorer and run the following command on Command Prompt:

regsvr32.exe “%ProgramFiles%Common FilesMicrosoft SharedVS7Debugmsdbg2.dll

For 64 bit Windows 7, above will be %ProgramFiles(x86)%

You can find the details about msdbg2.dll.

Category: Internet Explorer Visual Studio

About Web Development

Imran Abdul Ghani is working as Software Developer(Senior) with extensive knowledge in Web development technologies especially C#, ASP.NET, MVC, WCF, Web API, ADO.NET Entity Framework, jQuery etc. He has several years of experience in designing/developing enterprise level applications. He is Microsoft Certified Solution Developer for .NET (MCSD.NET) since 2005. You can reach his blogging at www.webdevelopmenthelp.net, www.topwcftutorials.net, and www.sharepointfordummies.net.

4 thoughts on “Attaching the script debugger to process ‘iexplorer.exe’ failed

  1. Helen W

    Thank you, thank you, thank you!

    Found this solution very quickly!

    Helen Warn

  2. bruce castro

    Thanks for showing various answers for this problem! For a web designer, checking the compatibility of a browser is needed and this command prompt really fixed the IE problem “regsvr32.exe “%ProgramFiles%Common FilesMicrosoft SharedVS7Debugmsdbg2.dll”.

Comments are closed.