VoodooShield/Cyberlock

Cool, thank you MrGump!

 

My pleasure, Dan, my pleasure...

 

Hi Dan.

Here is the quick video.Silent block.
https://www.youtube.com/watch?v=qxWch5sBtd0&feature=youtu.be

Regards,
Plamen.

 

Hmmm, very interesting. I tried to reproduce this behavior with IE 11, and downloaded filezilla from SF to my downloads folder, then tried to run it, but VS blocked it. I have an idea of what might be going on here... I will take a look at it tonight. BTW, what browser are you using in the video? Thank you!

 

To me it looks like Waterfox? https://www.waterfoxproject.org/

 

VS 2.10 working very well here Dano!

 

2.10 is logging more to the user log than 2.07, but it's still not logging many of the applications executed on my machine. For example: Auslogics disk defrag, VLC Player, Media Player Classic, Keepass, etc.. The list would be very large if I named them all.

 

Cool, thank you TH!

 

Same here and I sent you the logs Dan!

Daniel

 

TH and I have the opposite problem, it is logging duplicates for us. I will look at it, it should be super easy to fix, thank you!

 

Kwel!

 

Cyberfox
https://8pecxstudios.com/cyberfox-web-browser

Regards,
Plamen.

 

Cool, thank you, I will look at that issue and the logging issues this weekend!

 

I never thought I would say this, but I finally released VS 2.11 and updated the website . Thank you everyone for all of your help!!!

Please download the release version from here, that way it will auto update correctly in the future! If anyone experiences any weird bugs with the website or anything, please let me know!


http://voodooshield.com/download/versions/Install VoodooShield.2.11.exe

 

I'm experiencing that bug as well. VS is logging multiple entries of almost everything. Searchfilterhost.exe, route.exe, searchprotocolhost.exe, mscorsvw.exe, etc.. mscorsvw.exe is being logged 7 times for a single execution. It appears that way anyway. They all have the same time stamp.

 

Hi Dan

That won't work. The idea is to block it so training will not achieve that. I am running it from another partition and is also set to run in Sandboxie where "Launcher.exe" is set as the forced program.

On logs I notice that I am also getting multiple entries with 2.10

 

Hi Dan

Funny thing happened when I switched on my PC this evening (5 minutes ago). Got a popup saying that there was a new version of VS available and gave me the option to download/install the update...which I said 'Yes' to ...only to be told that it was a 16 bit version and was not compatible with the 64bit OS......but I have since gotten 2.11 from this thread installed and running nicely...

But you may want to look at the check update function

Have a great weekend.

Regards, Baldrick

 

Cool, I took that out for now in 2.11... I really needed to release 2.0, but it should be an easy fix. I will go through all of the logging and make sure everything is working correctly. Thank you!

 

Ohhhh, I gotcha. I think I know what is going on here, let me see what I can do. Thank you!

 

Hehehe, I was afraid something like that might happen to some of the users running the beta version. I could try to fix it, but the best thing to do is just to download it from voodooshield.com, and everyone will be good to go. Thank you!

http://voodooshield.com/download/versions/Install VoodooShield.2.11.exe

 

Hi Dan, I have downloaded the 2.11 version about a couple of hours ago...I am assuming that in the interim you have made no changes that would necessitate a redownload and reinstall?

 

Exactly. I will post any changes on here, and from now on, VS will notify you if there is an update as well. I disabled the auto update in all of the beta versions because otherwise it would have been very confusing for everyone involved .

 

Cool, but it will be great as and when the update feature fully works...but one thing at a time, eh?

 

It actually should be working right now. If you restart VS 2.11 and it does not prompt you to update, then it is working . The reason the beta gave you that error message is because I never updated the VSUP.exe that is in the c:\Program Files\VoodooShield folder (for the beta version), and that was pointing to the wrong place. But now, since the VSUP.exe for 2.11 is updated, it will point to 2.12 when it comes out.

 

Hi Dan, thanks for the explanation...can confirm that 2.11 installed on both 32bit & 64bit did not prompt for the update...roll on v2.12...

You is almost there...whey hey!