VoodooShield/Cyberlock

Hey, the new version is running great here, no crashes so far! It did freeze upon upgrading and told me I had to register again, but then it unfroze and was registered. So not sure there.

Can you take a look at the Nvidia profiles that are downloaded by the Geforce Experience program that comes with the drivers? Each time I install a new game and the program grabs the profiles for it, VoodooAi thinks it is a virus and I have to allow it, sometimes even allowing it as a false positive. It also has flagged various other files and functions by the drivers as unsafe.

 

v 323
there was a chrome update (stable), and voodoo didn't know how to handle it.
It did not know at all whether it was a valid process or not.
after clicking for more info and then more info, I did find it mentioned that it was signed by google.
okay, so then voodoo should know it is legit...

 

Chrome auto-updated here while my machines were idle - no problem.

 

Didn't the Voodooshield prompt showed the digital signature?

 

installed v 3.23 on top on v 3.22 without any problems Dan , download took a little longer this time ( approx 10 seconds or so ) will see how this build runs on my machine thanks for all the efforts you are putting in your product!!

 

I did a clean reinstall of SUPERAnti-Spyware from E drive to D drive and VS didn't even react? Interesting also I have Custom Folders allowed for



[06-02-2016 08:29:01] [DEBUG] - SRD::HP: ctx=24, proccess: id = 7436, name=SUPERAntiSpywareProv6.0.1220.exe, path=E:\Security Programs Folder\SUPERAntiSpyware Folder\SUPERAntiSpywareProv6.0.1220.exe, cmd="E:\Security Programs Folder\SUPERAntiSpyware Folder\SUPERAntiSpywareProv6.0.1220.exe" /runasadmin , parent pid=2252, parent process=SUPERAntiSpywareProv6.0.1220.exe
[06-02-2016 08:29:01] [DEBUG] - superantispywareprov6.0.1220.exe (7436) AllowReason: 0x0103
[06-02-2016 08:29:01] [DEBUG] - SRD::HP: ctx=24, allow = True (00:00:00.0058562)
[06-02-2016 08:29:20] [DEBUG] - SRD::HP: ctx=31, proccess: id = 6868, name=SASCore64.exe, path=D:\Program Files\SUPERAntiSpyware\SASCORE64.EXE, cmd="D:\Program Files\SUPERAntiSpyware\SASCORE64.EXE" -install -name:!SASCORE -display:"SAS Core Service" -description:"SUPERAntiSpyware Core Service" -pipe:sascoreservicepipe, parent pid=7436, parent process=SUPERAntiSpywareProv6.0.1220.exe
[06-02-2016 08:29:20] [DEBUG] - sascore64.exe (686 AllowReason: 0x0103
[06-02-2016 08:29:20] [DEBUG] - SRD::HP: ctx=31, allow = True (00:00:00.0064900)
[06-02-2016 08:29:20] [DEBUG] - SRD::HP: ctx=33, proccess: id = 512, name=SASCore64.exe, path=D:\Program Files\SUPERAntiSpyware\SASCORE64.EXE, cmd="D:\Program Files\SUPERAntiSpyware\SASCORE64.EXE", parent pid=784, parent process=services.exe
[06-02-2016 08:29:20] [DEBUG] - sascore64.exe (512) AllowReason: 0x0103
[06-02-2016 08:29:20] [DEBUG] - SRD::HP: ctx=33, allow = True (00:00:00.0049637)
[06-02-2016 08:29:40] [DEBUG] - SRD::HP: ctx=38, proccess: id = 5612, name=SUPERAntiSpyware.exe, path=D:\Program Files\SUPERAntiSpyware\SUPERAntiSpyware.exe, cmd="D:\Program Files\SUPERAntiSpyware\SUPERAntiSpyware.exe" /autoregister:2221011366 , parent pid=2252, parent process=SUPERAntiSpywareProv6.0.1220.exe
[06-02-2016 08:29:40] [INFO ] - Allowed: superantispyware.exe, d:\program files\superantispyware\superantispyware.exe, ff266c36040f90e2ad21cd74fcfbb85c82d62429a5efd94e8e44afb9da5d9c32
[06-02-2016 08:29:40] [DEBUG] - SRD::HP: ctx=38, allow = True (00:00:00.2763943)
[06-02-2016 08:29:40] [DEBUG] - SRD::HP: ctx=39, proccess: id = 6328, name=SSUpdate64.exe, path=D:\Program Files\SUPERAntiSpyware\SSUPDATE64.EXE, cmd="D:\Program Files\SUPERAntiSpyware\SSUPDATE64.EXE" *6.0.1220!{0D3C4F0D-1C11-47bc-AD1C-BAB98712DBFB}, parent pid=5612, parent process=SUPERAntiSpyware.exe
[06-02-2016 08:29:40] [DEBUG] - ssupdate64.exe (632 AllowReason: 0x0103
[06-02-2016 08:29:40] [DEBUG] - SRD::HP: ctx=39, allow = True (00:00:00.0066591)

Daniel

 

Thanks Dan, it was a good test for the freezing issues with VoodooShield and based on your advice I will try another one from this list:
listoffreeware.com/list-of-best-free-keyboard-status-indicator-software/
I went with TrayStatus

 

Dan, VS is still freezing. I opened Chrome and VS blocked Software Reporter Tool. I allowed it and a few minutes later VS Froze.




I will email you the logs.

 

Just had v323 hang. I went to install Unhackme and forgot to stop VS. Instantly hung VS rather than give me a notification. I had to kill VS to exit it.

Logs sent.

UPDATE: Just had VS freeze again. This time it was in install mode updating Flash Player.

Win7 64, EAM, no other security progs running.

 

See Dan, not just Software Reporter Tool.

 

Dan - I have 3.23 freeze on me yesterday. I was having problems sending emails and went to put it into training when if froze. No logs since I restored an image to get over other unrelated problems

 

Version 3.23 froze right after I closed sandboxied Chrome. It took longer than usual to delete sandbox contents, when I checked VS, it was frozen. Sent logs to VS support.
Edit - VS was in Smart mode at the time...

 

No freezes or any major problems here. Once, last night (Thurs), I shut down Firefox and the shield disappeared. Restarted FF and nothing. Checked Task Manager and no VS showing. I just clicked the desktop icon and restarted Voodooshield. No problems since.

 

Not sure, but depending on VS settings, install might get blocked depending on where the download was dropped and where it tried to install from. I sometimes find "issues" even when I put VS into install mode, and I typically will exit VS for an installation. voodoo_dan will hopefully correct me if I'm wrong.

 

Hello. I'd like to that product will also protect the Windows registry.
Best regards.

 

Hi,

I had some PM's discussion with Dan about the defaults of the free version (since you can not change the settings in the free version). For instance the suggestion of @yesnoo to set AI sensitivity at 90 could be one of the changes in default settings. This simple AI-sensitivity setting change would solve most of your issues.

The goal is to make the free version monkey proof (not requiring any input of the user). Reason to do so is obvious: when new version goes live, Dan does not have the resources to provide support on the free version (which is fair, since he does not get any money for it either). Also the concept of white listing using AI is relatively new, so defaults has to take that into account also to make the benefits of this concept available to the big audience.

Dan will probably come back on this topic after V3 is working perfect. I can imagine Dan is focusing on solving the freeze issues first, so please have some patience.

Regards Kees


So

 

Dan v 3.23 froze for the first time on my machine today. for the rest no problems to report , runs smooth. no slowdows whatsoever.

 

I have been running VS for the last 10 days (3.22 and now 3.23) on autopilot.
VS (3.23) froze for the first time while uninstalling Opera developer. I reinstalled and uninstalled twice again but the problem did not reproduce itself.
Relevant software:
Windows 10
Webroot SA Antivirus
Cryptoprevent - with default set and forget settings
VoodooShield - autopilot
Malwarebytes anti exploit
Adguard full version
I also have a giveaway version of Shadowdefender, and Sandboxie installed but rarely use them, but played around with them both on VS 3.23 installing and uninstalling various software without a problem.

 

Thank you for letting me know stapp! I will fix that right away, then I will post a special debug version of VS that will hopefully display a message box when VS freezes, to tell us what is causing the issue.

I am completely buried right now, but I will catch up on the posts I missed asap, have a great weekend, thank you!

 

I have windows 10 (x64) running Voodooshield 3.23, after reboot I keep getting unable to connect to voodooshield service. I uninstall, delete program data folder, Voodooshield reinstalls fine, runs fine, after reboot the problem returns.

 

VS froze again. I tried ejecting my sat nav from from machine while I had Cyberfox open and VS prompted for a Command Line, which I allowed. As usual, VS froze not long after.

As the logs aren't showing anything I won't bother sending them this time and will wait and see what your new version shows, if anything.

 

I will catch up on the other posts asap... but I needed to respond to this one right away.

What other security software are you running? I have been told that some other AV's are quarantining some of VS's components... mainly Trend Micro so far.

 

For anyone who is still having the freeze issue, I think the fastest way to get to the bottom of it is this...

I believe VS started freezing on version 3.09, because I found an old email that I sent Vlad, telling him that 3.09 froze.

If anyone who is having the freeze issue can install VS 3.08 for a few days to see if it freezes, then we will know what changes caused the issue. Krusty and I have been talking about the freeze issue for quite some time through email, and I think we have it narrowed down. Once we know for sure that it was changes from 3.08 to 3.09 that caused the issue, I will see if Vlad has the time to take a quick peek to see if he can figure out why it is happening. I think it has to do with the wildcard / regex code, which Vlad is extremely familiar with because he wrote pretty much all of that code.

So, anyone having the freeze issue, please try VS 3.08 for a few days and let me know how it goes. Thank you!

Here is the old version of 3.08:

www.voodooshield.com/Download/beta3/InstallVoodooShield_3_08.exe

 

Ok did a clean install of version 3.08. Disabled the notify for new version otherwise you keep getting prompted for version 3.10. I let you know if there are any problems.