David’s Technical Musings

33 Responses to “Upgrading to IE8 breaks debugging with Visual Studio 2005”

1. MelDJsays:
   May 19th, 2009 at 7:22 am

   I have the same problem in VS 2008. The solution 2. I d´nt work. tnx

2. Normand Carbonneausays:
   May 22nd, 2009 at 7:54 am

   Thanks a lot,

   Solution 2 worked for me.

3. Eric Eggerssays:
   June 4th, 2009 at 7:35 am

   Yep, same thing happened to me. IE8 got installed, and the next time I tried to debug in Visual Studio 2005 it opened a new IE window, but never stopped at my breakpoints. I then noticed the “play button” was still enabled. Solution 2 got me back to what worked last week. Thanks so much!

4. Waynesays:
   June 10th, 2009 at 4:44 am

   Thanks for the fix. #2 worked like a charm. I had been chasing down this problem for a few days before we discovered that it was being caused by IE8. My co-worker found this post, and voila, all better.

5. C Schrodersays:
   June 11th, 2009 at 12:15 pm

   Thanks a bunch, this was giving me a headache! Solution 2 worked great.

6. Max Mosays:
   June 13th, 2009 at 11:14 pm

   Thanks David,

   Solution No. 2 did the magic.

   Regards,

   Max

7. Ruansays:
   June 14th, 2009 at 11:35 pm

   Thanks for this.
   I sat here for an hour trying to figure the problem and Option 2 solved my problem also.
   THANS AGAIN!!

8. Charithsays:
   June 18th, 2009 at 4:08 am

   Thanks! Solution #2 worked for me as well.

9. Prashant Yesodharansays:
   June 18th, 2009 at 7:12 pm

   Solution 2 worked for me.

   Thanks heaps.

10. Jeff Tributtsays:
    June 19th, 2009 at 12:13 pm

    Hey David…
    Great article as per usual. I’m going to just upgrade to VS 2008. Found it here: http://www.zoomtorrents.com/index.php?file=Visual_Studio_2008_Developer_Edition

    Should I get the professional or developer? what’s the diff>

11. Ericsays:
    July 1st, 2009 at 8:58 am

    Solution #2 also worked for me (VS 2005) Thanks for the info.

12. Giladsays:
    July 2nd, 2009 at 5:53 am

    Thanks,
    Solution #2 was great for me.

13. Charlessays:
    July 25th, 2009 at 4:08 am

    Thanks, Solution 2 was the way to go for me. I’m realy disapointed in Microsoft, breaking their own products

14. Darrensays:
    July 28th, 2009 at 9:40 am

    #2 worked fine, thank you.

15. retnetsays:
    August 15th, 2009 at 9:31 pm

    good work with solution 2, thank’s.. good sharing.

16. Min Liusays:
    August 28th, 2009 at 4:24 am

    Thanks, Solution 2 works for me.

17. Eidensays:
    September 15th, 2009 at 2:27 am

    Great, after some head scratching I also found that having no ie windows open works, so I figured the VS debugger was having trouble attaching to the right process.

    Solution 2 worked for me. Btw, if it doesn’t work for you, as well as HKEY_LOCAL_MACHINE, try adding to ‘HKEY_CURRENT_USER -> SOFTWARE -> Microsoft -> Internet Explorer -> Main’ in the same way.

18. Chrissays:
    September 15th, 2009 at 8:03 am

    Solution 2 worked perfect. Why doesn’t Microsoft have this in a knowledge base or fix it in an update? What the heck! Thanks for the solution!

19. Randysays:
    September 22nd, 2009 at 10:20 am

    Solution 1 worked (but not very useful), and solution 2 really worked!
    thanks!
    I am using VS2003 with same issue… and this fixed it…

20. Kevinsays:
    September 23rd, 2009 at 9:08 am

    Solution 2 worked for me. Thanks for posting David!

21. rameshsays:
    October 1st, 2009 at 7:36 pm

    Thanks.. solution worked for me…

22. sarankamalsays:
    October 8th, 2009 at 11:08 pm

    Thanks David,

    This worked Great for me.Please give some keywords to reach this page, people search from google.
    Thankyou very much.

23. Kishoresays:
    November 3rd, 2009 at 12:08 pm

    Thanks a lot! The second solution worked for me.

24. Allasays:
    November 3rd, 2009 at 12:08 pm

    Modifying the registry solved the problem. Thank you very much!

25. Maheshsays:
    December 2nd, 2009 at 1:04 am

    Great,,,Second option did work for me
    Thank u so much…..
    how did u get this soultion ????? really greatt….
    Keep Posting such solutions

26. Vafasays:
    December 2nd, 2009 at 2:02 pm

    thanks, man,
    the only missing part is “how to deal with 64 bit”, so you need to open HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main insetad of 32 one, and the other point is DWORD needs to be 32bit instead of 64. thanks again

27. Anil Bansalsays:
    December 11th, 2009 at 1:00 am

    thanks, solution #2 works without any problem to system & IE8

28. Jareksays:
    January 9th, 2010 at 5:29 am

    Thank you :). #2 worked perfect.

29. bzbEldersays:
    February 13th, 2010 at 12:03 pm

    Great Stuff!
    XP 32bit SP2, VS2k5, 2nd solution worked like a charm.
    Thanks!

30. Asimsays:
    February 18th, 2010 at 2:29 am

    Thanks a lot dear, Solution#2 worked.

    Asim

31. janasays:
    February 23rd, 2010 at 3:21 am

    Thanks

32. Erinsays:
    February 24th, 2010 at 12:51 pm

    Would have never guessed IE was the cause. Thanks!

    I’m working with 64 bit, and used solution #2 except I used HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE as Eiden described, and still used DWORD (32 bit). I tried using DWORD and QWORD (64bit) in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main as Tafa mentioned but neither worked for me.

33. simhasays:
    February 25th, 2010 at 8:51 am

    Thanks a lot! The second solution worked for me.

Leave a Reply