How to reinstate WinMail onto Windows 8/10/11

[endeavor]

Quite frankly it's not fair you having had me spin my wheels because of the lack of 'upfront' information you left out, including that your message store location was changed from default to E:\ Duh! ..I had asked you over and over about details and you ignored many of my question marks! Anyway some of these previous unneeded posts now are a distraction for new members coming to this forum to use WinMail default, on an already complicated subject as it is. ..no worries, but next time please.

I guess the main issue here is how to get a working store file because it keep asking for one regardless if my folder is empty or not. It won't create a fresh one.

Your database is corrupted "DatabaseCorrupt"=dword:00000001" ...and since you asked, in your case you cannot just delete individual WindowsMail.MSMessageStore files within the store folder either (which normally would work only for very specific instances) ..but in your case it has to be the whole Folder that is Deleted. (not to worry you will have them in a zip for future, extract elsewhere, point to, import emails if you want to) And you cannot use your source registry info that you posted from your old registry, because when you first merge it and on re-instate of a first start WinMail, in timing it could write its own intended default entries overwriting yours, and so on and so forth it can get complicated if not done right.

However everything within the WinMail tutorial and built-in WM reinstate process is geared for Default WinMail users.

I will have to write a warning about this in all the tutorials Back/Restore procedures! ...edit: Done!

Okay I am only going to say this once for you killer, just because I am Trying to be a nice guy here, to get you going @ Default!
For you, in your specific situation, take any E:\ Windows Mail store folders you have, zip them, label them, delete folders.
Also , navigate to: C:\Users\yourcomputersname\AppData\Local\Microsoft\
Look for any (same or different dated) "Windows Mail" store folders in here, zip it, name them something, and delete them.
Check to see in 'Task Manager' and clear any errant/hung instances of WinMail.exe running, and 'end task' on any/all of them.
Now in order to get your WinMail to scratch and open up, now that you finally told the whole truth of your story (grrrrr)
Here's a new twist to the procedure I wrote you before:
1. Open regedit, navigate to:
"HKEY_CURRENT_USER\Software\Microsoft\Windows Mail"
right click on it, delete it, yes that's right, delete this whole registry "Windows Mail" folder key! (no worries)
- Do Not at any time merge your old reg! -
2. Delete, yes right click on and Delete any 'Windows Mail' store folders located at:
C:\Users\yourcomputersname\AppData\Local\Microsoft\ .....right click and Delete: Windows Mail (of any names)
3. For your v1709, then from post 1 & 2 on the tutorial, as long as you have all the proper files in their proper place?
..only then you will now need to (download) merge these '3' reg's Again!
~ WinMailEdit.reg.zip
~ reg_v1709+.zip
~ 5-2018_UpdateReg.zip
..unzip and merge them.
..remember, do not merge your old reg !
This is only to get your Winmail to startup and everything to be base, Default, in its default location
That's it..
...Now when you start WinMail and she opens up, it will auto finish rebuilding proper your WinMail registry entires, and recreate a new store folder in its Default location! ..leave it there! ..for now.
I've tested your scenario on my test bench, and what I wrote you here is confirmed working!

The 'manual' importing of any old emails I've already mentioned in my previous post in the EDIT, still applies here.

killer, after you get it working @ Default, then in this and in all WM re-reinstatement process it's not recommended to move the store folder! ...because everything within the reinstate procedures is geared toward @ Default. Moving the store folder you are asking for your kind of trouble - however importantly the WinMail reinstate process was not designed to work for you in that situation so take notice! Also, most likely every major Windows Update (which we all have to re-run the tutorial again to get WM going ...easy) ...but in the case of someone with a re-located store folder will most-likely have this extra issue every time too.
I am not saying it's impossible to have a store folder in a different location, thinking it over I could do it and succeed though an update with some back-n-forth maneuvering, but why bother for such very little advantage? ..actually imho it's a disadvantage.
...but for You right now, it's needed to clear out corruptions, and get back to default to get her to open and working again first!

All the information you need is here and on page1+2
The only reply I really want to hear back from you killer, is an ecstatic yes! ...it opens and it's working!

Also btw, don't forget to read the bottom of Post #451

 

[killer]

Endeavor, thanks for your patience! It works now! I could open up a fresh blank winmail where I am free to import my mails and accounts anyway I want!

The post 1+2 works better than previously. You must have refined it. I didn't need to read anywhere else to get it started up quick.
My current Win 10 version is 1803 Build 17134.48

 

[endeavor]

It works now!

It always worked

You must have refined it

I can promise you no files were changed since your very first post!
...it's just what You did with them that has changed

The only difference is that I wrote up specific instructions to fix/reset yours in my previous post, is when you told me you had a relocated store folder, and you upgraded, and your WM would not open with that particular error, and I saw you had a corrupted store folder.

If anyone performed my previous posts instructions exactly it fully resets WinMail for v1709+ back to 100% 'first open' Default

However if anyone keeps an updated Backup/Restore procedure, you will NEVER have a need to reset it like that!

Anyway, killer, I am happy for you, and am proud of you for finally getting a handle on it.
Once you get the different procedures and scenarios down, you will be an expert

..and really it's all very easy (for seasoned computer users) ..I just had to write that big pink disclaimer for appropriateness.

 

[BridgeHead]

Just upgraded another laptop to Windows 10 version 1803. After carefully completing all the steps, WinMail booted up the first time, albeit without message rules and requiring passwords. So I immediately closed down and ran the .reg file I had recently saved with all the WinMail entries in it. While I was not surprised to see the message rules come back, what did surprise me was that the passwords for all the accounts were also in place. I never thought about it, but the passwords must be contained in the registry. It was also nice that I didn't have to use the recent backup since as endeavor has previously noted, the data files were not touched.

 

[endeavor]

Passwords are not stored/located in the registry, but instead within the xxxxxxx.oeaccount files.
Also, performing OS upgrades do not remove server passwords on an established WM and will remain, not needing reentry. However when doing any Fresh OS install with a WM reinstate using the Backup/Restore method to replicate your previous setup over to your new OS, you will then need those passwords to be manually entered once, when the handshake happens with the target server itself asking to be confirmed; it's an appropriate security check.

 

[BridgeHead]

Hi. I apologize in advance, but not sure if there is a better place to ask this question. I have two computers running WinMail on Windows 10 version 1803. They both seem to have regular problems when replying to messages in that they will hang up. At first there will just be a spinning circle which significantly delays typing in the message field. If the message isn't completed in a minute or so, the entire application will hang requiring an end process and restart.

Has anyone else seen this behavior or have any idea what could be causing it? I have no problems in creating new messages or forwarding messages only when replying.

Thanks in advance,
Don

 

[endeavor]

Don,
As I briefly looked back months ago at some of your previous posts with what you were doing incorrectly at first that created the problems and reasons for those initial posts, by placing files differently, etc, than how it's outlined to be done; I wondered if any of those placements are still at odds, and/or if you are still doing everything correctly now. Everything in the tutorial was written the way it is for a reason.

Moving on from the past though, is to know that I (or anyone else that we know of) do not have this 'reply to' problem that you're having. With the file placings and other things you've done along the path it's hard to know which one (if any) could be causing your problem. You must have something out of place, OR, (if applicable) you are using a previous message store folder that has problems causing this - and unknowingly are carrying over the issue with it.

And so to isolate your issue (even if at first on a spare testing hd) ..one thing for sure is I do know that if you create a brand new fresh virgin Win10 install from scratch, and then setup a virgin WinMail reinstate as per tutorial (with no Backup/Restore procedures 'of any kind' done yet) ...and then 'manually' enter your account setup info - you will not have that reply problem in the new setup.

Going forward then in hindsight you 'might' then be able to determine what it was and 'possibly' what you could do to fix the issue without having to fresh install bypassing what the problem really is.

 

[TigerHN]

Dear Endeavor,

Thank you very much. It's working perfectly.

 

[Anixx]

Is there a way to make the interface Russian?

 

[Anixx]

Is there a way of changing encoding on NNTP (in OE everything is OK):

 

[dadreamer]

Is there a way to make the interface Russian?

I suppose it's all related to mui files: msoeres.dll.mui and WinMail.exe.mui from Russian version of WM should be placed to C:\Program Files\Windows Mail\ru-RU folder. If you look at ogri's archives you will find those files.

edit: additional info in my next post

 

[Anixx]

I suppose it's all related to mui files: msoeres.dll.mui and WinMail.exe.mui from Russian version of WM should be placed to C:\Program Files\Windows Mail\ru-RU folder. If you look at ogri's archives you will find those files.

No. The mui files have no effect. I fixed the lang problem only after copying the whole folder from Russian Vista.

 

[dadreamer]

No. The mui files have no effect. I fixed the lang problem only after copying the whole folder from Russian Vista.

Well, then it appears that mui and dll should go next to each other. According to Dmitriy there are 5 pairs that are responsible for localisation:
MSOERES.dll+msoeres.dll.mui (main interface)
WinMail.exe+WinMail.exe.mui ("missing libraries" dialogues on WM start, e.g. msidcrl30.dll)
ACCTRES.dll+acctres.dll.mui (accounts)
INETRES.dll+inetres.dll.mui (bottom panel on the mail preview + some context menus)
msoert2.dll+msoert2.dll.mui ("Get help from communities" links)

 

[jcc2]

Congratulations Endeavor !!!!! Thanks to your persistence we can enjoy once again Windows Mail. It took me about 10 minutes to set it up following your instructions and I am more than happy as I had almost decided to use Windows Live Mail instead. Until a couple of days ago I had Windows Mail running happily o a Windows 7 PC but I needed to upgrade my PC to windows 10 1083 and was almost in tears for not being able to install Windows Mail in the new PC. Now the sun is shining again!!!!

Many thanks once again for your hard work!!!!

JCC2

 

[cushlomockree]

Hi Endeavor,
Thanks for the .reg code!
I've been manually moving Vista Winmail files from each successive edition of both Windows and Windows Server (just installed Server 2016) over many years. It had been a while since I had done this, so I stumbled on your instructions trying to refresh my memory.
BTW: I never delete the Windows Mail folder; just take ownership and rename it.
I am experiencing the blank Tools/Options/Advanced tab issue (though the Maintenance... button and dialog still work) which there seems to be a fix for, but I can't figure out which of your files is used to resolve the issue.
Would be grateful for any guidance.
Thanks,
Mike

 

[endeavor]

Hello cushlomockree (Mike) and welcome to the Eight Forums

There is a reason why I have people delete the programs folder and not rename it each time (besides why save it since it contains all the wrong files anyway, including after major updates) ..and to instead each time use the specific Windows Mail Programs folder version files I offer in attachments which btw comes in the proper named Windows Mail folder anyway, and so it's just a matter of deleting the original and after the extract of "x64-wm_programsfolder-zip" for Server and just copy/paste the new Windows Mail folder in place, and since Server is x64 only and so of course using the other x64 attachments: "x64-msidcrl30-dll-zip" ...including! the x64 version msoe.dll that's contained in the Update_5-2018.zip, and of course importantly not to forget WinMailEdit.reg.zip and merge it ..all of which are attached on post #1

You just skimmed through the procedures/spoilers too fast is all, but if you methodically do as what's written only in the Post #1 Tutorial which is what applies to Sever - it will work guaranteed! ..and your Maintenance tab Advanced Options will not be blank but populated.

If I need to make a special note for something specific just for the Server edition that I don't have listed now - then I can if needed.

 

[cushlomockree]

Hi Endeavor,
The newer(than Vista 64-bit?) version of msoe.dll fixed the blank Advanced Options tab.
THANKS!
I'm curious about how it was modified.
I did have somewhat of an issue this PM, but I think it might be a permissions issue with the new installation of Server 2016.
Since I have 3 different OS's (Win 8.1, Servers 2012 R2, and 2016) on different SSDs, I don't have the Store Folder in the default location ...USERS\Username\etc....
It is in a separate folder on one of the drives so that I can keep the respective winmail.exe's synced regardless of which OS I'm in.
When I rebooted (after having been in 2012 R2) into 2016 and opened winmail.exe it went nuts because it could not access the Store Folder on a different drive, and kept opening new instances of itself. I finally killed all of them in Task Manager. Tried again and everything was working again.
Nothing like this ever happened in 8.1 or 2012 R2, and I haven't put winmail on any of my Win 10 VMs.
Thanks again for all your work,
Mike

 

[endeavor]

You're welcome
I figured it was the update zip you needed but I wanted you to read and understand everything else first for going forward is all. It's not that it's a newer dll as you referred, its basically the same one but required an edit in order to re-connect the interface linking which affected that advanced tab window to display its contents.

I see you boot Win 8.1, Servers 2012 R2, and 2016 ...and for me I triple boot (live not VM) Win7/Win8.1/Win10 with SSD's in both x86/x64 bit OS combinations, and also have another SSD with Win98SE/Vista/WXP, etc, even with W2K, and then another with Server editions ..I prefer to do live installs and boot from them Live instead of VM's ...for a number of reasons.

Anyway as to your store folder problems, I keep the Stock message store folder location on each of them and dedicated only to themselves (not shared) for good reasons. ..which could eliminate the problems you (an others) have had with it for the same reasons. These days with so many OS's (Vista/Win7/ Win8/Win10) being able to work with WM, we can get fancy with what we do connecting various OS's WinMail to the same stationary relocated store folder (don't do it) ..realize better to keep it simple with the stock Store Folder location on each:
%USERPROFILE%\AppData\Local\Microsoft\Windows Mail
Be careful, it's also directed in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows Mail\Store Root
..and so you can't have one OS's directing it one place and another to another place!
Besides that, each OS install reference for WM will have a different account number so one will not mesh with the other, and so when reinstating Store Folders to newer installations (just like I explained to you about deleting the programs folder, and same thing explained in the Backup/Restore write-up) ..require the 'Delete' of the folder and replace it with the current updated one for consistent pickup. For instance when I install a new OS version (any) and I want to carry my current WM latest message store over to it and use that as my main one from now on, I will delete the newly created store folder (yes the whole folder!) ..and in its place copy the latest from where I came from - but I only keep one OS and its WM message (default located) store folder fully updated on a continuing basis and normally only use that one particular OS for continuous email/news polling - then you'll help prevent a problem where it can't rectify properly thus keeps recreating useless new versions of itself and corrupting your message store, especially after an update or re-instate. keep it simple to succeed. Always always always keep a current backup of your store folder to be used in a time like this - I can't stress that enough for safety.
I hope I've explained my meaning correctly with this since the proper wording requires much thought, but when you get the reasoning and understand you will see my point and the sense of it.

Everyone don't forget to use the Like button for posts or tutorials that help you, it's just another way to show appreciation for the work done.

 

[cushlomockree]

You're welcome
I figured it was the update zip you needed but I wanted you to read and understand everything else first for going forward is all. It's not that it's a newer dll as you referred, its basically the same one but required an edit in order to re-connect the interface linking which affected that advanced tab window to display its contents.

I see you boot Win 8.1, Servers 2012 R2, and 2016 ...and for me I triple boot (live not VM) Win7/Win8.1/Win10 with SSD's in both x86/x64 bit OS combinations, and also have another SSD with Win98SE/Vista/WXP, etc, even with W2K, and then another with Server editions ..I prefer to do live installs and boot from them Live instead of VM's ...for a number of reasons.

Anyway as to your store folder problems, I keep the Stock message store folder location on each of them and dedicated only to themselves (not shared) for good reasons. ..which could eliminate the problems you (an others) have had with it for the same reasons. These days with so many OS's (Vista/Win7/ Win8/Win10) being able to work with WM, we can get fancy with what we do connecting various OS's WinMail to the same stationary relocated store folder (don't do it) ..realize better to keep it simple with the stock Store Folder location on each:
%USERPROFILE%\AppData\Local\Microsoft\Windows
Be careful, it's also directed in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows Mail\Store Root
..and so you can't have one OS's directing it one place and another to another place!
Besides that, each OS install reference for WM will have a different account number so one will not mesh with the other, and so when reinstating Store Folders to newer installations (just like I explained to you about deleting the programs folder, and same thing explained in the Backup/Restore write-up) ..require the 'Delete' of the folder and replace it with the current updated one for consistent pickup. For instance when I install a new OS version (any) and I want to carry my current WM latest message store over to it and use that as my main one from now on, I will delete the newly created store folder (yes the whole folder!) ..and in its place copy the latest from where I came from - but I only keep one OS and its WM message (default located) store folder fully updated on a continuing basis and normally only use that one particular OS for continuous email/news polling - then you'll help prevent a problem where it can't rectify properly thus keeps recreating useless new versions of itself and corrupting your message store, especially after an update or re-instate. keep it simple to succeed. Always always always keep a current backup of your store folder to be used in a time like this - I can't stress that enough for safety.
I hope I've explained my meaning correctly with this since the proper wording requires much thought, but when you get the reasoning and understand you will see my point and the sense of it.

Everyone don't forget to use the Like button for posts or tutorials that help you, it's just another way to show appreciation for the work done.

I'm a little confused.
Although I triple boot 8.1, 2012R2, and 2016; when each OS is booted, each sees it's %SystemRoot% as C:\windows (8.1), D:\Windows (2012 R2) and E:\Windows (2016) respectively. Basically, the C:, D:, and E: drives are always the same regardless of which OS is booted.
So the ambiguity, which I know often arises because the booted OS tends to see itself as C:, does not exist on my system.
Also, registry value on my 2016 system for HKEY_CURRENT_USER\Software\Microsoft\Windows Mail\Store Root=%SystemRoot%Mail.
There is no

 

[endeavor]

There is no need of quoting a whole post unless you had a specific reason?
..but there was a lot of ground covered and was meant for advanced users which I had assumed you are, and so I apologize if I got ahead of myself giving you full throttle which I thought you would properly interpret.

I'm a little old school when it comes to booting OS's I guess, in that having MBR and three primaries, and booting to one of the three OS's lends to always having C:\ as my system root, but that's my system and I don't want to get into that here though, and I realize there are other methods and ways but that is not the purpose of this tutorial to get into - this tutorial and thread is only about getting Windows Mail reinstated.

Your left your post cut off? ...you left it @

There is no

?

However sticking specifically to Windows Mail and where the store folder is located, which in the majority of cases for so many reasons should always be left default, and that is within
%USERPROFILE%\AppData\Local\Microsoft\Windows Mail
Yes you can manually change that location in WinMail Advanced Options but in the majority of cases especially those who boot more than one OS, and in response to what you have said, which was:

I don't have the Store Folder in the default location ...
It is in a separate folder on one of the drives so that I can keep the respective winmail.exe's synced regardless of which OS I'm in.

...and so referring back to all the things said and the intent of my previous posts references, is that your store folder corruption most-likely is happening because of how you have changed your default options.

When I rebooted (after having been in 2012 R2) into 2016 and opened winmail.exe it went nuts because it could not access the Store Folder on a different drive

I am not surprised of that at all !!! ...and normally you cannot as you said ''Sync'' your Store Folder for all your three OS's accessing WinMail, for the reasons I've already implied and stated here and in my previous post and gave you the reasons why!; even though you said previously you booted your previous setup that way, but it was under the guise of what you understood you were doing, and with what actually happened.

I really don't know what your question is now?
Also to mention I'm not sure if you truly understand the Backup/Restore procedures given in the first post and how to use them!

If you had a current backup of your message store folder, which you should - do you? ..then the resolve would be simple, you would simply delete your corrupted folder, and copy the last dated good one in its place, and upon opening your WinMail GUI and message store would be showing you everything in place exactly as it was the day your created the backup. Did you make one? ..However with the way you have it then even upon successful restore, I cannot vouch for what happens when You then boot to your other OS's unless as I've mentioned that all OS's have default message store locations, all isolated from each other - not as you say sync'd.
You can only have one message store leader at a time, and the closest to sync you can get is a copy of that manually put to any other OS at that moment, which must be manually placed as outlined in the Backup/Restore write-up.