I don't think Windows Update has anything to do with this.
Is WinXP SP3 installed?
When does your current Norton 360 subscription expire (or is it really
Norton Security Suite freebie from your ISP)?
Have you ever downloaded/run the Norton Removal Tool?
Has another Norton application or a McAfee application ever been installed
on the computer (e.g., a free-trial version that came preinstalled when you
bought it)?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1a. Move any messages that you want to keep out of Sent Items and Deleted
Items folders and into other local OE folders you've created for archiving
(saving) such messages.
1b. Move 99% of your messages in your Inbox folder to other local OE
folders, too.
2a. Write down the location of your identity's store
(http://www.insideoe.com/files/store.htm#storemain).
2b. Enable 'Show Hidden Files and Folders' via Start | Control Panel |
Folder Options | View (cf.
http://www.bleepingcomputer.com/tutorials/tutorial62.html).
3. Close OE.
4. In Windows Explorer, navigate to your store folder, find & delete the
files Outbox.dbx, Sent Items.dbx, and Deleted Items.dbx.
To avoid such problems in the future, adhere to the following caveats:
- Don't use Inbox or Sent Items to archive messages. Move them to local
folders created for this purpose.
- Empty Deleted Items folder daily.
- Frequently perform a manual compact of all OE folders while "working
offline". More at http://www.insideoe.com/files/maintain.htm
- Do not cancel Automatic Compacting, should it occur, and do not attempt to
close OE via Task Manager or shutdown your machine if Automatic Compacting
is taking place.
- Disable email scanning by your anti-virus application. It can cause
corruption (i.e., loss of messages) and provides no additional protection:
Why you don't need your anti-virus to scan your email
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
"Jeff" <Je...@discussions.microsoft.com> wrote in message
news:A7C31BC6-0F84-468F...@microsoft.com...
: This problem started awhile back (mid to late 2009) when I could no longer