Windows Mail

Greg S said:

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?

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.

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 please..parismj@tesco.net

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 said:

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 said:

poppa bear said:

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.

Code:

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

Code:

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

Code:

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

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

poppa bear said:

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