Endpoint Protection

I am a standalone home PC user, formerly using Sym Antivirus Corporate through work, advised to upgrade to Endpoint Protection through work.  Was told that in the process of insalling EP, Sym Antivirus would automaticallyt be deleted.  It wasn't.   Tried to delete Antivirus through Control Panel, but got error messages.  Finally  (perhaps stupidly), just deleted the program by clicking and deleting.

However, there is a .log file: that is causing me trouble
c:/docs and settings\allusers\applicationdata\Symantec\symantivirus corp\7.5\Logs\07012009
my disk defragmenter hangs when it reaches it, and when I try to delete it manually, I get:
Error deleting file or folder.  Cannot delete; access is denied.  Make sure that the disk is not full or write-protected and that the file is not currently in use.

I can delete other files with no trouble.

Any ideas??? Many thanks!!

Also: checked this .log file's properties -- not write protected.

maybe cleanwipe can help you. Open a ticket with tech support to grab a copy of cleanwipe

Cleanwipe is one option, and if you do call in to open a tick you should post your case number here so we can check up on it for you. But before you do that, first though have a look at what processes are running on your system? See any that look like the may belong to symantec. I don't run SAV myself so I can't tell you what the processes names are but they should be fairly easy to spot. If you find one kill that process and see if you can delete the log.

Also you should be able to do the erase command from the dos prompt to get rid of it, but usually Windows will only lock a process in this way if it really isn't suppose to be deleted (like for instance if the program is still using it and depends on it). So this option isn't the best and you should only attempt that if you are comfortable issueing commands for the command prompt. Another thought I jsut had is maybe to try renaming the file then deleting it. This shouldn't make a difference but you could give it a try. Really though the best thing to do is to check for the process that is currently using the file, because it will most likely be some part of SAV and will also have to be taken care of.

Cheers
Grant