G'Day Folks,
In another topic we discussed Outlook Express (part of Internet Explorer functions) and we seem to be having similar issues with Microsoft Outlook 2003 (part of the Microsoft Office 2003 Suite)
!!! - please do not confuse the issues as the Outlook eMail programs are different in behaviour (behavior) and function.
The problem is that using BDIS and or BDTS 2009 (also occurs in 2008 versions) the Microsoft Outlook 2003 does not close and stays resident as a TSR (Terminate Stay Resident) active program on the right hand side of the "Start Bar"
This can obviously be closed using the Task Manager, however it gets to be a pain in the rear having to do this all the time.
Microsoft Outlook 2007 does not appear to have this problem, i.e. the machine we use it on closes correctly with either 2008 or 2009 versions of BDIS or BDTS installed.
This however is not true in all instances as our customers have reported the same error which we fixed by either or both, repairing the Office and or BD installation. Unfortunately there was no president in which we repaired 1st as in some instances repairing either one, fixed the problem.
It should be noted that this problem of Microsoft Outlook 2003 (or other versions) not closing on XP machines is not restricted to being caused by BitDefender programs as other Internet Security suites like Norton, Kaspersky, McAfee and others have been reported as causing the same problem and these type of programs are listed among the most likely to do so i.e. cause the Microsoft Outlook not to close correctly.
Searching for "Microsoft Outlook 2003 does not close" will reveal 1000's of reports concerning this issue, all much saying the same thing, however no definitive answers to solve the problem. Where there are utilities that will do the job, i.e. close MS Outlook (any version) for you, it is however not the way to solve the problem caused by the Internet Security suites. (We tried these closers and would not recommend them !!)
Microsoft Outllok 2003 does not close
Again this has been an ongoing issue and also occurred in older versions of BitDefender.
Any suggestions for a fix ? - Please - Only reply if you have the answer to fixing this issue - thanks.
