The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    ***MARCH 1 - Internet Explorer immediately closes with application error (mshtml.dll) - RESOLVED***

    Discussion in 'Windows OS and Software' started by BatBoy, Mar 1, 2011.

  1. BatBoy

    BatBoy Notebook Nobel Laureate

    Reputations:
    7,395
    Messages:
    7,964
    Likes Received:
    25
    Trophy Points:
    206
    Folks, just a heads-up -

    If any of you are suddenly encountering a crash when launching Internet Explorer and use either Norton Internet Security or Norton Anti-virus, please run the Live Update feature of the app.

    Apparently an update was pushed out today which is conflicting with Intrusion Protection. This issue has been resolved with an update however you will need to run Live Update to grab it.

    More info here:

    NIS Intrusion Protection crashing IE8 - Norton Community

    Hopefully, you will see this before performing a clean install or spending hours trying to track it down :(

    This is not a virus/malware issue.
     
    BatBoy, Mar 1, 2011
    #1
  2. duvallite

    duvallite Notebook Consultant

    Reputations:
    0
    Messages:
    119
    Likes Received:
    0
    Trophy Points:
    30
    Bummer. I just saw this post. Probably too late for me. I spent hours yesterday trying to figure out what went wrong, since this problem occurred immediately after installing W7 SP1. After trying several "fixes", now my machine is really hosed up. I haven't had the "heart" to fire it up yet this morning to see again how bad it is.

    Update: This was indeed the problem. I was able to run NIS Live Update, and got the patch that Symantec put out around 8:00 or so last night. Now I'll just need to re-install SP1 and reconfigure the tweaks I'd previously done. D**n Symantec for pushing out the 1st update that screwed things up. They should have caught the problem before the update was put out.
     
    duvallite, Mar 2, 2011
    #2