Windows 7

Windows Live Mail Has Stopped Working

I am using Windows Live Mail on Windows 7 x64 Operating System. I can normally receive and read e-mails, but once I try to reply the message, my Windows Live Mail freezes and crashes.

With the help of my good friend from Microsoft, we run debbuger and found out that the problem is related to non-default spell checker.

If not automatically installed, once you open the message and start typing in order to replay, you might get a popup message asking you to download the spell checker for your language.

If you click Yes and install the spellchecker, you might have constant crashes of Windows Live Mail when you try to make a reply.


It seems that this is a bug in Microsoft Windows Live Mail application. Until this bug is fixed, you should do the following:

 - Open Windows Live Mail
 - Hit ALT on the keyboard to open the toolbar menu
 - Select 'Tools' from the menu and then select 'Options'
 - Click on the 'Spelling' tab
 - In the Languages list, find the English (United States) or English (United Kingdom), select it and click 'Set Default'

You're done! Windows Mail should be working normally now.



0 #13 Tanya 2013-04-12 21:50
Hello, I've been dealing with "WLM stopped working" issue for about two weeks now. First it would shut down and restart when I sent out an email, and now it wont even start up. I uninstalled the system and reinstalled it again but the problem doesn't seem to go away. I can't open the WLM to do what's stated here. PLEASE HELP ME!
0 #12 Todd 2012-12-12 19:49
Have tried the spell checker advice above, removing and reinstalling numerous times. Still doen't work. What a piece of crap MS has foisted on us unsuspecting users. Especially if this problem has been around for several years.
0 #11 Nik 2012-04-27 11:41
No, you won't loose any calendar entries since they are stored on Microsoft Servers.
Try to uninstall Live Products and then install Live Mail again.
If that won't help, try to use Revo Uninstaller application to completely remove Avast application (if there are any leftovers left).

You can also try to use the system restore to restore your system to a state before the Avast Antivirus. Hopefully that was not long time ago :)

0 #10 Norbert 2012-04-26 15:59
Windows Live Mail 2011 doesn't work properly after uninstalling avast anti virus with their uninstaller.
If I try to reply to a mail, or enter a new event in calendar I get the message: Windows Live has stopped working, WL will restart. After restart another message comes up: A problem has caused the programme to stop working correctly. I have tried to repair but the problem persists. I also tried the spell checker advice and made english UK the default laguage bu the problem persists. Also desktop gadgets will not display correctly anymore since uninstalling avast. I'm running WIN7. If I uninstall WL and reinstall, will I lose any calendar entries? Thank you.
0 #9 Dan 2011-05-12 22:05
I stopped using WLM because of this problem. In fact, I noticed this problem in 2008 on an old Vista PC. It's been over 3 years now. I can't believe they haven't been able to come up with a solution by now. The only thing that works is completely removing the dictionary file. When you do that, WLM starts warning you that you should install the Croatian dictionary file. Incredibly annoying.:sad:
+1 #8 sanford 2011-03-12 18:56
still not fixed tried it twice any thoughtsvx
0 #7 Nik 2011-01-15 22:00
Please check again if you followed everything right. Also, how is your error manifested?
0 #6 Gokul 2011-01-13 11:17
I tried as guided.... but the problem continues.... and I ma stuck badly
Jack H.
0 #5 Jack H. 2010-08-30 21:30
Thank you, Thank you, Thank you! But, my problem did not display anything about spellchecker. Once I tried to reply to or send a message, THAT's when I got the "stopped working" message above. When I set English as the default language, that took care of it. Now, it's working fine....
0 #4 Jeff 2010-05-09 06:21
thank you very much! My parents-in-law who live in Croatia were not able to send mails anymore. Thanks to your advice (and remote-access using CrossLoop) we were able to solve the problem!

Add comment

Security code