Windows live mail error 0X800C013E after feature 2004

Anonymous
2020-06-02T13:31:06+00:00

After installing latest W10 update feature 2004  WLM fails on trying to read emails with error 0x800C013E .

Winver is 2004 (OS Build 19041.264) WLM version 2012 Build 16.4.3528.0331)

Any assistance would be most welcome.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

57 answers

Sort by: Most helpful
  1. Anonymous
    2020-08-04T06:56:03+00:00

    Hi.

    I had this problem 2 days ago after a weekend windows update.

    Unable to send and receive emails in our live mail. iiInet  (the online iinet webmail was OK)

    Anyway I did these registry changes and it seems to have corrected the incoming outgoing mail issue but it had removed all previous historical emails and also my sub inbox category set ups.

    Is this normal?

    Is there a way to get those settings bacK?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-08-03T15:51:16+00:00

    This Works!

    Thank you very much :-D

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-07-30T11:01:11+00:00

    Il faut remercie WLMUser2020 qui a propose la solution originale.

    Thanks for the credits.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-07-24T05:54:45+00:00

    The Thunderbird .eml import process is non-destructive, so you have nothing to lose by trying it.  If it doesn't work to your liking you can always continue to use WLM.  I have Thunderbird and WLM both configured for IMAP, that way messages stay on the server unless I move them to a local folder.  I didn't commit to Thunderbird until I was convinced it would work for me.  The Thunderbird .eml file import allows the option of importing all .eml files in a single folder or the option of including subfolders as well and you can choose to start the import from any point in the folder structure and specify the destination folder in Thunderbird.  If a particular import approach doesn't work to your liking, you can delete the local store in Thunderbird and try a different import strategy.  The Thunderbird import process follows the WLM hard file structure and is not aware of the virtual folder structure.  If the WLM hard file structure is the problem, you can create your own folder structure and copy the WLM .eml files to that structure and import from that.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-07-23T21:44:02+00:00

    Thanks for the suggestion to migrate to Thunderbird.

    Since it is my path names that are indeed very long due to migrating the message store across many versions of Windows since 15 years, the only way that today I can create a new folder in my WLM is to create it in the DRAFT folder which will result in the .eml files being in a windows hard folder that has a very short path name. Then I drag the reference to the newly created folder located inside DRAFT into my tree structure within my storage folder.

    My virtual structure is a tree made up of many branches and sub-branches, e.t.c. pointing to 30000 emails. I would definitely need Thunderbird to import the virtual structure but I have to wonder if it will create a hard structure where the emails are distributed in an arborescence that is faithful to the WLM virtual structure and not the WLM hard file structure.

    I would also hope that Thunderbird would remove the useless extra characters in the path names, which were full of repetitions of the string « /storage folder « repeated additionally for every time I migrated the message store to a new version of Windows.

    Was this answer helpful?

    0 comments No comments