I also had this problem, but it was crashing also with the previous version Sadly this is now even worse. This is just typical Microsoft, replace an application that despite a few drawbacks actually worked and replace with a new solution with less core functionality and instability built-in.
They are a disgrace. The new MSN Messenger has very little to do with customers needs and more to do with a desperate attempt for MS to grab a slice of the social networking market and turn Messenger into a real advertising platform.
Stable functionality appears to be somewhat down the requirements. I hate Facebook too, it's taking over the world. Windows Live Messenger, fair enough it's social networking but if we aren't interested in Facebook, we won't be interested in using Windows Live, and if we did use it..
If people actually knew about this, they could quite Windows Live full stop. It could be possible, what do we all have in common because it could have some sort of compatibility issue? I have a dual screen, msn main window is on the primary screen and the conversations window is on the secondary screen.
Takes a least 1 minutes before a chat screen will open. Norton installed, de-install of nortin didn't fix the problem. My problem is that MSN crashes. It's not when I open a conversation, send a message or anything. It just Doing the steps above did not work as expected. When keeping the log-out window open, I can do whatever I want with it forever.
It will not crash. When you are logged in, it will crash. This is why I think it's related to wlcomm. If your steps, work for others I also use I. E9 instead of 8 ;. Although for the person who posted it, they had Windows Security Essentials. He put in an exception and it worked.
Although this doesn't work for me. Disabled all unneeded services to the bare minumum. Uninstalled anti-virus. Also uninstalled Messenger Plus! In all cases the "not responding" issue persists. When in "not responding" mode, freezes the computer no taskmanager or mouse move for up to 2 minutes. WLM is very useful facebook integration, etc. My problem, is just with WLM.
When it crashes, I can use anything on the computer except WLM. I can run up to atleast 10 Instances of Visual Studio smoothly before my pc crashes. It's just WLM. What I believe, is something is conflicting WLM.
It doesn't use too much memory or anything like that. What I find for me, is if I restart the computer, it may crash once or twice a day but let's say I don't restart for 1 week Which makes no sense what so ever.
This link did not help me, but may help some of you's. Of course, the most common method to fix a problem, is to completely reinstall WLM. Both these links are in the thread posted above, and neither helped me. The reinstalling, created the same effect as restarting Not all of us have the same problem, which makes it more difficult to figure out a fix but we can safely say WLM has it's whole bunch of issues. Windows Live told me to reproduce my logs.
During the process of doing this, Windows Live Messenger has stopped crashing! I have no idea how this has happened. I am now running Build Under Image Name, locate Nsvcappflt. I have unproposed because not all of us has Nsvcap. However, those who do have it - this will help.
There was definitely a conflicting issue and now it's gone. I did have an application for an MD5 Decryption. It required a registration and I did not want to do that - neither did I know why I even had an MD5 Decryption application.
I removed it. It's been working for over a month. I'm not sure if it's the removal of that application or it's because WLM was updated.
Whatever it was, it's now sorted. I'm sorry I can't produce anymore information to help anyone else. They do slowly reply, but be patient. They will more than likely ask for logs.
You could also go back versions, make a mark on what versions do not encounter the problem. That would help the team look into it further and maybe an update will be released to cure any ongoing issues.
I'm changing this to a Discussion seeing as many of us have different crashing issues. Someone could learn from this thread. I still wonder, what is the relation of automatically detect settings and windows live messenger. I was having an issue with opening and singing in messenger. I think it may have problems with the computer going into sleep. Seems the issue only arises after the computer goes to sleep.
The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums.
Windows Live Messenger Client: Development retired. Sign in to vote. I Have run multiple scans to try fix the problem but so far it has been unsuccessful. I am running Windows Live Messenger Build I'd like some assistance please. Monday, November 1, PM. I have the same problem. Every time I open the Window live messenger, it just said not responding but everything else works just fine!! Same problem too! Friday, November 5, AM. Same problem. When I'm opening a new conversation WLM freeze for 30sec.
And while typing a message it's random freeze for like 10sec. Very annoying bug :. Tuesday, November 9, PM. I'm experiencing the same problem. It started happening over a month ago with the previous version of Live Messenger which is why I upgraded to Upgrading didn't fix the problem and I'm still getting freezes when opening a new conversation window, clicking on the emotes button and sometimes randomly while using the program.
Wednesday, November 10, PM. I have the same exact issue. Windows Live Messenger just freezes and stops responding. I've also posted here but it seems that thread has gone dead. Recently a few of our users started having problems when signing into Windows Live Messenger. Once they provide their credentials and click on "Sign in", the client loads and loads and an error appears claiming that there is an internet connection problem with the Error Code: This error occurs on any versions of Live Messenger for those specific users.
The users can still access the web IM service of Live Messenger, but not sign into the client itself. Their internet connection settings point to a. We have a Squid Proxy Server version 2. Those were only added recently in an attempt to solve the problem, but to no avail. The rest of the company can sign in fine, with various versions of Live Messenger and so could the group of users in question. This discards the possibility of a proxy issue as the majority of the company can still sign in with no problems.
After trying all of that, Windows Live Messenger refuses to sign in. This is a huge problem for us a we use Live Messenger to communicate with clients and colleagues and also to provide technical support for users who travel overseas on business. Any help would be greatly appreciated.
Please let me know whether more information is needed. Thank you for your post, but trust me I've tried all of those steps and nothing has come of it.
I would have not posted here if it was literally a last resort and in the hopes of finding someone who has had the same issue and would be able to share how they've solved it. I've been struggling with this problem for about three weeks now and it's making me look like an idiot, :P. So, I managed to fix the problem temporarily for one of the users. Turns out the build version she was running was not running Build However the headache started all over again this morning.
Live Messenger is again refusing to sign in, despite all services connecting fine. The Error code I'm getting now is: Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question.
0コメント