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.

    IE8 Locked Until MSN Toolbar Loads, anyone else?

    Discussion in 'Windows OS and Software' started by Rodster, Aug 7, 2009.

  1. Rodster

    Rodster Merica

    Reputations:
    1,805
    Messages:
    5,043
    Likes Received:
    396
    Trophy Points:
    251
    I've encountered an issue recently on several computers running IE8 w/MSN Toolbar. IE8 is locked an inoperable until MSN Toolbar loads. I like MSN Toolbar but I wanted to see if anyone else has been plaqued by this as well. I hate it when stuff only happens to me, LOL. :D

    Anywho, it appears the trouble for me started when MS issued a recent IE8 compatibility update via Vista's updater.
     
    Rodster, Aug 7, 2009
    #1
  2. jackluo923

    jackluo923 Notebook Virtuoso

    Reputations:
    1,038
    Messages:
    3,071
    Likes Received:
    1
    Trophy Points:
    105
    can you check if it's actually msn toolbar that's causing the problem?

    go to tools->manage addon the check out the load time of each of your addon.
     
    jackluo923, Aug 7, 2009
    #2
  3. Rodster

    Rodster Merica

    Reputations:
    1,805
    Messages:
    5,043
    Likes Received:
    396
    Trophy Points:
    251
    Yup that's definitely the problem. I disabled MSN Toolbar and MSN helper and IE8 loads and is fully functional instantaneously. I checked the load time for toolbar and it's only 0.03 seconds which shouldn't be a problem but it is.

    Like I said all my laptops running Vista now appear to have this delay. Some are not as extreme depending on the CPU. Also as I mentioned earlier it may or not be a coincidence that it happened after the recent IE8 compatibility update.
     
    Rodster, Aug 7, 2009
    #3