MS Office 2000 -loading up CPU

[Hootyhoo]

I realize there probally something very simple to the cause of this but I
guess my minds gone beyond seeing it.
Computer -Dell Optiplex 280 w/ 1gig ram, really small video, but was working
efficiently, all updates installed for XP.

Heres the symptoms:
Computer taking longer to start up -kinda suddenly.
Used MS Office in morning worked fine, used in afternoon and suddenly took
all of CPU resource and never finishes loading file. Left loading for 15
minutes and still not done, or may be done but with CPU maxed doesn't work
properly.
Back out of loading file, but CPU stays maxed out.
Everything works fine until I try to run any Office program.
Before starting Office and running any other program
CPU 2-10%
Ram 300-350 mb
After attempting to run an Office program
CPU instantly spiked and stays at 100%
Ram 300-350 mb

Whats been done:
Virus Scan -3 times -Comodo
Defrag -3 times
System restore -back 2 weeks -3 times
Checked for any programs recently installed that maybe running in background
Checked startup from program list.
Viewed task manager as I started up Office file. The only change is the CPU
usage pegs out. Even Ram stays at about 346.
Watched in Comodo the apps running and nothing happens that wasn't happening
before.

During all this, 1 of my shutdowns and only once stopped with a message
about shutting down before -HiddenFax something in done. Canceled all
printing and faxing operations, and never have ran a faxing program on
purpose. Did a search for anything named HiddenFax and nothing came back.
Like I said it only came up once. Thought maybe it was trying to fax
something everytime I went into Office.
Nothing shows.
If you're still reading this then it must confuse you as much as it confuses
me. Any reply on what to try or do would be greatly appreciated.

 

[Bob I]

The word is COMODO had a bad update.

 

[Peter Foldes]

Quote from the Comodo support forums:
_____________________________
Hello Everyone,

Because of an issue with the latest virus database, some computers might
observe significant CPU consumption problems caused by cmdagent.exe.

You might observe this issue if your virus database version is 2525 and
later. We have reverted the problematic updates. However, because of the
nature of this issue, already affected computers might not function properly
to revert the updates back.

For those computers, the following instructions can remediate the issue:

1 - Reboot your computer in safe mode
To enter to the safe mode, you need to press F8 button before Windows starts
booting until you see the boot menu. In the boot menu, select the safe mode.
2 - Delete the file in c:\program files\comodo\comodo internet
security\scanners\bases.cav
3 - Copy c:\program files\comodo\comodo internet security\repair\bases.cav
to c:\program files\comodo\comodo internet security\scanners folder(this
action will replace the current bases.cav file with the original bases.cav
file that comes with the installation).
4 - Restart your computer and Update your virus database again.

after these 4 steps, everything should go back to normal.


Alternatively, you can manually download the latest bases.cav file from
http://download.comodo.com/av/updates311/sigs/bases/BASE_END_USER_v2456.cav
and replace the problematic bases.cav with this version.

We are sorry for the inconvenience this might have caused.

Regards,
Egemen

 

[Hootyhoo]

I appreciate the reply(s).
Another point that I forgot to mention was that I unistalled and reinstalled
MSoffice, as an attempt to many remedy the problem.
I have database 2537. Is That gonna make a difference?
Also I sat down and watch the complete shutdown and found that there where 3
files that had problems with the shut down, and offered to "end now or cancel
shutdown". I picked end now this time, but its obvious that they have been
ending on themselves. I just did'nt sit for the 10 minutes to watch the
complete shut down before.
In order of apperence.
Point32.exe
Explorer.exe
HiddenFaxWindow

I will still do what you instructed to see if that might be the issue.
Thanks again