Windows Mail could not be started

  • Thread starter Thread starter Betsy
  • Start date Start date
B

Betsy

Unlike others who get the message: Windows Mail could not be started.
Initialize junk filtering. Your computer may be out of memory or your disk is
full (0x80004005)
I am not using McAfee, I'm using Norton. Been using Vista for a couple of
years, know my disk is not full, know I'm not out of memory and am baffled!!
Any ideas?
 
Norton security products are among the top three troublemakers for
Windows Mail. Symptoms often don't surface until several months have
gone by, or until an update occurs.
First, be sure to disable its email scanning, for the reason explained here:
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm

Several users here have reported that Symantec will give you a free
upgrade to Norton Antivirus 2009, which may cure the problem. If
interested, contact Symantec via online chat.

Disabling the Norton program is often insufficient. Do a trial uninstall,
followed by using their debris removal tool:
http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039

Instead of uninstalling your antivirus, another option is to upgrade to
Windows Live Mail, which is more resistant to the adverse effects of overly
intrusive antivirus products: http://download.live.com/wlmail
 
I am trying to make Windows Mail work firsttime after many months of owning
a new Vista-PC and after reliably using outlook on Windows-2000 for about
10 years - which is outdated now.

Windows Mail generates this error:
1. Windows Mail could not be started. The application was unable to open the
Windows Mail message store. Your Windows Mail mailbox data is currently being
used by another program, such as a virus scanner. Close the program or wait
for it to complete its operation, then open Windows Mail again (0x800C0155,
2). After accepting OK, I got the second message:
3. Windows Mail could not be started because MSOE.DLL could not be
initialized.

4. Downloaded Windows Live Mail which generated the following Error:
"Windows Live Mail could not be started. It may not be installed correctly.
Make sure that your disk is not full or that you are not out of memory.
(0x80041161)"
5. Prior to that, I disabled all elements from the startup list and non-MS
services from msconfig,
the problem remained unresolved.
6. upgraded the vista-SP1 and repeated the above steps. Same Problem.
7. disabled all antivirous software. Problem remained unresolved. Vista is
running only the
basic microsoftware services and programs but the problem remained unresolved.

Any suggestion ? Is there any thing I missed to disable or to execute in
the above steps to make either the Windows mail or Windows Live Mail work? I
am desparate as I depend on the mail system. The above
described suggestions all I could find from various community sites which I
executed one by one.

Any help would be appreciated !!!!! - Microsoft any Solution ????????

Sanders
 
This post is a duplicate of your post under "Windows Mail could not be started errors".
 
After Windows Update did an update, I've had the similar errors.
That the mail files could not be found.
That MSOE.DLLL could not be found.
I tried a system restore and the system restore did not work,
saying there was an error, though it didn't identify the error.

I don't want new blank mail files.
I want the old ones working.
Any help?
 
Still trying to undo the Windows Update.

I tried another System Restore, using another restore point, which also gave
an "unidentified error" and failed.

Windows Mail still doesn't work since the update.
But now I've got an error number from Windows Mail.
0x800C013E
And it says my computer may be out of memory --- it isn't --- and that my
disk may be full --- it isn't either.

Denise Moore
 
Windows Mail STILL won't start.

But it is now giving a slightly different message about MSOE.DLL
saying that MSOE.DLL can't be initialized.

(No, I'm not using Outlook Express.)

DeniseM
 
Perhaps you need to do a repair install of Vista but I don't know the
details of how to do that; you need to look in the Vista help or in a forum
or newsgroup for Vista.

I don't know why it is complaining about MSOE.DLL but it might be that
Windows Mail has code from OE that was not properly revised.
 
I believe the repair install puts things back to where they were two years
ago when we bought the computer. That would wipe out a lot of stuff! I hope
there's a solution less drastic than that!

Denise Moore
 
That symptom is usually caused by interference from an antivirus
program. Which antivirus are you running?
As a minimum, email scanning in the antivirus should be turned off,
although that may not be sufficient to eliminate all bad effects.
In a worst case scenario, your antivirus may need to be uninstalled.

Email scanning in any antivirus should be disabled, for reasons
explained here:
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm

If no improvement after disabling email scanning, consider upgrading
to Windows Live Mail, because it is less prone to suffering bad effects
from overly intrusive antivirus programs:
http://download.live.com/wlmail
 
Gary, thanks. I saw that Microsoft likes to blame anti-virus programs and
Norton in particular. Which I think is unprofessional and rather unhelpful
of them, but I turned off e-mail scanning. That made no difference.

I did come across WMUtil and tried it. Again, no difference.

I had dismissed Windows Live Mail as being an online thing, like Live
Messenger, but ending up trying it anyway. Maybe it would have worked before
the Windows Update, but whatever the Update did, caused the same errors in
Windows Live Mail as in Windows Mail.

But I have seen those sometimes helped some people. So thanks for the
suggestions.

It appears that running sfc.exe somehow solved the problem, though it said
it found corrupted files that it couldn't fix. The log file is so HUGE that
there is just no way I can check out which ones it didn't fix and even if I
found them I wouldn't know how to fix them. But it seems to have fixed
something, even though the Microsoft documentation says the messages that it
has fixed a file are misleading. (Very strange!)

Then I was finally able to get back into Windows Mail. Importing the mail
files from a backup worked, though it wanted to keep re-importing them, so I
have some duplicate folders and folders misplaced, but we can now get at the
messages. Hurrah!

Thanks again, though, for the suggestions.
 
I'm getting the same messages and cannot open Windows Mail. Denise M Toronto
said she went to SFE.exe or sfc.exe and it got fixed so she could at least
get her mail...after reading her message i went to my antivirus...AVIRA...to
uninstall then went back to Denise M's email and could not find the sfe.exe
or sfc.exe whichever is correct on her message...like it just
disappeared...can anyone tell me which it is sfe or sfc and where do you find
this sfc or e.exe on the computer. I am not computer savvy...just email and
documents and Explorer is all I know and have no knowledge of "inside". I
usually press the wrong button when given a choice and so i am in fear of
doing things on computer on my own.

Mahalo from Kauai...Leota
 
Aloha and Talofa Denise where do you find sfc.exe on the computer. I have
same problems you have/had. Does anyone know where? And do you just click the
sfc.exe?

Mahalo fa'afetai

Leota
********************************************************
 
Thanks for reporting back. Windows file corruption is somewhat unusual,
so we don't suggest using sfc.exe for a first go-around.

From years of experience with its problems, most tech guys like myself
tend to recommend not using Norton security products with Microsoft
mail programs.
 
@Leota: Running a technical repair utility like sfc.exe should be kept as
a last resort. It is not geared for the average user.

I don't see a detailed problem statement from you in this thread.
I take it that after you uninstalled Avira there was no improvement?

Did you try installing Windows Live Mail?
See http://download.live.com/wlmail
 
Where did you see "that Microsoft likes to blame anti-virus programs and
Norton in particular"? I know that the experts here have learned from
experience that some anti-virus programs and Norton in particular cause
problems. I doubt that there is much from Microsoft on the subject and when
they do identify a problem I am sure Norton would (should) not deny that it
is a problem.

I used Symantec AV for a year and had a few bad experiences. For one thing,
it used a huge (7 GB?) amount of hard drive space when my hard drive space
was limited and it took them months to get around to telling me how to fix
it.
 
Also, if you want to blame Microsoft, then blame them for not designing an
OS that supports AV software. That is the problem; AV software vendors must
develop highly technical software to retrofit Windows to detect, prevent and
remove malicious software and it is sure easy to mess up. A vendor's success
or failure depends on the management's dedication to quality and comments in
this newsgroup are a likely result of that.
 
Sam, while it would have been nice to be able to count on a fix showing up
soon in Windows Update --- I'm sure I wasn't the only one adversely affected
by that Update --- I couldn't count on it. So I was looking all over the
place for various solutions. And yes, I did run across a number of nasty
comments made by Microsoft people about antivirus programs and Norton in
particular. And while some of the Microsoft people might have been
well-intentioned telling people to just install their antivirus software,
that does NOT seem very helpful to the people looking for help. So yes,
compared to some of what I've seen elsewhere, I did feel the answer given
here was much more polite and professional. And deserved to be commended.
 
It is accessed through a command prompt window. Go to accessories and run a
command prompt window with administrator privileges. The command is
SFC.EXE /SCANNOW

In my case it generated a HUGE log file, which I basically had to ignore
because even if I had figured out what to pay attention to, I wouldn't have
known what to do about those things. I came across a Microsoft document that
said the log entries that claimed SFC had fixed certain things were not true.
And SFC itself said there were some things it had not fixed. But all that
said, it did appear to fix SOMETHING on my computer.

----
 
Back
Top