Windows Mail

bobkupferer · Mar 1, 2011

win mail tutorial

I regret that I am afraid that at my "skill level" i would mess this up!
what I want to do is download windows mail and set gmail as my default;
thank you so much, i am sorry that my skill level is -14 ha ha ;
respectfuly bobk

swblake · Mar 1, 2011

Aw rats

Sadly, after successfully overwriting files identified by SFC as "corrupt", and attempting the SP1 update again, it failed again, with the same Code 80004005. That was disappointing; my entire working theory was that the issue involved the Windows Mail Reinstate process. I'd used the process detailed at How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 and been successful. System was "clean". Afterward, I tried several variables I'd read about; deleting the SoftwareDistribution folder, disabling all non-Microsoft services and startup items, etc, etc. Everything has failed. I noticed the sfcdetails.txt file that's one can generate after running SFC mentioned "update not allowed due to regulation". A search on that led me to a procedure outlined by a Microsoft tech involving shutting down several Microsoft services, deleting the %systemroot%\system32\catroot2 folder, etc. Followed the procedure explicitly, no joy. My last gasp will be contacting Microsoft support, which should be free for WU issues. Of course, they'll insist on running me thru all the things I've already done <grin>. If that fails, then I'll probably blast and reload, sadly. Then, too, there's always Ubuntu Linux. In fact, that's what I'm using right now. Of course, it has it's own issues, as well.....

Greg S · Mar 1, 2011

swblake said:
Sadly, after successfully overwriting files identified by SFC as "corrupt", and attempting the SP1 update again, it failed again, with the same Code 80004005. That was disappointing; my entire working theory was that the issue involved the Windows Mail Reinstate process. I'd used the process detailed at How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 and been successful. System was "clean". Afterward, I tried several variables I'd read about; deleting the SoftwareDistribution folder, disabling all non-Microsoft services and startup items, etc, etc. Everything has failed. I noticed the sfcdetails.txt file that's one can generate after running SFC mentioned "update not allowed due to regulation". A search on that led me to a procedure outlined by a Microsoft tech involving shutting down several Microsoft services, deleting the %systemroot%\system32\catroot2 folder, etc. Followed the procedure explicitly, no joy. My last gasp will be contacting Microsoft support, which should be free for WU issues. Of course, they'll insist on running me thru all the things I've already done <grin>. If that fails, then I'll probably blast and reload, sadly. Then, too, there's always Ubuntu Linux. In fact, that's what I'm using right now. Of course, it has it's own issues, as well.....

You are in good company my friend. I've done everything as well. I felt certain that mine had nothing to do with Windows Mail. I did restore mine back to the prior state and all but no joy here either. I ran their readiness tool which was a wasted 100mb download. I've downloaded the SP1 install package which doesn't work either. The winupdate version 61.2mb will download to 31 percent. Hd activity going on for hours especially in softwaredistribution/downloads folder which is continually being written to. I think it's writing to the folder, deleting items, then re-adding them. My longest attempt at this was over five hours. I wouln't mind going longer but the TrustedInstaller process is hosing the CPU during this time. As of right now, I consider myself blessed that it will not install. I have no doubt that it's just more MS garbage bloat of help files, fonts and one of there famous tricks, keeping the same files and updating them with their Blessed new version number added to them.

Doctor Colossus · Mar 1, 2011

Praise be to Gobbledegeek, and those geeks whose shoulders he stands on. His solution worked for me, after several agonizing days of failed installs.

Neither "sfc /scannow" nor Windows6.1-KB947821-v10-x86.msu found any problems with my installation. I'm multi-booting, so I marked the Windows partition as active and uninstalled GRUB bootloader. But none of this helped. I finally noticed this silly Mail-related error in CBS.log.

I finally succeeded using Gobbledegeek's procedure with this download of SP1 -- I read in some other forum that some other poor soul finally succeeded only with it, after having tried a multitude of other things. I also found virtually mounting this ISO to be slightly faster than the other two methods I tried (Windows Update - ack...; and a large, self-extracting .exe I downloaded).

swblake · Mar 1, 2011

Next step...

Thanks for the feedback regarding our mutual headache with SP1. I've read and followed every reasonable solution, regardless of its complexity, as well as thrown in a few ideas of my own. Greg S, I can feel your pain all too well. And I agree with you, that download hang at 31% doesn't sound like something you'd want to subject your CPU to for hours on end, jacked up at 100%. I think you're the only person I've seen with that particular issue, meaning during the actual download. As for Doctor Colossus' suggestion, thanks... I didn't install Win7 originally until after August of 2010, apparently the changes in KB978542 were slipstreamed into the downloaded updates during install; I don't have that item listed. As for the RTM of SP1, would you believe I've had that here all along, downloaded it when it was released, but never ran it. Maybe I'll try that if the process I'm running now fails. I saw a posting of a "fix" that's a bit extreme, but still far short of a blast & reload. Basically, it's to do an "Upgrade" off the Win7 DVD. Upon completion, there's a whole slew of updates needing to be run, and then, lo and behold, you're *supposed* to be able to install SP1. Very time-consuming, but at this point, it would still be way less than I've already invested. It's running right now, on a Core 2 Quad Q6700 machine with 6GB memory, so hopefully will go fairly quickly. I also used the suggestion to use that tool to save my activation info and restore it afterwards, hopefully avoiding the activation BS. Will get back with results....

swblake · Mar 1, 2011

Success!

OK, I'm now having a glass of wine (live in CA). The process outlined by mick823 on this forum, and utilizing the utility to save activation info I saw posted earlier, I've successfully (finally!!!) upgraded to SP1. It's time-consuming, and not perfect, but it works, and works well. I have probably a hour's worth of "clean-up" after the fact. Total time spent, with a relatively fast system (Core 2 Quad Q6700, 6 GB mem) has been about 3 hours. Essentially, it's similar to XP's repair function that was available after choosing to do an install. If there was an in-place XP installation, an option to overwrite all the system files without deleting the program files was available. Afterward, any and all updates issued since the OS shipped needed to be re-installed. Everything appears to be working normally, but the graphics drivers will need to be updated, etc. After the fact, if the system appears to be running fine, the backup files of the old OS can be deleted (in my case, nearly 3GB) using the Disk Cleanup wizard, and choosing to remove System files. The utility for backing up the Windows Activation info also worked spectacularly. All in all, I'm big-time happy. Think another glass of wine is in order....

mick823 · Mar 2, 2011

Service Pack 1

swblake,

Glad you got it working. I can report that the method described in my previous post #948 (sorry I can't figure out how to link) has a 100% success rate on 4 different installs. I just updated my daughters computer on Sunday with the procedure working without a hitch. It is slow, it is cumbersome, it is a PITA, but it works!

In the full post I also described how I was able to reinstate the Windows Mail with relatively little problems. Again 100% success rate on my 3 PC's. My daughter uses Outlook so the Windows Mail is not installed. All of my PC's are 32 bit so I can't offer any advice on the 64 bit Windows Mail.

I am still of the opinion that the Windows Mail has nothing to do with the failure of the Service Pack 1 to install.

poppa bear · Mar 2, 2011

Just when it's all fixed

What a pot pouri! And just when you think it's safe to go back in the water ....

Loaded SP1 via Windows update engine on backup PC with Windows 7 64bit Professional platform, and WinLiveMail, but no Windows Mail, and surprise, surprise ... guess wot! No go! Stayed at 28% for literally 4 hours. Went to bed and got up later and it was the one constant in an ever changing PC world!

Gotta give M$ top marks for consistency!

swblake · Mar 2, 2011

Not the culprit?

Yes, like others in this thread, I'm slowly coming to the conclusion Windows Mail is likely not the culprit. Initially, I was going to delete all the references the registry file added. Thought I'd print it out, so I'd have a hard copy in front of me. Didn't double-check on the size. 17 pages later, I realized that was unrealistic. So, instead, I removed every reference to 'Windows Mail' and 'msoe.dll' that I could find in the registry. That took a while

and accomplished nothing. So, then, what is it? Something buried in millions of lines of code somewhere? My friend, who also likes to streamline his OS as much as I do, ran SP1 on his desktop, no issues. Laptop 'stalled' at 28% for a long time, like a couple hours, but eventually worked its way past that and completed successfully. Anyhow, I know a winning procedure when I see one... it's running on my laptop right now. As for all those other attempts... wasn't it Thomas Edison who said it wasn't that he'd failed 1000 times in creating the incandescent light bulb; it was that he discovered 1000 ways how NOT to make one. I think I know how he felt.

Greg S · Mar 2, 2011

poppa bear said:
What a pot pouri! And just when you think it's safe to go back in the water ....

Loaded SP1 via Windows update engine on backup PC with Windows 7 64bit Professional platform, and WinLiveMail, but no Windows Mail, and surprise, surprise ... guess wot! No go! Stayed at 28% for literally 4 hours. Went to bed and got up later and it was the one constant in an ever changing PC world!

Gotta give M$ top marks for consistency!

I'm glad to see my Ole buddy swimming in the same pond as me, lol. I, like you, have clean setups to try these things from and with no joy. Prior to that, I put everything back to before WinMail. My only difference is the msoe.dll listing in the winsix folder. I had replaced mine with the Vista version when I was offline. I replaced it with the original whilst online. I had to take ownership of the folder containing the msoe.dll file, the easily placed it back. After that, I ran sfc for that file only in WinMail folder and all came back clean whereas prior to that it wasn't. CBS log gave me which winsxs folder was having fits so it was easy to know which one it was. Anywho, still no SP1 for me. The WinRecovery/Upgrade thingy is not an option for me. I can do it but won't.

poppa bear · Mar 2, 2011

Greg S said:
I'm glad to see my Ole buddy swimming in the same pond as me, lol. I, like you, have clean setups to try these things from and with no joy. Prior to that, I put everything back to before WinMail. My only difference is the msoe.dll listing in the winsix folder. I had replaced mine with the Vista version when I was offline. I replaced it with the original whilst online. I had to take ownership of the folder containing the msoe.dll file, the easily placed it back. After that, I ran sfc for that file only in WinMail folder and all came back clean whereas prior to that it wasn't. CBS log gave me which winsxs folder was having fits so it was easy to know which one it was. Anywho, still no SP1 for me. The WinRecovery/Upgrade thingy is not an option for me. I can do it but won't.

Howdy Greg,

Good to hear you buddy. Seems like old times again! Not sure I'm swimming ... feels more like I'm drowning in a sea of alogarithms; with a couple of conflicting program sharks swimming close by; and the life saver named M$ is sitting on the shore watching me go down for the third time ... and smiling! Pretty much given up on SP1. I've switched off all auto updates and manually update periodically; selecting only the individual ones I feel necessary.

Take care buddy, PB

roncerr · Mar 2, 2011

poppa bear said:
...Pretty much given up on SP1. I've switched off all auto updates and manually update periodically; selecting only the individual ones I feel necessary...

I've been doing the same thing. Tho I usually wind up taking all the updates except drivers I'm afraid of and some very obvious bloat that I will never use like Ultimate's language packs. I was already up to date as of patch Tuesday (w/o Windows Mail...same as you). When SP1 became available on the 4th Tuesday I accepted it. It downloaded and installed as any other update and asked me to reboot. The reboot part of the install took about a half hour on my intel atom processor w/Ultimate. But it finished and worked fine. All I can suggest is just run sfc /scannow a couple of times, look at the final "[SR]" strings and if there are no more than a couple of "normal-for-your-system can't-repairs" assume that's as good as it gets and do the SP1. I would not try to "out smart" sfc or try to fix things myself.

poppa bear · Mar 3, 2011

roncerr said:
poppa bear said:

...Pretty much given up on SP1. I've switched off all auto updates and manually update periodically; selecting only the individual ones I feel necessary...

Click to expand...

I've been doing the same thing. Tho I usually wind up taking all the updates except drivers I'm afraid of and some very obvious bloat that I will never use like Ultimate's language packs. I was already up to date as of patch Tuesday (w/o Windows Mail...same as you). When SP1 became available on the 4th Tuesday I accepted it. It downloaded and installed as any other update and asked me to reboot. The reboot part of the install took about a half hour on my intel atom processor w/Ultimate. But it finished and worked fine. All I can suggest is just run sfc /scannow a couple of times, look at the final "[SR]" strings and if there are no more than a couple of "normal-for-your-system can't-repairs" assume that's as good as it gets and do the SP1. I would not try to "out smart" sfc or try to fix things myself.

Thanks for the input Roncerr. Maybe I was premature in shutting down the SP1 update, if it can take that long. I must admit the machine I was doing it on is an old hyper threading CPU. And in fairness there were no error messages ... I just assumed it had frozen.

Might give it one last fling ... Hmmmmmmm?

Cheers PB

Greg S · Mar 3, 2011

poppa bear said:
roncerr said:

poppa bear said:

...Pretty much given up on SP1. I've switched off all auto updates and manually update periodically; selecting only the individual ones I feel necessary...

Click to expand...

I've been doing the same thing. Tho I usually wind up taking all the updates except drivers I'm afraid of and some very obvious bloat that I will never use like Ultimate's language packs. I was already up to date as of patch Tuesday (w/o Windows Mail...same as you). When SP1 became available on the 4th Tuesday I accepted it. It downloaded and installed as any other update and asked me to reboot. The reboot part of the install took about a half hour on my intel atom processor w/Ultimate. But it finished and worked fine. All I can suggest is just run sfc /scannow a couple of times, look at the final "[SR]" strings and if there are no more than a couple of "normal-for-your-system can't-repairs" assume that's as good as it gets and do the SP1. I would not try to "out smart" sfc or try to fix things myself.

Click to expand...

I must admit the machine I was doing it on is an old hyper threading CPU. And in fairness there were no error messages ... I just assumed it had frozen.

Might give it one last fling ... Hmmmmmmm?

Cheers PB

Old P4 HT here as well. Maybe that has something or alot to do with it.

geekman · Mar 3, 2011

Dude! You is a Legend!
Cheers.

alfranatic · Mar 3, 2011

Well,i finally did it.
I fixed the sp1 installation on my win 7 ultimate 64bits and got winmail back working,right after..

Here is how.

First:-at march 01-2011, i installed sp1 via automatic updates without any problem,but there was no way to get winmail working again..so i removed sp1 and the troubles began.

After trying to update again (failed 4 times) i had to fix a sqmapi.dll (error C0000135) and after that i got over and over the same error 800B0100 so what did i do.

I found the answer to be rather simple: just by installing and running hotfix Tool To Repair Windows Updates ( don't forget to restart.!!) and looking after the cbs logfiles which mentioned that everything was fixed/no problems i could install the servicepack.
This time quite a bit larger ,some 235 MB.

Before updating i removed all winmail files from programfiles and replacing it by the original one,which i still had.

After the update i renamed the winmailfolder to winmail-old and i put the before working folder back (i backed it up ofcourse) again in the same programfiles.
Made a shortcut from winmail.exe and attached it on my taskbar.

Yes everything works and i have all my accounts and extra mailfolders back. :party:

---------------------------------------------------------------------------------------------------

So before the final update (even after 8 times trying) for 64 bits:

1-backup your working winmailfolder

2-replace it by your original one,doesn't have to be 100% virgin..it's not a dealbreaker.

3-fix the install of sp1 by first running the hotfix KB947821.,VERY IMPORTANT..!!!

4-after installing , rename the updated winmail file and copy the original-working-one back into your programfiles

5-your done.

If anyone has more questions i'll be happy to answer them.

:sleepy:

Good luck..

swblake · Mar 3, 2011

Well, as for me, knowing it wasn't CRITICAL to get SP1 installed right away, it nonetheless nagged at me (character flaw?) and so I kept attempting the update, sometimes using other suggestions I'd read, sometimes combining them into a hybrid solution (I mean non-solution), sometimes throwing in some of my own ideas. Mostly, it was because I knew that, within a few months, SP1 would migrate from being an "optional" update to an "important" update. A few months later, there'd be new software products from M$ requiring SP1, much like how SP3 is required for most things now with XP. So, getting it installed and working has been a debacle, but I'm glad it's mostly finished. Two PCs are completed, using the process first mentioned by mick823, I may do the 3rd one tonight. I mentioned there's about an hour's worth of general cleanup after the process finishes; a few minor items have cropped up since. Really minor, actually. For one, you'll get migrated back to IE8. Yeah, I know, who cares? Anyhow, re-migrating back to IE9 RC took all of 5 minutes. The other item was going thru the Windows Media Player setup again, also trivial. There's probably other things I haven't found yet either. Oh, one other thing... my laptop is old, and has some old hardware. HP has NO 64-bit software support for my model, but I'd found resources online months ago when I initially installed Win7-x64. Good thing I saved them, because the SP1 update wiped out my audio and analog modem! So, I'd recommend that if you're upgrading an older PC, don't presume all your devices will work after the upgrade. Find the drivers before you attempt it, and keep them handy.

alfranatic · Mar 4, 2011

In addition to my previous post:

This was the "dealbreaking" problem,which update KB 947821 solved for me:

Installation for TAP-Win32 Adapter V9

De installatie van stuurprogramma FileRepository\oemwin2k.inf_amd64_neutral_e26979d6f0e2cf95\oemwin2k.inf voor apparaat-id ROOT\NET\0000 is voltooid door Stuurprogrammabeheer met de volgende status: 0x0.

Btw,i reclaimed over 2 GB by cleaning the system with various tools.

wing23 · Mar 4, 2011

I see a new problem here:
whenever I start winmail, it works as it should
BUT
taskman doesn't list it was winmail.exe
I see a process named 70c089bf20d5cb01730500001004dc15.WinMail.exe, it's location seems to be C:\Windows\winsxs\Temp\PendingDeletes

any idea how to fix this?

mick823 · Mar 4, 2011

Did you try deleting your old desktop shortcut and creating a new one? Probably a dumb question but sometimes we forget the obvious.

Windows Mail

Attachments

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Similar threads