none
Windows Live Email: "A problem occurred while trying to open this message."

    Question

  • I'm running Windows 7 Professional.   Windows Live Mail started giving me the message "A problem occurred while trying to open this message." any time I try to open a message (including old ones).  I've unistalled all of Windows Live Essentials which includes Windows Live Mail. I also cleared the registry entries for these and then rebooted and reinstalled All of Windows live Essentials.  I imported the email I exported before I unistalled Windows Live Email.  I get the same message when I try to open any email, old or new.

    Any Suggetsions will be appreciated

     

    Saturday, December 18, 2010 5:04 AM

All replies

  • I had the same problem and found a solution. Go to uninstall software and select uninstall for Windows Live Essetials 2011. You will be given the option to uninstall it or repair it. Select "Repair". Takes a few minutes but should eliminate the message. Did it for me. Good Luck & Merry Christmas!
    • Proposed as answer by Nerill Monday, February 14, 2011 1:44 PM
    Thursday, December 23, 2010 12:54 PM
  • I tried the repair before uninstalling. I still have the issue after doing both.
    Thursday, January 06, 2011 1:22 AM
  • I have the similar or same problem.  Last night everything was fine.  This morning I cannot read any mail new or old (double click doesn't open the popup).  I cannot access my address book at all. 

    Repair does nothing to help.

    Bumping this thread.  Does anyone have a solution?

    Thursday, January 20, 2011 4:10 PM
  • I have the similar or same problem.  Last night everything was fine.  This morning I cannot read any mail new or old (double click doesn't open the popup).  I cannot access my address book at all. 

    Repair does nothing to help.

    Bumping this thread.  Does anyone have a solution?

    Thursday, January 20, 2011 4:10 PM
  • I have a similar problem.  Although I can open my emails I can not send any.  I can't even write any.  If I click reply or new I get the same message.  It seems to have coincided with a windows update but there's no solution so far.
    Thursday, January 20, 2011 7:27 PM
  • Me too.  I can open incoming mail but get the error when I click "Email message", "Forward", or "Reply". 

    So I can hear but I can't speak, and I'd much prefer it the other way around. 

    I tried shopper2's suggestion; no help but thanks for trying.  It spent a couple of minutes repairing (whatever tf that means) Windows Live (dead) Essentials 2011, then asked for a restart and received same.  Problem remains. 

    If anyone at MS is listening: how about spending a few thousand of those billions on this problem?

     

    Friday, January 21, 2011 7:27 AM
  • I've had this problem several times since I've been using Windows Live.  Today, had several that I couldn't open. 

    Friday, January 21, 2011 10:32 PM
  • This is the Windows Live Writer forum.

    Support for Windows Live Essential applications are available in the Windows Live Solution Center

     http://answers.microsoft.com/en-us/windowslive/forum/livemail


    ...winston
    MSFT MVP Live Mail
    Sunday, January 23, 2011 3:24 AM
  • Ditto... BUMP! BUMP! BUMP!!!!

    Anyone? I guess it's Outlook for now...

     

    rags

    Thursday, January 27, 2011 11:23 PM
  • I had the same problem and found a solution. Go to uninstall software and select uninstall for Windows Live Essetials 2011. You will be given the option to uninstall it or repair it. Select "Repair". Takes a few minutes but should eliminate the message. Did it for me. Good Luck & Merry Christmas!
    It worked to me too!!!!! Thanks. It was rather annoying to see new email messages on my inbox but not been able to open them. ;-)
    Monday, January 31, 2011 8:06 PM
  • I too tried, and it worked. As an IT pro, this would be the first step I would suggest.  If it does not work for you, then other options would be in order, but at least the simplest solution has been attempted.

     

    Also, as an IT pro, it would be interesting to know exactly what WAS fixed with this solution.

    Monday, February 14, 2011 1:47 PM
  • Worked!, Cheers.
    Tuesday, April 26, 2011 10:08 PM
  • Actually, it worked for a while, now they're not opening again.

    Cheers.

    Friday, April 29, 2011 10:18 PM
  • Now I'm getting this message. I switched from Outlook to Windows Live because of the issues with Outlook.  I went to your link- it's absolutely ridiculous that you tell people to back up, delete registries, uninstall, reinstall, etc...  When is MICROSOFT going to provide a fix for this issue instead of putting it back on the consumers?   Do we all have to abandon MS email and go to gmail/yahoo,etc...?    I read the feeds and the suggestions are tried and do not work. MS needs to provide a fix for this.   Incidentally, this problem did not start until my computer ran MS updates this evening....   Time for Apple?????
    Friday, June 17, 2011 2:31 AM
  • I also got this after updates were installed. What the hell? I thought updates were supposed to improve not destroy....
    Friday, June 17, 2011 5:24 AM
  • Worked!, Cheers.
    yes!!! worked .
    http://makemoneyhomebusinesscenter.com
    Friday, June 17, 2011 9:00 AM
  • You state you've had this problem several times. 

     

    How did you resolve initial instantces?

     

    artreid44@hotmail.com

     

    Tuesday, June 21, 2011 9:09 PM
  • "repaired" twice. did not solve "A problem occurred while trying to open this message."
    Wednesday, June 22, 2011 3:52 PM
  • I get the same message except it's when I try to compose a new message.  Tried the repair and it didn't work.
    Thursday, June 23, 2011 2:48 PM
  • We've had the same problem for the past week. After checking replies, trying Windows Live Essential repair, defrag, registry cleaner/repair, etc., still frustrated!

    . . . . and waiting on a solution from Windows - more than a few of us are suddenly having this problem

    Friday, June 24, 2011 3:13 AM
  • Ottabe, I had a similar thing happen, but it turned out to be in the midst of 32 "Automatic Updates" from Microsoft on 18 June.  They came in two batches, 26 and 6.  After  the initial 26 self-installed, the problem you describe started.  I worked on doing all the things that have been suggested, including removing and re-installing Windows Live Mail all to no avail.  Then, after the next 6 updates a day and one-half later, I could Reply, Create and Send eMails again.  The real pain came with restoring my "Exported" messages.  The export process seems to do weird things creating empty folders with valid names and folders with strange, unfamiliar names (e.g., "Frontier (l b51" & "Imported Fo c25") that contain properly archived folders (e.g., Family, Social, etc).  I agree with you about Microsoft getting on the ball about fixing this problem - the Posts on this problem go back nearly a year and seem to come in batches.  Look what Tina1966 said above about MS Updates on 17 June - an unrelated witness and she has a good point about MS.  Here we are floundering in the wilderness with no help from MS and little hope that there will be.

    Sunday, June 26, 2011 5:43 PM
  • I searched and found Mr. Fixit

    http://support.microsoft.com/kb/910336

    I ran it and can now create messages. I wonder what other effect it will have on the system

    Thanks Dragonfly (and others)

    • Proposed as answer by NetReamer Saturday, July 02, 2011 4:00 AM
    Monday, June 27, 2011 4:12 PM
  • I had the same problem and found a solution. Go to uninstall software and select uninstall for Windows Live Essetials 2011. You will be given the option to uninstall it or repair it. Select "Repair". Takes a few minutes but should eliminate the message. Did it for me. Good Luck & Merry Christmas!


    Thanks a lot. This solution worked for me.

    I am able to reply and forward emails now.

    Thursday, June 30, 2011 7:23 AM
  • I searched and found Mr. Fixit

    http://support.microsoft.com/kb/910336

    I ran it and can now create messages. I wonder what other effect it will have on the system

    Thanks Dragonfly (and others)


    I was helping out a friend that had this problem (the error message in question) when trying to compose new messages.  The default behavior (I didn't need to try the aggresive) of the MS fixit in KB910336 worked like a charm for her.  Thanks.
    Saturday, July 02, 2011 4:04 AM
  • I tried all of the above including the aggressive fix and still can't compose or reply to email.
    Saturday, July 02, 2011 5:53 PM
  • I tried all of the above including the aggressive fix and still can't compose or reply to email.

    Same as you Lulu, I've tried all the suggestions above and no resolution.
    Friday, August 05, 2011 10:14 PM
  • The uninstall/repair worked for me. I dd notice that my email compose/reply/forward stopped working after I installed 14 Office 2010 updates.  Could that be the cause?
    Saturday, August 06, 2011 4:58 PM
  • Unlikely

    Office (2010, 2007. 2003) updates don't change Windows Live Mail files or program.


    ...winston
    MSFT MVP Live Mail
    Sunday, August 07, 2011 1:46 AM
  • Repairing 'Windows Live Essentials 2011', on Windows 7, worked for me.
    Sunday, September 18, 2011 12:03 AM
  • I am fed up with Live Mail.  The problem continues no matter what I do, and about one in five tries do I bring up the contact names when composing.  People bitched about Vista but at least MS Mail worked great.

     

    Sunday, October 02, 2011 3:07 PM
  • hi,

    yes i do agree  with you that it works.... really works...

    thanks for sharing...

    -----------------------------------------------------

    niteshahir

    www.esparkinfo.com/

    Tuesday, October 04, 2011 6:49 AM
  • Okay, I am tired of Live Mail, and want to try Thunderbird.  I have downloaded it and love the format.How can I get all my contacts transferred from Live Mail?

     

    I have farted with Live Mail for over a month, and opening messages takes forever, and trying to bring up recipients when creating new message is impossible.  What piece of garbage, and this is an improvement?  MS needs to take this program down.

    Thursday, October 06, 2011 2:15 PM
    • close your windows live email:
    • run as a cmd admistrator: sfc /scan now
    • reopen windows live email

    Good luck!

    • Proposed as answer by still_trying Monday, December 31, 2012 6:47 PM
    Saturday, July 14, 2012 3:34 PM
  • @newuser7

    1. This forum is defunct. For Windows Live Mail support (questions or answers) --> http://answers.microsoft.com/en-us/windowslive/forum/livemail

    2. The last post in this thread was approx 8 months ago.


    ...winston
    MSFT MVP Live Mail

    Sunday, July 15, 2012 12:16 AM
  • Now, Live email is working well, But i want to set up in my signature my website http://www.vemaybay999.com, I don't see where to set it
    • Edited by MrVi Sunday, July 29, 2012 6:22 AM
    Sunday, July 29, 2012 6:21 AM
  • hi,

    yes i do agree  with you that it works.... really works...

    thanks for sharing...


    How does it works, could you please tell me the solutions. Thanks in advance.
    Monday, October 08, 2012 3:46 PM
  • THUMBS UP TO YOU, I AGREE A THOUSAND PERCENT WITH YOUR COMPLAINT AGAINST WLMAIL ESSENTIALS.  DITTO FOR ME A MILLION FOLD!!!  THIS EMAIL PROGRAM IS PURE GARBAGE.  BESIDES HAVING THE GLITCH OF THIS THREAD, I HAVE TONS OF OTHER ONES, SOMETIMES ALL AT ONE TIME.  MICROSOFT IS THE PIT OF A BUNCH OF CROOKS STEALING OUR MONEY, OUR PEACE, AND OUR HEALTH AND MENTAL HEALTH TOO!!!!!!!!!!!!!!!!!!!!!!!!!

    WHEN THEY SIMULATE TO "HELP US" THEY ASK US TO DO DRASTIC THINGS LIKE UNINSTALLING/INSTALLING AND SENDING US TO A MERRY-GO-ROUND...

    THEY EXPECT US TO DO THEIR WORK BY THRUSTING ON THE MARKET UNFINISHED PROGRAMS FOR US TO SUFFER THE CONSEQUENCES AND GIVE THEM FEEDBACK.  THEN THEY THRUST TO THE MARKET ANOTHER ONE WITH THE FEEDBACKS INSTALLED....BUT WAIT!  THESE HAVE A LOT OF GLITCHES TOO....SO, AGAIN A MERRY-GO-ROUND!!!!!!!!!!

    MAY THEY SUFFER THE THOUSAND AGGRAVATIONS WE SUFFER ON THEIR MISERABLY DONE PROGRAMS!!!!!!!!

    Sunday, November 17, 2013 4:38 PM
  • Hi artreid, did you get an answer to your private email?  If it worked please let me know?   nuevadela2@rcn.com (of course I won't be able to open it because of this glitch here, but hopefully I will sometime....)
    Sunday, November 17, 2013 4:42 PM
  • This forum (Live Writer) is defunct and has been for over 2 yrs when all support from MSFT transitioned to answers.microsoft.com

     i.e. No one from MSFT is monitoring this forum

    For MSFT support on Windows Live Essentials (2009, 2011) or Windows Essentials 20012 use the following link

    http://answers.microsoft.com/en-us/windowslive/forum/

    • Scroll down and choose the appropriate application in the 'Product' field -

    .e.g Live Mail support would be found here

    http://answers.microsoft.com/en-us/windowslive/forum/livemail/

    Also, I don't think artreid is monitoring this thread either...his last post/feedback was approx. 2.5 **years** ago

    Finally, no one is stealing your money when using Windows Live Essentials or Windows Essentials - it's free unless someone managed to convince otherwise.


    ...winston
    MSFT MVP Consumer Apps

    Sunday, November 17, 2013 11:34 PM
  • Hi, I was having this exact problem. Uninstall didn't work, neither did repair.

    Analyzing with PROCMON I found it was trying to create a temporary file somewhere in the user profile (C:\Users\%userprofile%\AppData\Local\Temp) and it needed admin access. After the re-install etc I ran as administrator and it worked.

    I think it needs an uninstall/re-install first as my customer said they had tried just running it as admin before and it did not work.

    hope this helps.

    Wednesday, August 05, 2015 3:38 PM
  • Dear fellow detectives, let me share you some information after my own Sherlock Holmes session with Windows Live Mail 2012 on Windows 7 yesterday.

    At first I tried the repair/reinstall thing multiple times, it didn't work.

    Then I thought, if I'm lucky the programmers might have built in some logging into the application, and it will leave some information traces in the eventlog or something, so I looked in eventvwr.exe, but alas, no information.

    So I looked further for diagnostics, and there it was! Options -> Advanced tab -> Maintenance button, on the bottom there is a section "Trouble shooting". Lo and behold, you can check the "E-mail" checkbox. So now I try to reply to an e-mail again, same error message ofcourse. and I now I open the log file, which has thousands of lines of every little thing it does, and amongst that there I saw this section:

    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (contenteditorfactorymanager.cpp:76), failed with 0x80131018  
    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (contenteditorfactorymanager.cpp:191), failed with 0x80131018  
    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (contenteditorfactorymanager.cpp:237), failed with 0x80131018  
    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (composehost.cpp:643), failed with 0x80131018  
    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (mehost.cpp:3840), failed with 0x80040104  
    [23:57:44.18] 1e58                 Mail:            Zone_MailChk ERROR: (note.cpp:3088), failed with 0x80131018  

    This looked very suspicious, looks like it can't fire up the "contenteditor", which I assume is the message edit window. This seemed like a good hint to finding the root cause and so I decide to dig deeper with this information.

    Googling for error 0x80131018 didn't give me a very clear idea of the problem, but I did see some posts about failing to load .NET assemblies and NGEN. I had a hunch a failure to load a .NET assembly might actually be it. I vaguely remembered that it's possible to monitor the loading of .NET assemblies, including any failures of doing so. The tool is Fuslogvw.exe, so I fired it up, and chose some path to log into and pick some detailed level of logging. And voila, bingo!

    *** Assembly Binder Log Entry  (17-11-2015 @ 0:22:43) ***

    The operation failed.
    Bind result: hr = 0x80131018. No description available.

    Assembly manager loaded from:  C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
    Running under executable  C:\Program Files (x86)\Windows Live\Mail\wlmail.exe
    --- A detailed error log follows.

    === Pre-bind state information ===
    LOG: User = PC-51873942\Wout
    LOG: DisplayName = System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
     (Fully-specified)
    LOG: Appbase = file:///C:/Program Files (x86)/Windows Live/Mail/
    LOG: Initial PrivatePath = NULL
    LOG: Dynamic Base = NULL
    LOG: Cache Base = NULL
    LOG: AppName = NULL
    Calling assembly : WindowsLive.Writer.PostEditor, Version=16.4.3528.331, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
    ===
    LOG: This bind starts in LoadFrom load context.
    WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
    LOG: No application configuration file found.
    LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
    LOG: Post-policy reference: System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    WRN: Found match in cache, but cannot create assembly from the cache information.
    ERR: Unrecoverable error occurred during pre-download check (hr = 0x80131018).

    It failed to load the .NET 2.0 assembly System.dll when firing up the message editor. I figured the .NET assembly was ngen-ed (precompiled), and that the ngen native image was potentially broken. I didn't really manage to repair the ngen native image unfortunately, and I didn't have much faith in fixing this one assembly to solve everything (I already tried scanning and chkdsk for errors and that didn't help either, which should repair .NET corruptions, although they did find/recover some errors. I also tried the NetFxRepairTool with no results). So in my case I decided to reinstall my Windows, because I figured there might be a whole lot corrupted (while gaming my system black screened and did some odd stuff, and I think at that moment some things got messed up), and I rather spend a few hours reinstalling than days fixing the next little thing and the next. Reinstall worked ofcourse, there was also nothing wrong with the e-mail database as is suggested in some forums.

    Conclusion: Windows Live Mail itself was not broken, the mail database was not broken, but the .NET 2.0 framework (or parts of it) were corrupt. What Microsoft could (and should) do is give the user a proper error message so he knows what is broken, and what to do to fix it. From googling it looks like there are thousands of people with this problem, and I can't believe that nobody at Microsoft bothered to get to the bottom of this. When seeing all these reports they could have easily improved there error message handling and they would have very soon found out about what the problem was.

    For donations you can contact me.

    - Wout

    • Proposed as answer by wout11010110 Tuesday, November 17, 2015 5:01 PM
    Tuesday, November 17, 2015 4:58 PM
  • This worked for me.
    Wednesday, January 06, 2016 8:26 AM