Il faut remercie WLMUser2020 qui a propose la solution originale.
Thanks for the credits.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
Il faut remercie WLMUser2020 qui a propose la solution originale.
Thanks for the credits.
I found the below and it fixed my wlm issue:
Close Windows Live Mail.
In the registry under
Computer-HKEY_CURRENT_USER-SOFTWARE-Microsoft-Windows-Live Mail
create these 3 DWORD entries (i did not have them) or change them to 1 if available
RecreateFolderIndex=1
RecreateStreamIndex=1
RecreateUIDLIndex=1
Restart Windows Live Mail. After that, the message display at me goes back to normal and the 3 values in the registry are reset to 0. Can be left like this.
For me, the account display in WLM with multiple accounts was also corrupt after the Windows Update 2004. This is also fixed.
I would recommend exporting a copy of your registry ahead of an editing, and only edit if you are comfortable doing that.
Thanks
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.
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.
I think you are making the migration to Thunderbird harder than you need to. Just follow the process described at: https://support.mozilla.org/en-US/kb/switching-thunderbird . You don't need to export anything from WLM; Thunderbird does all the work and directly imports from the directory structure and .eml files located at "\AppData\Local\Microsoft\Windows Live Mail\Storage Folders". All of my .eml files in WLM are 21 characters long including the .eml extension. If the long file names you are referring to are the path names rather than the file name, then you can choose to import all the .eml files in a single folder rather than including subfolders. The ImportExportTools NG add-on in Thunderbird lets you specify the local folder or folders you want your .eml files imported to. The path length and hard structure / virtual structure are not constraints to migrating to Thunderbird if you use the import process described in the link above.