-
Bitdefender Isos (rescuecd & Linuxdefender)
I have a few old BitDefender-related ISO files sitting on my hard drive. The files are: BitDefenderRescueCD_v1.6.2-4.iso LinuxDefender_Live!_v1.5.6_CeBIT.iso LinuxDefender_Security_v1.0.iso If I recall, they were for recovery when the workstation could not be booted due to virus. Have these now been superseded by…
-
False Positives - srvany.exe & instsrv.exe
The following two modules are (once again) being detected as containing viruses/malware. A few months back, these were getting detected, then the detection of them as viruses/malware seemed to stop. They started getting detected again during the full and deep system scans I ran this past weekend (2 June). They were not…
-
Possible Bug - AntiRootKit Scans Not Recorded in Events
While looking into what I thought was a problem with the event list (it wasn't), I noticed what may be a bug in the recent updates. Previously, if the "Scan for Rootkits" task was run, an entry was made in the Events list and the value under the Source column was "Antirootkit". Now when I run the same task, it no longer…
-
Have Some Event Types Been Pruned?
Have any of the recent updates pruned some of the event types which usually show in the Events list? I noticed that my event list seemed awfully small all of a sudden, and when I clicked on the "Select Event Source:" drop-down, the only items in the list were: All Antirootkit Update In the past, I thought there has been…
-
(Some) Scheduled Tasks Stop Running
I noticed a few days ago that the problem with the scheduler being an hour off appears to have been fixed again. It must have occurred with a recent program update since the update which created the 247 build. The problem I seem to run into now is that tasks in the scheduler will work fine for a while, then some tasks will…
-
Trojan.Starter.GY - False Positive?
Another possible false positive. My recent "Full System Scan" has suddenly started detecting Trojan.Starter.GY on two system files. The files are: C:\i386\utilman.exe c:\windows\system32\utilman.exe In contrast to my post in the Trojan.Starter.IM thread, in this case the detection is only occurring on my WinXP Home Edition…
