VoodooShield/Cyberlock

Thank you. But not available in free version

 

Contact dan@voodooshield.com and he will set you up with a pro sub! And I don't know how along he will be offering this and I will contact him and ask him to post some info.

Thanks,

Daniel

 

Ok Dan - I have found a solution but don't understand it.

When I start Windows and once it has fully loaded with start ups, I then manually load The Bat, Opera 12.17, Otter. In this formation Otter is blocked by VS. If I reboot and once loaded start Otter it opens correctly. I can then open the others without any problems. Just wondering if VS is not seeing Otter initially. Will have to reboot to find out.

 

To update this is as I suspected at the end. VS is not seeing it until some other web facing prog is started. I have now added Otter to VS so now it again blocks. I have trained it again but still after a reboot it is blocked.

Otter is running in Sandboxie which is probably causing the problem. I have tried running it outside SB and it then works correctly. But if I close Otter and restart it normally in SB then it goes through unchallended.

All a bit too weird for me.

I am running Win 8.1/64

 

Thanks Dan.

Version 2.30 is running smooth so far.

 

I purchased VS previously but decided for some reason not to use it. I have just re-installed it (Version2.30) and I LOVE it. I must have had a mental lapse before - lol. I am recommending it to my family - as most of them need something like VS to help them. It's running great for me on Windows 8.1 x64 with virtually NO pc load. Just wanted to say thanks Dan & VS!

 

Hey everyone, I will reply to the above posts a little later. I was a very productive weekend, and I added a lot of new stuff. And I also installed the new version of Visual Studio 2013 Ultimate, and it found almost 200 "bugs", although most were just optimizations. I have all but 16 fixed . I will fix the other 16 this week, but seriously, they are no big deal at all. But, there were A LOT of changes under the hood, so please let me know if VS does something odd.

Here is what I added:

- Fixed the targeted VoodooShield bypass (Basically just added self protection). I was always reluctant to add self protection in case something went wrong, but I figured out how to do it, and still allow the user to kill VS in the Task Manager if necessary. I am going to have to add another self protection mechanism as well, I will do that soon.

- Changed a few things in Settings

- Added a prompt 3 weeks after installation that asks the user if they would like to disable auto allow. You can move your clock forward 3-4 weeks and you should be able to test this prompt.

- Put the close X back in the User Prompt for TH

- Put the Allow False Positive link back in the User Prompt. You can still turn the button on in Settings / advanced so you can have the full button if you like. CET will like this .

- VS is now 100% Windows 10 compatible (build 9926 and above)

- I also found new places in the registry to obtain a really great snapshot, wait until you see it in action! It is a combination of a couple of different things, but basically adds your recent / frequently used programs to the snapshot. I added the Take Snapshot right click option in full time so users can easily access this feature. Or you can reset your snapshot, or click on the Automatically allow all software from the Program Files folder option in settings to access this feature. Please keep in mind during testing... if you add the Extended Whitelist items, there is a HECK of a chance that any executables you are using to test will be automatically whitelisted. So for example, if you have a folder on your desktop with malware in it, and you use this new option, VS will whitelist the malware. But there is a prompt that addresses this issue... basically it asks if this is a new / clean computer, or one that has been recently infected. If the user clicks NO, then the standard snapshot is taken, and not the extended. Also, the extended snapshot is not currently set to add the new items to the user log, but it does add them to the snapshot. We can go either way on this, but I would prefer to just add them to the whitelist, but please let me know if you guys think we should log them in the user log as well. To me, the user log... well, is the user log and logs how the user interacts with VS. But we can go either way, just let me know what you guys think!

- Also, I am trying something new. There are a handful of troublesome windows processes, for example, dismhost.exe that would be blocked when Windows Disk Cleanup was started. I am going to specifically (and safely) whitelist these processes, basically hardwire them in like we do the standard command lines. So if anyone has a windows process that seems to be blocked all the time for no reason, please let me know. This is assuming that you have the auto allow specific critical windows processes enabled. Otherwsise, I cannot list them all .

- Fixed close to 200 "bugs" from Visual Studio Code Analysis... almost all were optimizations and security fixes

I meant to work on the change log for 2.30 and the instruction manual this weekend and today, but I kinda got carried away with adding new stuff. There are other small new features and optimizations as well.

Anyway, since there were so many changes, please let me know if I broke anything! Thank you!

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.31 beta.exe

 

Hi Dan,

That's awesome news! . I'm just downloading the newest beta and will install it in a few seconds.
And of course I will share my thoughts in a short time .

Thanks,

Mike

 

BTW, it is kinda acting a little funny on my XP machine, but it should work great on everything else. I normally do not test as heavily with XP as I do the others, but I will try to see why it is acting a little funny.

 

Awesome to hear Dan, we will let you know if we see any issues!

Daniel

 

As I said the last time I posted in this thread, I haven't been running the last few betas of VS because I was having a BSOD problem with another software...But, that seems to have been resolved, now.

But, I am starting to feel like the orphan with my XP system...

 

Hi guys,

Did you see any issues after installation?
All I can see is:

"VoodooShield is not able to connect to the VoodooShieldService, please reboot your computer to start VoodooShield
If you continue to see this error, please uninstall, reboot, and reinstall VoodooShield to resolve this issue".

I've rebooted, reinstalled and nothing... Still can't start new beta working...

Any ideas?

Mike

 

Sorry, please try it again, both issues should be fixed. Sorry about that! BTW, VS's settings might take a second or two to load after it first starts. I had a fix for that, but it was messing other stuff up, so I am trying something else.

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.31 beta.exe

 

Hi Dan,

It works!.
I've deleated VoodooShield folder from ProgramData and also made brand new rules for VS in SpyShelter Firewall (I'm not sure, but maybe there was some conflict with these older ones made by me for earlier VS versions). Now it cooperates both with Webroot and SpyShelter as an efective security combination.
In a short conclusion - the newest beta v2.31 looks great now, working perfectly si far and I simply have no issues to report.

Great job Dan - many thanks and big congrtas for everything!.

Mike

 

2.31beta stutter a lot when first launching. love the new options!

win 764bit has stutter

not so much issue on Wndiows 8.1

 

Suggestion:

Would be nice to have the option to allow when obvious FP's occurs, in this case using 2.30 i've had this FP several times in the last 24 hours, was it not Rising AV the last time this file was wrongly detected?

 

If you are using the Pro version, in advanced settings the bottom option, (which I believe is disabled by default) .........

'Show allow button for false positives if a threat is detected'.

 

Sir Percy, new beta 2.31 has this option (to allow FP)....

 

ghodgson & siketa, thank you both.

I did check the settings and despite this completely overlooked the 'Show allow button for false positives if a threat is detected' option!

 

Nice review here.....

https://www.youtube.com/watch?v=doxC5VYJ6b8

 

You can watch it here too.

https://voodooshield.com/

 

Oh, Okay, didn't realise :-D

 

2.31b
<<I went to a questionable or unknown website and VoodooShield keeps flashing. What do I do?
Most likely VoodooShield is killing a virus. We highly recommend that you do not visit that site.>>
What does 'killing a virus' mean ?

 

I'll have a stab, bjm. I think it means that VS is stopping a "virus", or more correctly malware, from executing on your system.

 

Hey, I will reply to the posts I missed tomorrow or this weekend. In the meantime, please try this beta, it is running incredibly smooth. There were another 245 errors / optimizations that I found, and pretty much all are fixed now. They really were not bugs, just little things to optimize the code, but I really think it made a difference! Thank you!

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.31b beta.exe