Hi,
It just froze, no error message?
--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources -
http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2006 Jonathan Kay.
You *must* contact me for redistribution rights.
--
"Morten" <> wrote in message
news:12F2426D-2D21-4A52-A51D-...
> Hi there
>
>
> My computer kept freezing up like yours and WLM would just exit. After I
> installed the new Flash Beta from Adobe, it worked fine, though, so I suggest
> you try that to eliminate any Flash problems. At least this was a problem on
> Vista.
>
>
>
> Morten
>
> "kenneth" wrote:
>
>> Hi, I am experiencing problem with my WLM. Yesterday my laptop went into
>> hibernate mode as the battery went flat. When i charged it up again and
>> 'woke' my laptop up i realised i could not use my WLM anymore.
>> I could login just fine but when my contact list was displayed the WLM will
>> just freeze. Sometimes Live! Today will show, and the alerts for new mail
>> will show, but they are inoperational. My cursor will just switch to busy
>> (hourglass) when i move my mouse over WLM, Live Today, or the email alert.
>> The top part of WLM indicates that WLM is not responding and i have to
>> manually end task to close WLM. I've tried all the solutions posted on the
>> web including reinstalling fully/installing, doing regedit, and even system
>> restore, but to no avail. I downgraded to 7.5 and i could not use MSN as
>> well; it was only when i installed 7.0 that i can use MSN without it freezing
>> up.
>> One bizzare point is that i could use WLM IF AND ONLY IF i signed in using
>> another account.
>> I have erased the client cache by using the %appdata%\microsoft in RUN but
>> still after i login with my primary account, MSN would just freeze. If i left
>> it long enough it would be fine but i've only tried it twice so i cant be
>> totally sure about the length of time. When WLM freezes, CPU activity shoots
>> up to >90% and consumes way above normal resources.
>> Would desperately like to seek help from anyone out there.