Windows live mail error 0X800C013E after feature 2004

This fix works well and saved me from having to rebuild a lot of email in a different program.  Thanks.  The German threw me a bit, but I was able to add the 3 DWORDS to the registry and assign them the number 1.  After rebooting Windows Live Mail now displays new email messages.

yes fantastic, worked no problem at all

Many thanks for the fix.  It worked for me after hours of searching for the fix.

Thank you so much, this resolved my issue.  I am a novice and was beating my head against the wall to get this issue resolved. Your instructions made it easy.

Those three DWORD's worked for being able to get/send email. However, even before the update to 2004, I occasionally would write a reply to an email, but when I would hit "Send", I would get a message box that said "The message could not be sent. A problem has occurred. Pleas try again.", but no amount of "trying again" worked either. However, I found that I could save the email to the Draft folder, then when I opened it from there and hit "Send", it would go fine. Now however, when I "Save" the email, I have no idea where it goes as it is not in the Draft folder! Any idea of a fix for this?

The DRAFT folder, like the INBOX folder, is one of the few folders in WLM that cannot be dragged elsewhere or deleted.

When I create a message and at the last minute I close the window rather than send it, I get asked if I want to save it. If I answer YES, WLM places my message in the DRAFT folder. Since I have 2 email accounts, I also have 2 DRAFT folders and depending on which account I am sending from, my saved message will be placed in the corresponding DRAFT folder.

If your saved message does not appear in (one of) your DRAFT folder(s) after saving it, then the next time you are about to save another message in a similar situation, add a unique 10 digit code to the bottom of the message text and then save it. Then use the search function to look across your whole message store for a message that has the same 10 digit keyword in the message body. You will see if and where WLM has placed the missing saved message and that may help you to better locate future lost messages.

To do your search, right click on each email account and also on the STORAGE FOLDER and select FIND, and then do each search including all sub folders while looking for the 10 digit keyword in the “message” field of the search window.

If like mine, your WLM message store has been built up over decades through a series of export/import transactions starting with Outlook (Express) and cascading across XP, VISTA, WIN7, WIN8, and finally to WIN10, then the following may be of interest to you, else please ignore it.

The biggest problem that I had with WLM is that my STORAGE FOLDER of 32000 emails is made up of physical folder names which in some cases are close to the limit of 256 characters long, due to multiple iterations of export/import. When you import, WLM adds the string “STORAGE FOLDER” to the physical folder name.

I have some subfolders where this string is redundantly occurring 4 times in a row. If during an import, the physical name tries to grow past 256 characters, a corruption occurs and emails get lost. Trying to add a new subfolder to an existing subfolder with an already very long filename also causes a corruption. You can only see how long your physical folder filenames really are by using Windows Explorer to navigate within the WLM message store.

To avoid this problem, I take advantage of the DRAFT folder located at the top of my STORAGE FOLDER tree.

Any new folders that I wish to create within my super large STORAGE FOLDER virtual tree must first be created in this DRAFT folder and then I drag the new folder into my STORAGE FOLDER virtual tree structure.

In spite of this dragging process, the newly created folder in DRAFT remains physically in DRAFT folder on my hard drive, but it appears virtually to be deep in my virtual STORAGE FOLDER tree where I dragged it to from DRAFT.

This way the physical folder's name remains very short and WLM does not crack as it did when I did not use this work-around.

During one past export/import of the message store, I tried to edit the physical export data file by removing all the redundant occurrences of the string “STORAGE FOLDER” which were concatenated in the folder names, but WLM would not allow me to import properly. Within the export file there may be hidden information that defines the tree structure both virtually and physically, and editing the physical without access to the virtual did not work for me.