Windows Mail

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

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.

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...

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

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...

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.

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.

Dude! You is a Legend!
Cheers.

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.

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?

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