Windows Mail

endeavor · 27 Jun 2012

Ex_Brit said:

Sorry, I understood perhaps wrongly from what has just been said here that the xsmile reg fixes from my old default mail client thread (note: I used 2 not 1) were supposed to be part of the single fix in post #1. Sorry now I'm lost..

Yes Peter, Both! of those attachments registry information was/is already included into the WinMailEdit.reg in Post 1, and that was done back in 2009.
What I'm also saying as already noted is that the WinMailEdit.reg in post 1 is now incomplete since it is missing New pertinent registry information that's included in post #1230, but is Not in post 1

I don't see the point of a tutorial if one has to read thousands of posts...why hasn't #1230 been incorporated into post #1? Or perhaps a large font proviso included in post #1 to read also post #1230?

I totally agree! ..it should be put into Post #1. (Edit - it now is on page 1)

I have not asked Mark to do it, has anyone else?
Many of us, many times, have asked/hinted to Brink if he would do so, but he has not answered that question directly iirc I don't think, but indirectly he has said to others posting in this thread that they should move on from WinMail, of which I can only assume is for all the good reasons that Slartybart so eloquently outlined so well at the beginning of his Tutorial on Post #1.
I see it as a good disclaimer too, but for those who get it, and who are 'capable' then can Easily have WinMail (the updated Outlook Express) on Windows 7 if they want to, and I personally will have it on 7 for many years to come!

Maybe I'm misunderstanding you as I'm reading things at extreme speed. If so I apologize.

I hope I've cleared up any wonderings.

For Post 1 we do need ''Someone'' if Mark has moved on from the subject, and if he gives permission, who will edit Post 1 and possibly combine the Manual way that's there already (updating it's old reg file of course with the new one) ..and also give users another choice of a faster more accurate way of doing it by putting in Slartybarts combined automation process; or if not, at least put a link pointing to it.

Any ideas for who?
It's complicated, many of the original contributors have moved from WinMail?
Ideally though and realistically I would think? ..it would best be someone who has WinMail installed already. No I'm not volunteering myself, but I will contribute and work behind the scenes in the ways of my expertise as I've been doing right along.

Ex_Brit · 27 Jun 2012

Thanks for clarifying it. That takes us back to to whether or not someone wants to take ownership of the thread if Mark has left or is otherwise busy and that would be either the forum owner, Shawn or any of the Moderators I would imagine.

Sorry but I can't for reasons previously given.

Ex_Brit · 27 Jun 2012

I just PM'd a couple of people and copied you in on it.

Ex_Brit · 28 Jun 2012

Shawn Brink has done it I believe. Check it out please.

endeavor · 28 Jun 2012

Thank you Peter for your help in getting the Page 1 Tutorial updated to be Current, and thank you Shawn for making it happen!

Thanks to Slartybart for taking over the ownership and maintenance of the tutorial.

Thanks to Each and Every person over the years who has contributed to this project.

Long Live WinMail

...even with its current understood limitations, including being unsupported.

Ex_Brit · 28 Jun 2012

I was merely the messenger - but thank you ;-)

grits · 08 Jul 2012

vmcinab said:

Thanks everybody -- with the help of you fine folks and a lot of internet research, I finally got everything working perfectly last night (or this morning) around 2:30 a.m. -- even the SendTo problem. Sooooo nice to have WinMail back again -- I am very happy!!

Hi vmcinab, could you please tell me how you solved the 'Send To' problem? I've been using WM now for a couple months & love it except for that glitch.

Thank you,
grits

primal · 09 Jul 2012

Gobbledegeek said:

Try this if you have used the method described at the front of this thread to enable Windows Mail in Win 7 and now can't install SP1:

1. Go to C:\Program Files\Windows Mail\ and move the file msoe.dll to another location. If it won't move you will need to 'take control' of the file as described in the first page of this thread. (This is the file you downloaded to make the modification).

2. Open Control Panel - System and Security - Windows Update - View update history. Look for KB978542 and uninstall it. This update addresses a security threat to Windows Mail and makes numerous changes to the registry.!

Thanks for posting this.Had trouble with installing SP1 on 7 gave up trying again and found this. But i do not have the update KB978542. However something stopped win mail working and i just got thunderbird. I deleted the msoe.dll If win mail is that special to MS they can keep it. Running scannow and will try SP1 again

EDIT: Scannow found/fixed corrupt files but sp1 is still giving error 80004005
Edit: Chkdsk found no problems

DukeS · 11 Jul 2012

Happy Dance!

For those that follow, what worked for me was mostly the "Gobbledegeek solution" at post 958. Note that my CBS.log file specifically points to msoe.dll as the trigger of the error. Others suggestions (and frustrations) in this thread are associated with several other triggers of the 80004005 other than msoe.dll.

My variation of His solution follows:

1) If it was renamed per other suggestions, restore the Windows\SoftwareDistribution folder so you have access to the installed update history (disable the Windows Update Service to make the change, then re-enable it.)

2) Go to Windows Update, Installed Updates and remove the update KB978542. I suspect this Vista-related update is triggered to be applied to Win 7 by the Vista version of msoe.dll, which is why I think the Win 7 SP1 gets confused by file versions it doesn't expect to find.

3) Delete the Windows Mail folders in c:\Program Files and c:\Program File (x86)

4) Run sfc /scannow in an elevated command prompt to rebuild the folders, files and matching registry entries to the pre-KB978542 state. This restores the correct version of both the files and the registry entries relating to msoe.dll that SP1 is trying to uninstall.

5) Per the suggestion in comment 968 and others in that thread, I used the RTM ISO version of the SP1 update (link in that comment.) Apparently it is coded a bit differently than both the Windows Update and downloadable .exe versions. This was not tested and isolated as essential, it was one suggestion I used within my final recipe for success.

Hope this helps others. Just look in the CBS.log to be sure the 80004005 error is first triggered by the msoe.dll file (scroll up a ways from the bottom) to know whether this recipe applies to you.

Sammy888 · 19 Jul 2012

Is the search feature in WM dependent on indexing being enabled? Recently, I can no longer search within the main tree folder of Local Folders. I can search within the folders individually below this bu that's about it.