My messenger 2009 is boned.

[Kilroy238]

AppName: wlcomm.exe AppVer: 14.0.8050.1202 ModName: ntdll.dll
ModVer: 5.1.2600.5512 Offset: 0001b1fa


I completely uninstalled all old versions. I ran zapmessenger.exe I have
never used windows blinds or any type of theme software. I deleted all the
old cache files.

But still every time I try to connect I get the crash. It doesn't kill the
program but it won't let me connect either.

<u>Windows Live Communications Platform has encountered a problem and needs
to close. We are sorry for the inconvenience.</u>

8.5 works just fine and server tests from 2009 say that it can connect to
the server but still no dice....

Any ideas?

TIA

 

[Jonathan Kay [MVP]]

Greetings Kilroy,

Another option you've not mentioned here is that some security/antivirus software is known to
cause this problem. You may want to (at least) temporarily uninstall (not just disable) any
such software, reboot and try after that.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog: http://www.messengergeek.com
Messenger Resources: http://messenger.jonathankay.com
(c) 2009 Jonathan Kay - If redistributing, you must include this signature or citation

 

[Kilroy238]

Thanks for the reply. I am running Kaspersky 2009 internet security.

I have done a complete uninstall of my anti virus but still no luck.
According to the connection tests everything is ready to go but when I try to
connect .

I use a router but I have tried connecting with and without the router still
the same error.

Windows Live Communications Platform has encountered a problem and needs to
close. We are sorry for the inconvenience.


Messenger does not shut down just won't connect.

Any other ideas?

TIA

 

[canada_67]

I'm still having exactly the same problem - any further ideas or should we
all roll-back to 8.5?

 

[Kilroy238]

i am rolling back to 8.5 for now. Maybe in another 6 months enough people
will have this problem MS will figure it out.

 

[Zsuzsa]

I installed live messenger 9.0 and dosn't let me sign in. Connection ok. How
I can uninstall it? it doesn't show up in control ad/remove. It doesn't let
me install 8.5. The computer did not have live messenger before.

 

[Zsuzsa]

Never mind this post I found out how to uninstall Live Messenger 9.0 simple :
Start, run and write in this:
msiexec /x {0AAA9C97-74D4-47CE-B089-0B147 EF3553C}
Than click OK. and will uninstall this horrible messenger!

 

[Kilroy238]

AppName: wlcomm.exe AppVer: 14.0.8050.1202 ModName: ntdll.dll
ModVer: 5.1.2600.5512 Offset: 0001b1fa


I completely uninstalled all old versions. I ran zapmessenger.exe I have
never used windows blinds or any type of theme software. I deleted all the
old cache files.

But still every time I try to connect I get the crash. It doesn't kill the
program but it won't let me connect either.

<u>Windows Live Communications Platform has encountered a problem and needs
to close. We are sorry for the inconvenience.</u>

8.5 works just fine and server tests from 2009 say that it can connect to
the server but still no dice....

Any ideas?

TIA

Nice to see that there is still no one that can help us.

 

[vlipje]

june2009 now and still no solutions known for this problem, still get the
error message in XP in Vista there are no problems yet

 

[Kilroy238]

It's plain to me the problem is not widespread enough for them to care.

So F'em 8.1 works good enuff.

 

[Kilroy238]

OK I finally fixed it. The problem was with the live call service and NVIDIA
Forceware Network Access Manager (AKA Nvidia firewall) not messenger itself.

That is why messenger never shut down from the crash.



Now this was a pain on my system. I read to just uninstall NVIDIA Forceware
Network Access Manager from the remove software section. Well it wouldn't
remove.

So I ended up using another program to quarantine all the running processes
of NVIDIA Forceware Network Access Manager at startup. Later on I will go
thru the registry and try to manually remove all the references to the
program.


But for now it is fixed.... Thanks to all the help I got from Microsoft
and all the ideas I got from the tons of helpful people here.


NOT!!