on feb 2, everything will work right... right, I figured that out, but you can be sure some new users won't know that, and if they are on the free version, well...
Real quick... Evjl's Rain, this is not true, the parent process feature does not apply to scripts, since most people do not need to run scripts and since a lot of ransomware utilize scripts. https://malwaretips.com/threads/voodooshield-discussion.63827/page-5#post-590515 You can test it with this script. www.voodooshield.com/artwork/test.js Guys... please test before you guess.
Actually TH, I've thrown almost 225 malware samples of all types at VS, and it has stopped it all. Even the Petya class of Ransomware. Awesome job Dan.
Hi boredog - Sorry for the delay in replying, I often work from can't-see to can't-see but it's remunerative Anyway, moving the shield ain't the answer, sorry. The alerts still show up at bottom right of screen. Good for some, but...
I think people shouldn't be surprised at this given what VS is designed to do. If it's not in the whitelist, has a high number of VT detections, has an unsafe AI score or a combination of those, of course the sample is going to fail to run.
If I run VoodooShield together with Emsisoft Anti-Malware, do you guys advice anything else? How about HitmanPro.Alert? Is the combination of VS/EAM/HMPA stable and not a hog on performance?
Right now, I'm more concerned with VAi detecting safe applications as "unsafe", rather than having it strong detection against malware. Maybe VAi is too strong or stringent in its decision making that it also flags some safe programs as unsafe. I'll be ecstatic if VAi is fine-tuned to detect safe programs properly.
Hi XhenEd On my desktop, VS is quiet as a church mouse. On my VM it's quiet until I run Malware. Then it talks.
I'm new to VS. Since using it on Dec. 30 2016 till date, I agree with Peter. VS is silent as a church mouse. Besides it works fine along my sec setup.
But with no-so-popular safe programs, it also talks. Yes, I agree though that VS is silent most of the time.
I find that it talks a lot about program and driver updates. If I am not mistaken, this happens when the update file is created in a location such as appdata/local/temp. This behavior is understandable, since a file was dropped in a suspicious location, so Ai wants to check it out.
Exactly. And this is normal and expected behavior as Ai needs to learn about the file in question. Once it has learned it becomes silent. I like VS a lot.
I think when I mentioned I had VS set to paranoid, dan asked me to set back to balanced because Ai is still learning at the present time. that tells me it is still auto self tuning as we speak.
Update, Voodoo Shield working like a charm here along with Sandboxie. Not running an A/V program and only use MBAM 2.0 for on demand scans.
I thought about trying VoodooShield until I saw in the EULA: "You agree that VoodooSoft may collect and use personally identifiable, technical and related information, not limited to technical information about your computer, system and application software that is gathered periodically and automatically to facilitate and improve upon the provision of the Software, Software updates, support and other services to you." No one else has any concerns about this collection of personally identifiable information? Is there a reason it can't be anonymized and still serve its purpose?
Nope, not worried about Dan mis-using our information. Sounds like it will only be used to improve VS and not be sold to 3rd parties. Dan will comment on this.
I am using VS with Windows Defender, Heimdal Pro and Adguard for Windows - everything works like a charm.
What difference is this compared to literally any other program that can read your registries and log the PC/hardware information? There's a difference between having your browsing history logged and having easily accessible registry keys accessed/logged.
I agree but it needs some sort of privacy statement on what information is collected. I did not like seeing the file names for every video I watched or every folder I unzipped in the logs. Okay so it's easily fixed by editing command lines but still a privacy issue if the data is collected but not anonymized.