MSOE.DLL???

[Jeff G]

My Outlook Express Program will not open because it says
MSOE.DLL could not be loaded.....what is going on and how
do I fix it??? This just started up out of the blue.

 

[Lorien]

Sometimes, different versions get in conflict and create a problem. Search
My Computer for MSOE.DLL. I found it in c:\Program Files\Outlook Express
and C:\I386. The version in OE was more recent than the one in I386. Copy
the most recent version to all the other places it exists right now and then
reboot.

You probably don't need it in all those places, but this should get you
going. You can tackle saving a MB here and there another day. LOL!

Good Luck.

 

[Brian Tillman]

Sometimes, different versions get in conflict and create a problem. Search

My Computer for MSOE.DLL. I found it in c:\Program Files\Outlook Express
and C:\I386. The version in OE was more recent than the one in I386. Copy
the most recent version to all the other places it exists right now and then
reboot.

If the OP follows your advice, he'd replace the version in C:\I386 with the
later version in
"C:\Program Files\Outlook Express". Not good. The version in C:\I386 is
the distribution version; the one that the computer was originally installed
with. I think it's a bad idea to overwrite the installation kit.
--
Brian Tillman
Smiths Aerospace
3290 Patterson Ave. SE, MS 1B3
Grand Rapids, MI 49512-1991
Brian.Tillman is the name, smiths-aerospace.com is the domain.

I don't speak for Smiths, and Smiths doesn't speak for me.

 

[Lorien]

Then I assume you've never input a hotfix or a patch, because Microsoft does
that all the time with their fixes. The problem is, they done't always know
every place it might exist and people install software with older versions
that don't check the system for more recent versions, and so they get out of
sync.

They sell programs that actively search for such duplicates to preserve the
most recent version and remove or replace the obsolete "duplicates." Often
the system gets cluttered with a host of versions.

I've yet to see a DLL that isn't fully backwards compatable - but then
again, I do learn something new every day. IMHO, if the source of the file
is valid (e.g., Microsoft and not Joe Schmoe from the South Pacific), the
most recent version is the only one that should be on your system at any one
time. The obsolete duplicates can only cause problems and I do not believe
the more recent releases will cause any backwards comapatability issues
whatsoever.

....But I'm always willing to learn. Can you point out an article that
specifically recommends keeping multiple versions of the same DLL
(especially when both were from the same vendor - Microsoft) because the
newer ones cause problems with older software?