If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Gradual out of disk space - fidbox.dat
In case anybody didn't know about it, there's a
remnant from some popular virus scanner that gives you a growing file that eventually gets big enough to matter. c:WINDOWS/system32/drivers/fidbox.dat It's harmless to delete (and will grow again over a period of months) but you have to be in safe mode. A smaller one c:WINDOWS/system32/drivers/fidbox.idx can be deleted at the same time. The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them. -- On the internet, nobody knows you're a jerk. |
Ads |
#2
|
|||
|
|||
Gradual out of disk space - fidbox.dat
Ron Hardin wrote:
In case anybody didn't know about it, there's a remnant from some popular virus scanner that gives you a growing file that eventually gets big enough to matter. c:WINDOWS/system32/drivers/fidbox.dat It's harmless to delete (and will grow again over a period of months) but you have to be in safe mode. A smaller one c:WINDOWS/system32/drivers/fidbox.idx can be deleted at the same time. The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them. How is that info going to help anyone since you deliberately chose to omit WHICH anti-virus program is modifying that file? There a tons of anti-virus programs available. Your post is like saying "A certain program to remain unnamed will crash the OS when you use its File - Save dialog". Uh huh, yeah, like who would know what to look out for. If the "feature stays there long after the virus scanner is gone", where "gone" is assumed to mean uninstalled, then the program wasn't really uninstalled, was it? It's still there updating that file. Perhaps the partial uninstall is why the remnant process doesn't properly manage that file. Some anti-virus software has an incomplete uninstall which not only leaves behind remnant registry entries and files but also leaves behind remnant active processes; however, you won't name the crappy software. Thanks for nothing. Is it a secrete anti-virus program that you created for only your own use or software that only you are supposed to know about? Without identifying specifics, you're just spreading FUD. |
#3
|
|||
|
|||
Gradual out of disk space - fidbox.dat
VanguardLH wrote:
Ron Hardin wrote: In case anybody didn't know about it, there's a remnant from some popular virus scanner that gives you a growing file that eventually gets big enough to matter. c:WINDOWS/system32/drivers/fidbox.dat It's harmless to delete (and will grow again over a period of months) but you have to be in safe mode. A smaller one c:WINDOWS/system32/drivers/fidbox.idx can be deleted at the same time. The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them. How is that info going to help anyone since you deliberately chose to omit WHICH anti-virus program is modifying that file? There a tons of anti-virus programs available. Your post is like saying "A certain program to remain unnamed will crash the OS when you use its File - Save dialog". Uh huh, yeah, like who would know what to look out for. If the "feature stays there long after the virus scanner is gone", where "gone" is assumed to mean uninstalled, then the program wasn't really uninstalled, was it? It's still there updating that file. Perhaps the partial uninstall is why the remnant process doesn't properly manage that file. Some anti-virus software has an incomplete uninstall which not only leaves behind remnant registry entries and files but also leaves behind remnant active processes; however, you won't name the crappy software. Thanks for nothing. Is it a secrete anti-virus program that you created for only your own use or software that only you are supposed to know about? Without identifying specifics, you're just spreading FUD. I think it's a common module from Kapersky code. Just check if you have the file. It's a roach motel kind of thing. It stays behind no matter what. I think for instance Zone Alarm installs it, and maybe AVG, in old versions at least. Harmless to delete but it will grow again and you delete again after a few months. -- On the internet, nobody knows you're a jerk. |
#4
|
|||
|
|||
Gradual out of disk space - fidbox.dat
Ron Hardin wrote:
VanguardLH wrote: Ron Hardin wrote: In case anybody didn't know about it, there's a remnant from some popular virus scanner that gives you a growing file that eventually gets big enough to matter. c:WINDOWS/system32/drivers/fidbox.dat It's harmless to delete (and will grow again over a period of months) but you have to be in safe mode. A smaller one c:WINDOWS/system32/drivers/fidbox.idx can be deleted at the same time. The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them. How is that info going to help anyone since you deliberately chose to omit WHICH anti-virus program is modifying that file? There a tons of anti-virus programs available. Your post is like saying "A certain program to remain unnamed will crash the OS when you use its File - Save dialog". Uh huh, yeah, like who would know what to look out for. If the "feature stays there long after the virus scanner is gone", where "gone" is assumed to mean uninstalled, then the program wasn't really uninstalled, was it? It's still there updating that file. Perhaps the partial uninstall is why the remnant process doesn't properly manage that file. Some anti-virus software has an incomplete uninstall which not only leaves behind remnant registry entries and files but also leaves behind remnant active processes; however, you won't name the crappy software. Thanks for nothing. Is it a secrete anti-virus program that you created for only your own use or software that only you are supposed to know about? Without identifying specifics, you're just spreading FUD. I think it's a common module from Kapersky code. Just check if you have the file. It's a roach motel kind of thing. It stays behind no matter what. I think for instance Zone Alarm installs it, and maybe AVG, in old versions at least. Harmless to delete but it will grow again and you delete again after a few months. Here's what I found for Kaspersky: https://support.kaspersky.com/1700 While that article discusses the Enterprise edition, the feature may be available in other editions. My recollection of Kaspersky (but it might've been a different anti-virus program) was that it use alternate data streams of files to record whether or not a file had already been tested. A hash and flag got recorded in a file's alternate stream to identify the file (the hash would check if the file had been changed since the last time it got recorded) and the flag said whether that file already got tested or not. That way, the AV scanner did not have to spend time retesting the same unchanged files over and over. Alternate data streams are a property of NTFS so you must be using that file system to make use of ADS https://en.wikipedia.org/wiki/NTFS#A...eams_.28ADS.29 Apparently either Kaspersky abandoned using ADS or it was something else that used ADS to track scanned files. Instead of using ADS, Kaspersky is [now] using its own database. However, if you uninstalled Kaspersky per your "The feature stays there long after the virus scanner has gone" then having any of its process lingering around to continue building the database sure makes it look like you did not [completely] uninstall Kaspersky. |
#5
|
|||
|
|||
Gradual out of disk space - fidbox.dat
On Tue, 03 Jan 2017 17:10:47 -0500, Ron Hardin wrote:
I think it's a common module from Kapersky code. Just check if you have the file. It's a roach motel kind of thing. It stays behind no matter what. I think for instance Zone Alarm installs it, and maybe AVG, in old versions at least. Harmless to delete but it will grow again and you delete again after a few months. Try going into safe mode, delete that file, then create a subfolder using the exact name. i.e. c:\WINDOWS\system32\drivers\fidbox.dat If whichever software is creating that file doesn't complain and doesn't delete that subfolder and replace it with a file, it'll never eat the disk space again. |
#6
|
|||
|
|||
Gradual out of disk space - fidbox.dat
On Tuesday, 3 January 2017 23:08:32 UTC+8, Ron Hardin wrote:
In case anybody didn't know about it, there's a remnant from some popular virus scanner that gives you a growing file that eventually gets big enough to matter. c:WINDOWS/system32/drivers/fidbox.dat It's harmless to delete (and will grow again over a period of months) but you have to be in safe mode. A smaller one c:WINDOWS/system32/drivers/fidbox.idx can be deleted at the same time. The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them. -- On the internet, nobody knows you're a jerk. |
Thread Tools | |
Display Modes | |
|
|