One way might be if ZASS allowed command line options to run an anti-spyware scan, but I have not found any yet. Best regards. Since 1994 Back to top #3 JEtkins JEtkins Occasional Forum Poster Members 51 posts Posted 24 September 2008 - 07:40 PM The catalog in on my local C: drive, in that And so I am also thinking that the approach of disabling KLIF is not going to work if I wish to have the Anti-Spyware function. have a peek here
If necessary the file can be reset manually or via a command prompt (beginning from application version 6.0 MP2). Edit: Forgot to mention ZoneAlarm version:7.0.408.000 Edited by Mickeyjoe, 02 December 2007 - 10:44 AM. Then delete the fidbox.dat. I did find klif.sys but no kiln files in the indicated directory.
Back to top #12 JEtkins JEtkins Occasional Forum Poster Members 51 posts Posted 27 September 2008 - 04:53 PM OK, I set it to run as the logged-in user, but got To re-enable scanning, repeat the above steps except this time enable KLIF. Since 1994 Back to top #9 JEtkins JEtkins Occasional Forum Poster Members 51 posts Posted 26 September 2008 - 02:58 PM I'll give it a try, but won't that create problems I also noticed that fidbox.dat and fidbox.idx are the only files of their type in the my system32\drivers folder.
Rather, this seems to be a legitimate curiosity about a file that you've noticed. It contains mostly .sys-files (about 360 of them) and some .dll, although there are other exceptions too. fwiw, per procmon's display record, my anti-virus (ravmond.exe) was accessing C:\WINDOWS\system32\wbem\Logs\FrameWork.log from 3:03:02 PM to 3:03:08 PM, so the timing is there, but not mention of fidbox. oldsodOctober 14th, 2008, 04:01 PM
jasimon wrote: I have determined that the fidbox.dat grows 20MB every time NOD32 does a full scan.
Stop Kaspersky Anti-Virus 6.0 for Windows Servers Enterprise Edition either via the product console or by running the following command in the command prompt: net stop kavfs 2. Other than some occasional testing. Back to top #5 Doug Doug Retired Administrator -Tech Team Tech Team 10,057 posts Posted 04 December 2007 - 01:09 PM Hi Mickeyjoe, Have a look around in your Control Panel Kaspersky has taken a lot of heat for designing iSwift this way, and if you search online (for example, 'Kaspersky you lost me at iSwift') you will find several extremely lengthy
Let us know if you find items that relate to your original question, and/or other questions. oldsodOctober 17th, 2008, 01:21 PMI had the same problem.
jasimon wrote: fidbox is used by the Kaspersky scanning function, which apparently has both an AV component and an anti-spyware component. Join the ClassRoom and learn how. And suppose there's no way to clear it, what then?
- Please advise as how to remove fidbox.dat.
Search all files of the Windows directory for the fidbox.dat in all files and remove it's mentions. I do not need to use this function, as I use NOD32 for AV. So fidbox.dat is used by that virus scanner. I would like to get rid of fidbox.dat, because it takes 4GB of space, and insists on becoming horribly fragmented. I guess each time the svchost or something else hit it, it grew by another dot or space, or such... If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download and unzip them from here.)Under "Configuration and Preferences", I get a message that "The system is NTFS. As Oldsod said, the best solution is to uninstall ZASS and run ZAPro instead, along with a separate antivirus program. The best solution maybe just periodically start in the safe boot and delete the fidbox.dat to keep it's size at a minimum.
And thanks again for sharing your knowledge. Thanks for contacting the ZL, they are really the ones who can make effective patches and fixes. Robin MayoffDirector, Retrospect Support ServicesRetrospect Employee #63. I'm curious to know if resetting it according to their instructions reduced the file size.
Have a work around. navigate here Need some help if possible please. Back to top Advertisements Register to Remove #2 Jacee Jacee SuperHelper Classroom Teacher 7,658 posts Posted 02 December 2007 - 02:41 PM Did you, at one time, download and scan The catalogs folder - and the catalog files themselves - have Full Control permissions for both my user account and SYSTEM.
oldsodSeptember 30th, 2008, 03:37 AMthat fidbox.dat is used by the Kaspersky AV embedded with ZASS. They may otherwise interfere with our toolsDouble click on ComboFix.exe & follow the prompts.As part of it's process, ComboFix will check to see if the Microsoft Windows Recovery Console is installed. dallas7, Sep 12, 2009 #8 ~Q~ Command Sergeant Major dallas7 said: ↑ This thread isn't about an infected system or the use of an appropriate tool.Click to expand... Check This Out Run Kaspersky Anti-Virus 6.0 for Windows Servers Enterprise Edition either via the console or by running the following command in the command prompt: net start kavfs Warning Important: o no anti-virus
jasimon wrote: I understand
Voila! Now fidbox.dat and fidbox.idx can be removed. Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password?
Once deleted it will no longer impact your hdd.
By the way I had used the same CD with which I had upgraded to XP. 0 #6 Broni Posted 30 August 2009 - 09:11 PM Broni Kraków my love :) Something that I perhaps did not emphasise in the original post -- fidbox.dat it always in an extremely fragmented state, which on some of our system is impacting performance. Thanks for contacting the ZL, they are really the ones who can make effective patches and fixes. Rather it is ZASS scanning any file, which then causes fidbox to do something to store something about that file.
However, it then rapidly grows back when KLIF is reenabled. zuluNovember 25th, 2008, 11:45 AMDuring my testing I found that a fair number of ObjectIDs were written during the initial installation of ZASS, without ever using or enabling the Antivirus module. You can try the following. http://easygiftsoftware.com/c-windows/c-windows-system32-drivers-pxhelp20-sys.html Edited by Mickeyjoe, 06 December 2007 - 08:32 AM.
You do not mention any system performance problems. I now have the response from the higher level support -- "we are not going to fix it." As has been surmised in this thread by Oldsod and jazzi, since ZA Here are the steps to removed fidbox (and disable all ZASS scanning): 1. http://www.pctools.com Usual disclaimers.
Double-click that icon to launch the program.If asked to update the program definitions, click "Yes". The file stores only actual information about files really existing in the system if any file is deleted, the information about this file is deleted from the file fidbox.dat too. Share this post Link to post Share on other sites This topic is now closed to further replies. Register now to gain access to all of our features, it's FREE and only takes one minute.
I also ran "svchost viewer," which provided the following (additional?) info: The svchost with PID 1504 is using ~14MB of memory (memory use varies; only 6MB when I reloaded svchost viewer).