VoodooShield/Cyberlock

Hi polly77, nice to meet you! If you need a VS Pro license, please let me know... just pm me the email address you want to use for your account.

I just tried OkayFreedom and it worked perfectly for me, both Automatic and ON (I think that is what they were called), worked great. Then I switched to OFF and it worked as well... and I tested my public ip each time, and it worked as expected. Are you a new VS user? Are you running any other security software that blocks internet requests? I also noticed that OkayFreedom updated itself right after I installed it, so you might want to check for an update. The only other thing that I can think of off the top of my head is that you should maybe uninstall OkayFreedom, then reinstall it with VS in Training Mode, and leave VS in Training mode until OkayFreedom is up and running correctly. I only mention this because OkayFreedom seemed to have a lot of command lines. If that does not work, let me know and I will see what else we can try, thank you!

 

hey Dan, just a little request about Voodooshield
can we have the option to specify the installation directory of the product? and what is the approximate installation size of Voodooshield?

thanks

 

Anytime man! anytime. Thank you

 

@VoodooShield
Hey Dan, what about making some limitation to use VooDooShield for free without the Friday nag screen?
For example, when you first run VS, if you choose "AutoPilot Mode", you don't get any Friday nag screen (you can keep the setting nag screen).
If you choose "Application Whitelisting Mode", you get a popup saying something like "you'll get a nag screen on Friday. To remove it, please purchase a PRO license".
Of course, if at a later time you decide to switch from "AutoPilot Mode" to "Application Whitelisting Mode", you'll get the same popup and the Friday nag screen can't be removed even if you switch back to "AutoPilot Mode" (unless you uninstall VS and then reinstall it).
So, basically:
- BASIC: "AutoPilot Mode" only (without option to modify the settings, but also without Friday nag screen)
- FREE: "AutoPilot Mode" or "Application Whitelisting Mode" (without option to modify the settings, but with Friday nag screen)
- PRO: "AutoPilot Mode" or "Application Whitelisting Mode" (with option to modify the settings and without Friday nag screen)

 

3.59 Final

https://voodooshield.com/Download/InstallVoodooShield.exe

 

Thank you Dan for give me a chance to test and use this great program. And I am sure we all do.

 

Dan, I get the same hash as you.
My region format is English (United States).
But my system locale (this affects non-unicode fonts) is Hebrew (Israel).
Maybe that is the problem here?

 

No problems with 3.59 so far. Upgraded yesterday.

 

Installed 3.59 over the top of 3.58 yesterday, all working fine so far. Thanks Dan.

 

Hi Dan

Hope that you are well?

v3.59 installed over the top of previous version under 32 & 64 bit OS...been working fine since installation early yesterday.

Great job! Would say that this is prime time.

Regards, Baldrick

 

v3.59 working fine here. thanks

 

Same here. Updated to v3.59. Running great!

Thank you

 

After the installation of v3.59, i can see that all folders at the right side of Custom Folders are now selected

 

[QUOTE="shmu26, post: 2672074, member: 146836"
But my system locale (this affects non-unicode fonts) is Hebrew (Israel).
Maybe that is the problem here?[/QUOTE]
Nope, that isn't it. I reset system locale to US English, and same behavior. VS doesn't see the digital sig.

 

v3.59 works fine on Windows 10 x64 (Creators Update).

 

Can be VS registered as an AV in windows 10? Is an option at all?

I am planning to run Zemana and VS only with WFC

 

@VoodooShield
Nothing detrimental to report with 3.59, smooth on 3 installs Win 7, 8.1 &10.
Alongside Eset AV/Comodo Firewall

 

You can't make Windows recognize VS, or Zemana, as an AV.
But you permanently disable Windows Defender with a registry hack or in group policy.

And you can turn off the Windows warning that no AV is running, see screenshot

 

I would not recommend putting VS in Action/Security Center it's a pain as is for some.

 

100% Agree

 

Got 3.59 via Majorgeeks, all good.

 

Hi, I wasn't actually recommending that, and in fact, I don't even know how to do it.
I was rather recommending that @guest rid his system of annoying Windows intrusions, namely:
1 Windows Defender activating itself automatically
2 Windows nagging about the lack of an AV

 

Agreed!

 

Browsing Kaspersky Total Security (KTS) logs, I located this...

Suspicious action was blocked VoodooShield
Action: Read memory from other processes
Application: VoodooShield
Application path: C:\Program Files\VoodooShield\VoodooShieldService.exe

Is this a concern? Is it OK that KTS does this, or should I find a way to exclude this action?

 

3.59 running well.

I would add both Voodooshield.exe and Voodooshieldservice.exe to the Trusted/Exclusions in KTS. No need for KTS to interfere with Voodoo tbh.