Outlook Process Does Not Quit

[Major Malfunction]

I've found this program on two computers in my house. Both computers are
running Outlook as part of Office 2000 and both machines are running Windows
2000 SP3 with the latest critical patches. If mail is sent from either
computer, the Outlook process does not shut down after Outlook is closed. If
the Outlook process tree is killed from Task Manager and we open to read
mail, all is well, the process terminates with Outlook closing. It is only
if mail is sent that the process does not terminate.

I discovered this after checking my e-mail and finding the inbox full of
spam that my Rules normally filters out. So far, this is the only
consequence. Both systems are clean (checked with two different antivirus
programs) of any virus or parasite / trojan / malware. This problem cropped
up a couple of months ago, and I've been trying different things to
eradicate it. I've been dealing with this by killing the process after
sending e-mail or using webmail for an alternate provider. Both are
inconvenient. Short of uninstalling and reinstalling Outlook, does anyone
have any clues as to what the problem might be and how to correct it?

 

[Major Malfunction]

I've found this program on two computers in my house. Both computers are

Sorry, that should be "problem", not "program"

 

[Major Malfunction]

I have been experiencing the same thing in Outlook XP for months and it is

driving me crazy. Hopefully an MVP will hear our plight and offer some
solutions.

Glad to hear I'm not alone in this. I mean I'm not glad you're having a
problem, but it's nice to know it's not just me ;-{)

 

[Major Malfunction]

Still no solutions for this problem?

 

[Major Malfunction]

I have been experiencing the same thing in Outlook XP for months and it is

driving me crazy. Hopefully an MVP will hear our plight and offer some
solutions.

Well, it's 11 days and no one else seems to be responding to this problem. I
guess we're the only three people in the world with an Outlook that won't
properly close down after send e-mail.

 

[PaulP in NZ]

It would appear not. Microsoft deny there is a bug.....

I first encountered it when I installed Office2k3. Not
only would it not shutdown, it wouldn't restart either.
The feedback suggestion said uninstall or upgrade Winfax
Pro as that is what is causing the problem. ??? Hello,
OL2k2 and Winfax worked fine, I'd say it was OL2k3 that
causes the problem.

I uninstalled Winfax from the Office 2003 machine. Re-
installed Office 2k3. What's changed? Now I only have to
kill off one process in Task Manager to get Outlook to
restart. That process is Outlook, why? cause it never
fricking shuts down properly.

Someone said it takes a long time to quit as it needs to
synchronize. What what? This is a stand alone PC. I can
leave it on all night and it still won't quit.


Come out of the woodwork geniuses, give us a clue!!

Paul P in NZ

 

[Paul P in NZ]

After an earlier rant I found the following:

http://www.daveswebsite.com/software/olshutdown/default.sh
tml

an interesting little add-in.

The following thread on www.outlookforum.com

http://www.outlookforum.com/t62792-s

actually supplied me with my solution. Even though I had
uninstalled Winfax Pro, it still left a "Winfax Log"
entry in "Data File Management". When I attempted to
remove my whole system locked up. After a reboot I went
and reread the above thread. "Winfax controller must be
running", I re-installed Winfax Pro, removed the entry in
Data File Management and hey presto, all is fine.

I can use both Outlook and Winfax Pro. No upgrade
required.

P.

 

[Major Malfunction]

Thanks for trying, but my problem does not seem to be related to any of the
scenarios presented. There is no WinFax installed on either of my PCs having
a problem with Outlook not shutting down and no, the Outlook window is not
being minimized, it is being closed out. There are also no add-in's being
used in conjunction with the two PCs in my network.

While two bucks is not a big deal, the product advertised on DavesWebsite
does not fix the problem, it just provides an alternate means of killing the
process. I'd like to *fix* the problem, not click another button.

 

[Major Malfunction]

I appreciate your trying and responded to your spin-off thread. Well, with
you that makes four people in the world ;-{)}

(You mean Microsoft didn't tell you that the problem was the bits are upside
down on your computer and the blood rushing to their heads is confusing
them? Or because you are on the other side of the International Dateline
they can never catch-up with the bits in Redmond?)

Totally OT, my Mother-in-Law just returned from your paradise islands. We
are so impressed with the pictures she brought back, my wife and I are
planning to visit. Unfortunately, not a soon as we would like: got kids to
get through college, etc, so we're going to time is for a big anniversary
for us.

 

[moe howard]

driving me crazy. Hopefully an MVP will hear our plight and offer some
solutions.

Well, it's 11 days and no one else seems to be responding to this problem. I
guess we're the only three people in the world with an Outlook that won't
properly close down after send e-mail.

Nope you're not the only people with this problem. I run win2k and
outlook doesn't always shutdown either. I tried searching for the
answer elsewhere, but didn't find one, so I tried here. It's a pain
esp when trying to shutdwon computer - after a while it says it's
waiting for outlook to shutdown or some such nonsense. ctl-alt-del and
kill the outlook process(es) will help it along but I *shouldn't* have
to do this though.

 

[Major Malfunction]

"Major Malfunction" <[email protected]> wrote in message


Nope you're not the only people with this problem. I run win2k and
outlook doesn't always shutdown either. I tried searching for the
answer elsewhere, but didn't find one, so I tried here. It's a pain
esp when trying to shutdwon computer - after a while it says it's
waiting for outlook to shutdown or some such nonsense. ctl-alt-del and
kill the outlook process(es) will help it along but I *shouldn't* have
to do this though.

If you search back through this thread, you will not see any response from
Microsoft on this. I've had this system up and running for three years, yet
I was without this problem for over two years. I have no idea what changed
as I have not added new hardware and no new software that interacts with
Outlook during that time, only Microsoft updates to the OS.

I'd like to take a poll of people who have this problem and find out if they
have changed anything on their system prior to this problem cropping up.
Maybe we can link this behavior to some program interaction . . . or maybe
to a Microsoft update.