Event log in Symantec Antivirus Corporate Edition V9.0

I am using Symantec Antivirus Corporate Edition V9.0.  Today I noticed that when I look into a folder within the application called event log, it makes notes with exclamation points that a number of files could not be opened or scanned.  There are about sixty notations or events noted.  I will list several of them below so that you understand what I am talking about.

Scan could not open file C:\WINDOWS\system32\drivers\atapi.sys [00000003]
Scan could not open file C:\WINDOWS\system32\config\SECURITY.LOG [00000003]
Could not scan 1 files inside C:\WINDOWS\I386\SOFTBAR.IN_ due to extraction errors encountered by the Decomposer
Scan could not open file C:\Documents and Settings\LocalService\Application Data\Webroot\Spy Sweeper\Temp\SSCS0B4752E9-74E2-4B31-846E-1F98CE7850FC.tmp [00000003]

All of the listed events are "scan omissions".  Because I have several PCs all running Windows XP I checked the event logs on those as well and it is the same thing.  Can anyone tell me if this is normal and if it is normal what does it mean?  Why can't the antivirus program scan these files?  Is there any danger that because these files can't be scanned that I could have a virus lurking in one of those files?  
When I run scans, the program finds viruses on occasion but it has always removed or quaranteend the virus and makes a log of that as well.

Dean Blair
Who is Participating?
I would say this is normal and nothing to worry about. These are all legit files that could not be accessed because they were in use at the time:

atapi.sys : disk/cd driver
security.log : The Security Event Log
softbar.in_ : Part of the original Windows installation file
The tmp file: You must have Spy Sweeper running at the same time.

No, there is no danger that these could be harboring viruses (at least virtually no danger).

In the case of compressed files (like .zip) Symantec tries to expand them and examine for viruses. In the case of the softbar.in_ file it mistakenly thought thast was compressed, but then could not expand. That is just a mistale on the part of Symantec.
deanblair1Author Commented:
Thank you R-k
Thanks and good luck.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.