Windows 10: Windows Mail

...fwiw, the only thing different I noticed with re-instating ''WinMail'' after an update with this new Win10 build 15063 that has come out, is that specifically "when upgrading previous Win10 builds" that afterwards besides replacing the Windows Mail programs folder again, you Also have to copy the msidcrl30.dll to the System32 folder again too because the upgrade removed it and of course WinMail won't start; I even merged the WinMailEdit.reg again for good measure.

I've updated the tutorial in Post #10 in the Eight forums to note that.

 

Vista WinMail is no longer able to be reinstated on Windows 10 beyond version 1703 build 16193

Microsoft has removed the OE legacy code of WinMail, see within article here:

Features removed or deprecated in Windows 10

 

Hi friend, since I installed Windows 10 version 1709 16299.5 I see the following error "I could not start windows mail because no library was found" Can you help me???

 

Welcome to the TenForums roerisi,

It will not work with your newer version, and just as the post before yours says, it will only work for Windows 10 versions Before 1703 build 16193, and so if you want WinMail, you will have to go back to that earlier version.
I am sure most Windows 10 users will want to move on to another email client, and forget about WinMail
.......(..not me though *Smile ...... ..well, not for a long while yet anyway)

All information on how to reinstate WinMail into Win8 or earlier Win10 is located over in this thread Here please.


Let me repeat my previous post again:
____________________________________________________________________________________________________


Vista WinMail is no longer able to be reinstated on Windows 10 beyond version 1703 build 16193

Microsoft has removed the OE legacy code of WinMail, see within article here:

Features removed or deprecated in Windows 10

 

thanks for your kindness and courtesy in answering me, I had already read that from the future versions of win 10 would have been decreed the end of Windows Mail, I thought some of you knew the way to bypass the source code and run our well-loved Windows Mail, thanks anyway.

 

Hello roerisi,

Friendly greetings to you in Italy!

As I have spoke about in this post Here and and other posts around that one, I have tried to do it a number of times already to work it out, but it's just not practical anymore on any level to spend more time on it.
However we have many good years left though to still use WinMail on Win7, and/or Win8, and/or the earlier versions of Win10 ...preferably v1607 ..fully updated current with it's latest Cumulative Here just last week to 14393.1770

 

If I revert to Win 10 Build 1703 which lets WinMail work, how can I prevent, or can I prevent Build 1709 from installing?

 

Hello Billg226,
I remember you from the main WinMail thread in the Eight Forums, and I hope things are going good with you.

Maintaining Windows 10 with WinMail is much more tricker than doing it on Windows 8, especially now! ..and that needs to be known up front. Honestly I don't really recommend it! ...unless, a person has a current, easy come, commanding control over all aspects of their computer environment. If you do then only then it can be an easy or fun side project, that is expendable; otherwise I don't recommend it at all please. No support is offered.

To your question though, in order to stop Windows Updates from updating/installing things automatically, you have to turn it off in Services completely; some other information how to do that, iirc, is here.
After that, from then on, now you'll always (while they are still offered anyway) have to do a few updates manually. Again not recommended unless you have a commanding understanding about what that means, and how to update your computer manually with the Cumulative Updates I mentioned in my last post (your question mentioned version 1703 and that would be always given here) and always changing forward; along with any service stack updates, and of course flash if you use it.
To reflect that information I've just now updated the main tutorial with those 1607 Cumulative, Servicing Stack, and Flash update links Here.
As known with this, most updates you do of course always breaks WinMail and so you have to go through the process to re-instate it again. So you see this WinMail project on Win10 is not for everyone, for Win10 i don't recommend it really, and if a person has to ask how to do any of this then honestly this project is not for them; and of course no support is offered.

1703, I believe is where the Creators Update started, and is why I chose (on my main towers anyway) to stay back with 1607 and keep them maintained current there; otherwise yes I test 'newer' builds to keep up with the ''Windows 10'' evolution itself without the thought of using WinMail on it.
If you like and want to stay current on the Windows 10 train, then you'll have to forget about WinMail, and so join the Windows 10 movement onward.

all the best..

 

Endeavor,
Thanks for your reply & all your past help in my keeping WinMail going until this Build 1709 came out & broke it for good. My tower has Win 10 Pro Build 1703 on it which I've got Updates Delayed. However, my laptop has Win 10 Home (reverted back to Build 1703 with WinMail re-instated) and set as a metered connection but on next Restart 1709 will get installed again, sigh. Yes, I've had to re-instate WinMail many times since installing Win 10 however to me it's been worth the trouble & only wish I could continue doing that. . I'd had to re-instate WinMail so many times, I'd got to where I no longer needed to use the tuts. But looks like no way now after 1709.
Again, thanks for your past help........................Bill

 

Your Welcome Bill, and because of your post it prompted me to update the main WinMail tutorial to reflect the information I gave you. I've just now updated the tutorial with those 1607 Cumulative, Servicing Stack, and Flash update links, Here. (scroll down to where I edited in green print)

With 1607, in Services, having the Windows Update service set Disabled, etc, it does not auto update anything ever!

(I only give 1607 links, so for your 1703 current ones (which change) you'll have to click within them to find your way to 1703, where/if applicable.

I personally like to stay with 1607 for WinMail for a few reasons, ymmv, and also since I don't need anything the 1703 (beginnings of creator update) has to offer anyway, ymmv.

...have a great day!

 

Endeavor, since I've rolled back to 1703 from 1709, would it be possible on my Win 10 Pro & Home PCs to roll back to Build 1607 (understanding I'd have to re-instate WinMail & disabling Updates in Servicing) by clicking on the 1607 link in your tut or do it as I did for 1709 to 1703 from within Win 10? I to don't need anything in 1703.
Thanks again...............Bill

 

Well you know me being a big proponent of partition imaging. Creating a partition image before each version change or major update, and save the OS versions backups for years and so can go back to any point in time. I never use the rollbacks, don't like the baggage and file size of Windows.old folders, etc, and prefer to restore the partition image itself. Anyway sorry for digressing, but I take it you don't use imaging software, and so with what you did, I think, you can only go back one version; I've forgotten so would have to research a little but I'll let you do that instead. Also minor things maybe but your Home versions have some limitations over your Pro version, for the active user.

It may just be easier for you just to stay with 1703 if you can't, no problem, and I wouldn't blame you if you don't want to bother with the time/hassle with a fresh install ..but of course much better to do a fresh install but then again if you have yours built up with lots of things installed, then it's a p.i.t.a. to have to reinstall it all again I know.

Just stay with 1703 if you prefer then.

That's why partition imaging is so darn excellent, fast, accurate, and easy, with unlimited possibilities at your fingertips to go back in time as far as you want, in just minutes, to as far back as you had saved backups.