Windows Mail

How to Reinstate Windows Mail in Windows 7​

   Warning

Microsoft no longer supports Windows Mail, aka WinMail. It's recommended you use another well known supported email client. This Tutorial is for Advanced users who importantly have the Technical Ability to make the changes, have backups of everything including your OS, and to be your own tech support for WinMail going forward. If you decide to complete this tutorial you accept the fact that you are using WinMail as-is. It might be necessary to uninstall other email clients to resolve any WinMail conflicts in some environments. Understand it's likely that new OS updates from Microsoft will break WinMail's operation, and to fix make it necessary to rerun the tutorial again to reinstate it. With those things in mind, this tutorial was written so that you can rerun it without affecting WinMail user data.
Please see this Errata (Bug List) post before you install, to be aware of the current information about known issues using WinMail within Windows 7, these issues are programmatic and in most cases cannot be resolved by this tutorial, and will never be fixed.

Having said all of that disclaimer, if you have the technical ability, and can put up with the annoying minor byproduct bugs, then like so many of us still enjoy using WinMail on Windows 7 ...ymmv!

   Tip

As of January, 2025, the instructions given here supersede all other instructions given in forthcoming older posts. Realize some of the posts that follow are over 16 years old, and many of the link pointers within have become mislinked over time, many of the files or information within them is outdated, incomplete, or superseded with more accurate information - and so be careful. However you can always be sure that the latest info from all research is incorporated into this tutorial post, and its downloads are the latest available. This post is continuously kept up-to-date, and so..
...Always refer to this Tutorial post for the very latest updated information

This is the 4th iteration of the Windows 7, WinMail tutorial.

The process of this tutorial Will Not work to reinstate WinMail on Windows 8/10 !
Windows 8/10 users please go Here

Start here

1. Download tutorial package TutReWinMail.zip
   
   Download
   
   
2. Extract the TutReWinMail.zip into your user Downloads folder
   • Note: Be sure once extracted this is the address of the ''TutReWinMail'' folder:
   • C:\Users\username\Downloads\TutReWinMail... ... (if it's not there please put it there)
3. Navigate to your user Downloads\TutReWinMail folder to be sure the above is correct.
   • (..if you need more verbose install instructions to follow, download this WinMail Local Tutorial.zip)
   • Advanced Users can proceed below:

     ---

     (..log in for Full Access, being able to get support, remove ads, like, and even to post, etc..)

Advanced Users: ..use this easy excellent overview of the steps in the local tutorial:

• Open an Administrator Command Prompt. (screenshot showing in Administrator mode)
• copy/paste this line into the command prompt: cd %USERPROFILE%\Downloads\TutReWinMail\
• Your command prompt must now be showing you are at That Same Folder Address ..which contains the tutorial files that the batch file in the next step executes programs and copies files specifically from that folder address - if it's not there the batch file will fail since it cannot find what it needs!
• Next type in either winmail32 or win64mail <matching OS bit, to interactively process These Next Steps
• If you've finished to the bottom as shown in last screenshot, restart your machine (sets registry)
• Create a shortcut from WinMail.exe to your Desktop
• Open WinMail - it may prompt you one (or both) of These Two Notices ..click yes, and okay.
• They now should be already set, but you can manually check/set at any time These Default Settings
• That's pretty much all there is to it, and from here you setup the rest of the Windows Mail client (aka: WinMail) as normal within its various tab menus for Accounts, Options, Layout, etc, etc, to suit your individual needs.
• Lastly, but should be the First thing you do, is to Create A WinMail Backup (new version) ..Go to this next link and when you get there scroll down to the heading: Backup/Restore Procedures for further instructions.

   Information

See How to open an elevated Administrator Command Prompt
Important: The exact text provided by the tutorial must be entered into the Administrator Command Prompt.
Hint: to avoid typos, copy/paste the entire line containing the command into the Command Prompt window.
Also see: How to Enable Copy to Clipboard from the Windows 7 Command Prompt

---

Every effort has been made to make this a step-by-step process, however, it is beyond the scope of a single tutorial to provide information on every command or concept. Search the Main Tutorial Section if you need greater detail on a concept or command presented in this tutorial.

Good luck, and long live WinMail

   Note

Made possible by members:
Mark (aka Mr GRiM) - provided the original tutorial
Poppa Bear - continued Mark's work within the 2nd version
endeavor - provided continuous feedback, changes, invaluable testing instrumental to tutorial operations
EKManitis - propose the batch code that made operations easier
Slartybart - updated, tested, and consolidated all of the above into the 3rd version
endeavor - reviewed, updated, tested, and incorporated all of the above into this 4th version
...and also a special thanks to All the other members who presented discovery for this project

Related Tutorials

---

• How to Backup/Restore Messages in Windows Mail (Vista version)
  
• Windows Calendar - Import into Windows 7
• Vista Windows Sidebar - Reinstate on Windows 7
• Windows Live Mail - Import Windows Mail Messages
• Windows Live Mail - Import Windows 7 and Vista Contacts

 

[Greg S]

To GregS re:

Eaz-Fix does work with Multi boot, same drive different partitions. That's the way I use it. I Multi boot XP and Win 7. When installing, check the custom installation, select Multi boot, install it, restart OS booting into your other OS, install with custom setup only this time check the box that says this is multiboot but I have already installed in the other OS.

Yep, you were dead right Greg. I thought you only had to instal it in one operating system and it would auto pick up the others.

Did exactly as you said and it worked a treat. Decided to go with Comodo. It seems to do everything that Eaz Fix does, except create a back-up image of the whole partition if you need to format your hard drive for any reason. But I've already got Acronis to do that.

I think it will be brilliant when doing a fresh installation. Just periodically create snapshots during installation, and if anything honks up your sytem, just go back to the previous snapshot stage. Then at the end delete all the snapshots used along the way.

I once spent hours re-loading WinXP for a friend, and had it about 90% finished, when I installed Adobe Reader and for some reason it conflicted and wrecked the whole installation. I had previously turned off Windows Restore because I wanted to save hard drive space. Eaz Fix or Comodo would have been brilliant, and it doesn't take up anything like the space used by Windows Restore which really bloats your system.

Thanks again Greg, I'm really grateful. Great program. Cheers PB

I'm fixin to download CTM now and give it a try. I've been in constant contact with Eaz-Fix support over their Drive Image not working for me after the latest update just a few days ago. Prior to that, it's worked flawless. I even decided to try the Win 7 System Image without initial success. I uninstalled Eaz-Fix and System Image began working. I was amazed at how quick it backed up both partitions compared to Drive Image. I attached System Image .vhd file/files and all was there so I hope it will work in the future in case it's needed. If not, I will still have my prior EZ Drive Images backups, albeit a bit outdated

 

[poppa bear]

To GregS re:

I'm fixin to download CTM now and give it a try. I've been in constant contact with Eaz-Fix support over their Drive Image not working for me after the latest update just a few days ago. Prior to that, it's worked flawless. I even decided to try the Win 7 System Image without initial success. I uninstalled Eaz-Fix and System Image began working. I was amazed at how quick it backed up both partitions compared to Drive Image. I attached System Image .vhd file/files and all was there so I hope it will work in the future in case it's needed. If not, I will still have my prior EZ Drive Images backups, albeit a bit outdated

Very interesting. I've got Eaz-Fix still on my main PC; & a 2nd PC with CMT on it. The main one has XP Pro, Vista and Win7. The other has XP Home & Win7. Whether it's because I've got 3 OSs on the main PC, or Eaz-Fix instead of CTM, it now takes a lot longer to boot up an OS than the 2nd PC, despite the main one having the advantage of dual core versus hyper threading, more RAM and a much faster video card.

I didn't know Win 7 had a System Image program. Is that the image referred to in the repair utility after you boot from the Win 7 DVD and it offers the option of restoring to a saved image? I must have a look at that. I started doing system images back in the days of Norton Ghost. But then SATA came along and Norton Ghost would no longer work. So I graduated to NTI Drive Image, but when Vista came out, NTI did not support it, so I went to Acronis.

And Acronis has been flawless in operation, although restricted in some areas. If you save a system image to more than one linked DVD, and want to use the partition resize when reloading the image, it's not feasible, because you have to exchange the discs in the optical drive multiple times so it can work out the new partition information. After 25 swaps of the discs, and it still not finalised, I gave up. It warns you of this restriction. Works fine if your image fits on a single DVD, or is saved to a storage partiton on the hard drive.

What I do now is save an activated bare bones installation to a DVD, with all the motherboard drivers, for a fresh re-build from scratch. And one fully loaded image also to DVD, as a baseline. Then I save an image to a primary storage partition on the HD. This last operational image is periodically auto-updated, and can be reloaded straight over the top of an existing OS which has become corrupted or infected, although I prefer to unconditionally format the partiton first, especially if there's been a virus.

Re:

I was amazed at how quick it backed up both partitions compared to Drive Image.

Is the Drive Image referred to here the back-up image application in Eaz-Fix that saves to an external storage? Acronis takes about 15 -20 mintues to burn a back up image of say Vista OS partition, where there's about 15GB of info. And about 12 minutes to reload it straight over the top of the existing system.

Cheers PB

 

[poppa bear]

To GregS re:

Quote: Originally Posted by Greg S
I've used this tutorial for adding WinMail to Win 7 and all is working well. Thanks. I've also used this tutorial How to add Windows Calendar to Windows 7 to add WinCalendar which works as well. In WinMail I have a toolbarbutton to access WinCalendar although it doesn't bring up WinCalendar. Anyone have an idea what to tinker with in order to make it work?

Nevermind, I fixed it. I found all applicable wincal reg entries in Vista and merged them in Win 7. All is well

Hey Greg, I got caught up in the Win Calendar thing, and successfullly imported it as per the tutorial you referred to in an earlier post. But like yourself earlier on, I can't make the tool bar button in Windows Mail open it. Would you have any registry edits to make Windows Calendar work off the tool bar in Windows Mail?

Cheers PB

 

[Ex_Brit]

To ExBrit re:

Click on the start button and type in regedit and hit Enter.
Navigate through HKEY_CURRENT_USER, Software, Microsoft and Windows Mail.
Create a new DWORD called NoSplash.
Set the value of NoSplash to 1.
Exit Registry Editor.

Hey ExBrit, that's brilliant. Worked a treat. Have never done a new DWORD before and didn't know what that meant or how to do it.

Anyway, tried right clicking Windows Mail and found the option, and once it was created and named, right clicked new DWORD, then clicked Modify to reset the value to 1.

I've also used it in Windows Mail in Vista, which always took yonks to open. Now opens in about a quarter of the time.

Keep up the good work. Cheers PB

Yes, those splash screens delay things quite a bit, that's why I disable them in anything I can.

 

[Greg S]

To GregS re:

Quote: Originally Posted by Greg S
I've used this tutorial for adding WinMail to Win 7 and all is working well. Thanks. I've also used this tutorial How to add Windows Calendar to Windows 7 to add WinCalendar which works as well. In WinMail I have a toolbarbutton to access WinCalendar although it doesn't bring up WinCalendar. Anyone have an idea what to tinker with in order to make it work?

Nevermind, I fixed it. I found all applicable wincal reg entries in Vista and merged them in Win 7. All is well

Hey Greg, I got caught up in the Win Calendar thing, and successfullly imported it as per the tutorial you referred to in an earlier post. But like yourself earlier on, I can't make the tool bar button in Windows Mail open it. Would you have any registry edits to make Windows Calendar work off the tool bar in Windows Mail?

Cheers PB

Why heck yea,lol. What I did was a Vista to Win 7 registry compare. When I came across one in Vista, I saved it to the Vista desktop, copied all onto a usb flash which was used to import into Win 7. Having said that, it's about 10 of them and all are very small in size. I'll zip them up and upload for ya.
View attachment WinCalReg.zip

 

[poppa bear]

To ExBrit re:

Yes, those splash screens delay things quite a bit, that's why I disable them in anything I can.

That's exactly how I think. Funnily enough though, for some unknown reason, I never thought of the WinMail initial screen as being a splash screen until I read this post.

I guess it's understandable that freeware providers put in nag screens, but they drive me crazy. It's almost an obsesion with me to get rid of them. I did a post in Techspot telling how to disable the free Avira nag and splash screen. And had a lively debate with some members who felt the freeware providers were doing us a favor and we should be beholding to them.

However, as I pointed out, they have to do that to stay in the market place. What's more they also get their product tested and advertised. I think of freeware as being more like Adware; and akin to Microsoft putting out beta versions of their operating systems. And last but not least, the costs of the freeware are factored into the production costs of the final product, as they are simply one stage in the manufacturing process leading to the final product. So it doesn't cost them anymore to put it out there. And they get repaid by the profits from consumers who buy retail. So there's still no free lunch.

Better stop, I'm getting on my hobby horse now.

Cheers PB

 

[andjayik]

how do we get rid of the the windows mail splash screen?

1. Click on the start button and type in regedit and hit Enter.
2. Navigate through HKEY_CURRENT_USER, Software, Microsoft and Windows Mail.
3. Create a new DWORD called NoSplash.
4. Set the value of NoSplash to 1.
5. Exit Registry Editor.

Thanks alot worked like a charm!!

 

[Ex_Brit]

You're welcome.

 

[poppa bear]

Win Cal registry edit

To GregS re:

Why heck yea,lol. What I did was a Vista to Win 7 registry compare. When I came across one in Vista, I saved it to the Vista desktop, copied all onto a usb flash which was used to import into Win 7. Having said that, it's about 10 of them and all are very small in size. I'll zip them up and upload for ya.
WinCalReg.zip

Wow! Wow! Wow! Thanks heaps Greg. You are a gentleman and a freakin genius! I applaud! It worked without a single hiccup.

Man I'm impressed. How the heck did you work out how to do all of that? Yo all! I've never saved a regisry key in my entire PC experience. At a guess do you right click and save? And once saved do you then have to convert it to an auto .exe file type?

Hell I could get hooked on doing this kind of stuff! Cheers Bernie :roflmao:

 

[Greg S]

To GregS re:

Why heck yea,lol. What I did was a Vista to Win 7 registry compare. When I came across one in Vista, I saved it to the Vista desktop, copied all onto a usb flash which was used to import into Win 7. Having said that, it's about 10 of them and all are very small in size. I'll zip them up and upload for ya.
WinCalReg.zip

Wow! Wow! Wow! Thanks heaps Greg. You are a gentleman and a freakin genius! I applaud! It worked without a single hiccup.

Man I'm impressed. How the heck did you work out how to do all of that? Yo all! I've never saved a regisry key in my entire PC experience. At a guess do you right click and save? And once saved do you then have to convert it to an auto .exe file type?

Hell I could get hooked on doing this kind of stuff! Cheers Bernie :roflmao:

Hi PB, you just save it as is. The .reg file can either be single clicked and merged into registry or right click context menu, select merge and it will merge it into the registry. As to saving locations of the registry for save keeping, always wise to do if you're a tinkerer, right click the key that is in the left hand pane and select Export. Give a descriptive name you'll understand and that's it. If you tinker with more than one key, instead of flip flopping back and forth by scrolling in the registry, save the key to in the Favorites located in the menubar above. <--- That one is a big help

Offtopic: I'm giving CTM a go. I hope it works out. I also hope EF support doesn't monitor this,lol. They've always been a big help with support. Only thing offhand I don't like about CTM, is it's fetish for the color RED.

 

[Greg S]

Ok, I'm not working this week and have nothing better to do,lol. I've just now put back the original Win 7 Windows Mail Folder. I went into Folder Options to show the Win 7 hidden WinMail.exe. I brought up the cmd console, typed in attrib -s -h WinMail.exe and hit enter to remove the attributes. The only file I needed from Vista to make Win Mail work was msoe.dll

Anyone know where sfc /scannow gets it's original files for replacement? I have a hunch that it's from E:\Windows\winsxs. I quoted my post above because of the fact that I am able to get Windows Mail working with just the one file as quoted above. I know the folder that I just mentioned is a bit taboo for users to muck around in and really you can't from within windows anyways, but when I get more confident with CTM, I'm going to do a little experimenting. I think if one can replace a file(msoe.dll) from within the above folder, I have a feeling that it would cure the Win Updates or sfc problem. I searched the above folder and found the one reference of msoe.dll in it, which of course is the Win 7 version. Placing the Vista version of it in there might just work. I know that it can't be done from within Win 7, but I think I can replace it when booted into XP. I have compared the files and they are the same. The only diff I see is they have different hashes. Could the hash be what Win 7 sees to determine that the file needs replacing?

 

[martinu]

I can't make this work. Having saved the existing files and copied the ones from Vista over the top of them, I try running WinMail.exe and it either spawns loads of "WinMail.exe *32" processes, consuming vast amounts of memory (page file usage shoots through the roof!) or else I get just one WinMail and one WinMail *32 process, but no splash screen or window appear.

What am I doing wrong? Is it because I'm trying to run the 32-bit Vista version on 64-bit Windows 7? If so, is there any way of getting round this because I've only got a 32-bit version of Vista that I can copy the Windows Mail files from.

 

[myzr7]

I can't make this work. Having saved the existing files and copied the ones from Vista over the top of them, I try running WinMail.exe and it either spawns loads of "WinMail.exe *32" processes, consuming vast amounts of memory (page file usage shoots through the roof!) or else I get just one WinMail and one WinMail *32 process, but no splash screen or window appear.

What am I doing wrong? Is it because I'm trying to run the 32-bit Vista version on 64-bit Windows 7? If so, is there any way of getting round this because I've only got a 32-bit version of Vista that I can copy the Windows Mail files from.

Welcome to SevenForums, martinu
Win7 has two program files folders, You need to use the program files x86. This is covered a couple of pages back in this thread by poppa bear, Good luck to you with this problem and I hope that you enjoy your time here on SF.

 

[SparkyB]

Windows Mail x64 needed please

My main pc has had a complete rebuild and now has windows 7 ultimate x64 on it..I need windows mail x64 from somewhere so that I use windows mail again..I have vista basic 32 on a laptop but apparently from what i have read on here i need x32 and x64 folders to continue..help [email protected]

 

[poppa bear]

To GregS re:

I'm giving CTM a go. I hope it works out. I also hope EF support doesn't monitor this,lol. They've always been a big help with support. Only thing offhand I don't like about CTM, is it's fetish for the color RED.

Hey Greg, thanks for that info on registry key saving/restoring and merging. It's something I thought about doing for a long time, but was always reluctant in case I wrecked my OS. But it's a different story now I've got CTM. FYI as a test I deleted the boot files for Win7 using EasyBCD. Then checked it wouldn't boot. Reloaded a snapshot taken prior to deleting boot files, using CTM, and hey presto, all up and running again. I've now got CTM on both PCs and so far so good. Owe you one for putting me onto it.

Re:

Anyone know where sfc /scannow gets it's original files for replacement? I have a hunch that it's from E:\Windows\winsxs. I quoted my post above because of the fact that I am able to get Windows Mail working with just the one file as quoted above. I know the folder that I just mentioned is a bit taboo for users to muck around in and really you can't from within windows anyways, but when I get more confident with CTM, I'm going to do a little experimenting. I think if one can replace a file(msoe.dll) from within the above folder, I have a feeling that it would cure the Win Updates or sfc problem. I searched the above folder and found the one reference of msoe.dll in it, which of course is the Win 7 version. Placing the Vista version of it in there might just work. I know that it can't be done from within Win 7, but I think I can replace it when booted into XP. I have compared the files and they are the same. The only diff I see is they have different hashes. Could the hash be what Win 7 sees to determine that the file needs replacing?

Be interesting to see how you go with the msoe.dll file. Can't help with location of restoration files when running sfc /scannow. It's way out of my league. As I'm sure you'd know, it used to be from the installation CD when running it in XP. I'd be curious to know where it's at in Vista and Win7 if you find out. Good luck.

Cheers PB

 

[poppa bear]

To SparkyB re:

My main pc has had a complete rebuild and now has windows 7 ultimate x64 on it..I need windows mail x64 from somewhere so that I use windows mail again..I have vista basic 32 on a laptop but apparently from what i have read on here i need x32 and x64 folders to continue..help [email protected]

The Windows Mail folder from your 32 bit Vista installation should work, but they must be imported to the X86 Program Files, which is for 32 bit applications. You would still need to remove Windows Mail from the 64 bit program files. If you wish, save a back-up copy of these files to a storage location, before deleting. If you need it, click here to a guide to the whole process.

Good luck, PB.

 

[Greg S]

To GregS re:

I'm giving CTM a go. I hope it works out. I also hope EF support doesn't monitor this,lol. They've always been a big help with support. Only thing offhand I don't like about CTM, is it's fetish for the color RED.

Hey Greg, thanks for that info on registry key saving/restoring and merging. It's something I thought about doing for a long time, but was always reluctant in case I wrecked my OS. But it's a different story now I've got CTM. FYI as a test I deleted the boot files for Win7 using EasyBCD. Then checked it wouldn't boot. Reloaded a snapshot taken prior to deleting boot files, using CTM, and hey presto, all up and running again. I've now got CTM on both PCs and so far so good. Owe you one for putting me onto it.

Re:

Anyone know where sfc /scannow gets it's original files for replacement? I have a hunch that it's from E:\Windows\winsxs. I quoted my post above because of the fact that I am able to get Windows Mail working with just the one file as quoted above. I know the folder that I just mentioned is a bit taboo for users to muck around in and really you can't from within windows anyways, but when I get more confident with CTM, I'm going to do a little experimenting. I think if one can replace a file(msoe.dll) from within the above folder, I have a feeling that it would cure the Win Updates or sfc problem. I searched the above folder and found the one reference of msoe.dll in it, which of course is the Win 7 version. Placing the Vista version of it in there might just work. I know that it can't be done from within Win 7, but I think I can replace it when booted into XP. I have compared the files and they are the same. The only diff I see is they have different hashes. Could the hash be what Win 7 sees to determine that the file needs replacing?

Be interesting to see how you go with the msoe.dll file. Can't help with location of restoration files when running sfc /scannow. It's way out of my league. As I'm sure you'd know, it used to be from the installation CD when running it in XP. I'd be curious to know where it's at in Vista and Win7 if you find out. Good luck.

Cheers PB

I'm in XP as we speak. I can't help myself, I have to do this then boot back into Win 7 and run sfc and see what get's replaced. If it borks, CTM gets first shot at it. If it's a no go, it's Image restore time. Back in a few

 

[Greg S]

To GregS re:

I'm giving CTM a go. I hope it works out. I also hope EF support doesn't monitor this,lol. They've always been a big help with support. Only thing offhand I don't like about CTM, is it's fetish for the color RED.

Hey Greg, thanks for that info on registry key saving/restoring and merging. It's something I thought about doing for a long time, but was always reluctant in case I wrecked my OS. But it's a different story now I've got CTM. FYI as a test I deleted the boot files for Win7 using EasyBCD. Then checked it wouldn't boot. Reloaded a snapshot taken prior to deleting boot files, using CTM, and hey presto, all up and running again. I've now got CTM on both PCs and so far so good. Owe you one for putting me onto it.

Re:

Anyone know where sfc /scannow gets it's original files for replacement? I have a hunch that it's from E:\Windows\winsxs. I quoted my post above because of the fact that I am able to get Windows Mail working with just the one file as quoted above. I know the folder that I just mentioned is a bit taboo for users to muck around in and really you can't from within windows anyways, but when I get more confident with CTM, I'm going to do a little experimenting. I think if one can replace a file(msoe.dll) from within the above folder, I have a feeling that it would cure the Win Updates or sfc problem. I searched the above folder and found the one reference of msoe.dll in it, which of course is the Win 7 version. Placing the Vista version of it in there might just work. I know that it can't be done from within Win 7, but I think I can replace it when booted into XP. I have compared the files and they are the same. The only diff I see is they have different hashes. Could the hash be what Win 7 sees to determine that the file needs replacing?

Be interesting to see how you go with the msoe.dll file. Can't help with location of restoration files when running sfc /scannow. It's way out of my league. As I'm sure you'd know, it used to be from the installation CD when running it in XP. I'd be curious to know where it's at in Vista and Win7 if you find out. Good luck.

Cheers PB

I'm in XP as we speak. I can't help myself, I have to do this then boot back into Win 7 and run sfc and see what get's replaced. If it borks, CTM gets first shot at it. If it's a no go, it's Image restore time. Back in a few

Partitial success and it does read the hash value for determination, although it can't replace the file, I was still given this message from the cbs.log file. To me, not a big deal since it can't replace it and that's what I was lookin for.

Repair transaction
2010-01-17 13:51:59, Info                  CSI    000000d4 [SR] Cannot repair member file [l:16{8}]"msoe.dll" of Microsoft-Windows-Mail-Core-DLL, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-01-17 13:52:10, Info                  CSI    000000d7 [SR] Cannot repair member file [l:16{8}]"msoe.dll" of Microsoft-Windows-Mail-Core-DLL, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-01-17 13:52:10, Info                  CSI    000000d8 [SR] This component was referenced by [l:238{119}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~6.1.7600.16385.Microsoft-Windows-Client-Features-Update"
2010-01-17 13:52:11, Info                  CSI    000000db [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\E:\Program Files\Windows Mail"\[l:16{8}]"msoe.dll"; source file in store is also corrupted

I haven't tried it yet, but I think the registry value

x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de

could be edited with the Vista version which I have and the file wouldn't need replacing in the winsxs folder. Not for sure on that. Another possibility would be, deleting the registry value mentioned in the code above. This way it wouldn't have anything to compare to, but this registry value

Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385

is what it was referenced by and shouldn't be altered since there is more than just Mail being considered as a Client.

Hang on a minute, I'm already knee deep in this snapshot, might as well finish the experiment. I'm going to delete the x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de registry entry and run sfc /VERIFYONLY and see what happens,lol.......

OK, deleting this registry entry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de

fixes the sfc /scannow replacement of the one and only file(msoe.dll) that windows mail uses from Vista. Experiment Over

 

[poppa bear]

regedit

To GregS re:

Hang on a minute, I'm already knee deep in this snapshot, might as well finish the experiment. I'm going to delete the x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de registry entry and run sfc /VERIFYONLY and see what happens,lol.......

OK, deleting this registry entry

Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de
fixes the sfc /scannow replacement of the one and only file(msoe.dll) that windows mail uses from Vista. Experiment Over

Unfortunately you lost me in that experiment as I haven't got enough back ground to follow the logic of what's happening. Check me out, but if I'm reading you right, does this mean I can safely delete the registry key shown above to fix the sfc /scannow issue? Awwww what the hell, I've got CMT, so I'll back it up, then delete it, and see what happens!

Update: Hey Greg, I deleted it, ran sfc /scannow and it worked a treat! Man, you're incredible. Triple WOW! (no red since you don't like the CMT fetish for red). I couldn't have worked that out in a million years.

Probably should add that into my Techspot Guide? What do you think? Safe to do so, or would it confuse the masses?

Cheers PB

 

[Greg S]

To GregS re:

Hang on a minute, I'm already knee deep in this snapshot, might as well finish the experiment. I'm going to delete the x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de registry entry and run sfc /VERIFYONLY and see what happens,lol.......

OK, deleting this registry entry

Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de
fixes the sfc /scannow replacement of the one and only file(msoe.dll) that windows mail uses from Vista. Experiment Over

Unfortunately you lost me in that experiment as I haven't got enough back ground to follow the logic of what's happening. Check me out, but if I'm reading you right, does this mean I can safely delete the registry key shown above to fix the sfc /scannow issue? Awwww what the hell, I've got CMT, so I'll back it up, then delete it, and see what happens!

yes, I deleted it and ran sfc without any mention of the mismatch of the file msoe.dll or any other warnings pertaining to Windows Mail for that matter. But then again remember, I wouldn't have any warnings to other files because I am using all Win 7 files except msoe.dll.

If you also can confirm that it works, then the steps for making it work are down to just a few.
1)Unhide and lose the attributes of WinMail.exe
2)Copy and paste Vista version of msoe.dll
3)Delete the reg key
4)Merge your 2 winmail reg keys on your other site

I would assume step 4 would still be needed, not for sure on that