How do you close Outlook 2007 beta ?

I just tried it for the first time after setting up my email account and
after I was done it would not close. See screenshot
here .

Joe--

You're going to get the best quality answers in the Outlook groups because
that's where the Outlook experts are. They are excellent, several of them
are always there, and they answer very fast.

You can click Win Mail and put Outlook in search--I don't know why you use
the slow clunky Web interfact if you have Vista.

The web interface for the Outlook group is
http://groups.google.com/group/micro....outlook?hl=en

I don't know of this as a known Outlok 2007 issue.
http://www.slipstick.com/outlook/ol2...own_issues.htm

You can try to fix Outlook by using Help>Repair or Repairing it from
Add/Remove.


If you can't kill it, put up Taskman>Process tab>highlight outlook.exe and
right click it>end


For your enjoyment

65 Reasons why Outlook 2007 Will Suck
http://chris.pirillo.com/2006/05/26/...007-will-suck/

CH

"Joe Ogiba" <JoeOgiba@discussions.microsoft.com> wrote in message
newsC0E55C9-A82F-4424-B38C-C9DF44AB5BE1@microsoft.com...

>I just tried it for the first time after setting up my email account and
> after I was done it would not close. See screenshot
>
> here .

Chad is correct. If you can't close it, right click your taskbar, select Task
Manager, on the processes tab right click OUTLOOK.EXE and end it. That's the
best way. If it loads at startup, try removing it from there.

"Joe Ogiba" wrote:

> I just tried it for the first time after setting up my email account and
> after I was done it would not close. See screenshot
> here .

I meant to add DJ--I have Outlook 2007 working well on Vista and it has on
several builds but frequently either Outlook or Outllok Express will stay
runing in the background after I close them so I have to go to Task Manager
Processes to get that done.

In Windows XP, I have noticed for a long time that when I use OE (that was
the way I read the groups in XP so I used it all the time) or Outlook that
often the process persisted and neither detect and repair for Outlook, or a
repair install of XP, or in the case of OE running SFC (System File
Checker) made a difference. I just went to processes and killed it if
necessary. The way I'd find out about it is if I had a hang, or I went to
reopen OE for some other reason--I got the message an instance was still
running and then I closed it in Task Man and everything was fine.

When it happens, and it's not every time, I've come to accept it as a .5
second extra little chore I might have to do.

I linked a list of problems frequently seen in Outlook 2007 from MSFT, but
the only problem I've had so far with it on XP or Vist came because of an
error caused by the incomplete uninstall of Business Contact Manager that I
had with my Outlook 2003. Once I realized this from googling and nuked the
file, it worked like a charm.

CH


"DJ TECH" <comp_nerd3@msn.com> wrote in message
news:CC077B81-16EF-4C22-B87F-D68CA73A7897@microsoft.com...

> Chad is correct. If you can't close it, right click your taskbar, select
> Task
> Manager, on the processes tab right click OUTLOOK.EXE and end it. That's
> the
> best way. If it loads at startup, try removing it from there.
>
> "Joe Ogiba" wrote:
>

Thanks Guys,

I used Task Man like you said and it worked.

Joe

"Chad Harris" wrote:

> I meant to add DJ--I have Outlook 2007 working well on Vista and it has on
> several builds but frequently either Outlook or Outllok Express will stay
> runing in the background after I close them so I have to go to Task Manager
> Processes to get that done.
>
> In Windows XP, I have noticed for a long time that when I use OE (that was
> the way I read the groups in XP so I used it all the time) or Outlook that
> often the process persisted and neither detect and repair for Outlook, or a
> repair install of XP, or in the case of OE running SFC (System File
> Checker) made a difference. I just went to processes and killed it if
> necessary. The way I'd find out about it is if I had a hang, or I went to
> reopen OE for some other reason--I got the message an instance was still
> running and then I closed it in Task Man and everything was fine.
>
> When it happens, and it's not every time, I've come to accept it as a .5
> second extra little chore I might have to do.
>
> I linked a list of problems frequently seen in Outlook 2007 from MSFT, but
> the only problem I've had so far with it on XP or Vist came because of an
> error caused by the incomplete uninstall of Business Contact Manager that I
> had with my Outlook 2003. Once I realized this from googling and nuked the
> file, it worked like a charm.
>
> CH
>
>
> "DJ TECH" <comp_nerd3@msn.com> wrote in message
> news:CC077B81-16EF-4C22-B87F-D68CA73A7897@microsoft.com...

>
>
>