Calendar of Updates

Official Support Forums => VoodooShield => Topic started by: hayc59 on August 21, 2017, 06:49:52 am

Title: VoodooShield v4 Beta Discussion
Post by: hayc59 on August 21, 2017, 06:49:52 am
Any sign of the man??  8)
Title: Re: Ok Dan...4.0 Lets roll
Post by: Baldrick on August 21, 2017, 10:44:50 pm
Well, I for one hopes that he turns up soon amongst users who appreciate his genius & efforts to provide one of a kind security apps.  :)

Baldrick
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on August 25, 2017, 11:22:09 pm
Apparently,after what ever took place at wilders he has been posting a forum called MT
he needs to get his rear end here and post some info on version four!!
Title: Re: Ok Dan...4.0 Lets roll
Post by: Baldrick on August 26, 2017, 02:37:40 pm
Apparently,after what ever took place at wilders he has been posting a forum called MT
he needs to get his rear end here and post some info on version four!!
Indded...and pesonally I would not go near MT as a place of permenant residence. The discussion are purile and as and when the residents set against one there is nothing that can be done...they all think that they know one better than the other...but I digress.

Hopefully he will heed the advice.  ;)
Title: Re: Ok Dan...4.0 Lets roll
Post by: Triple Helix on August 26, 2017, 04:31:49 pm
I'm still waiting for a reply from VoodooShield Dan to see if we can get this going here again!
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on August 26, 2017, 04:58:32 pm
I'm still waiting for a reply from VoodooShield Dan to see if we can get this going here again!
Thank you Danny..I have e-mailed him and can you see your pm please
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 03, 2017, 04:08:04 pm
Apparently,after what ever took place at wilders he has been posting a forum called MT
he needs to get his rear end here and post some info on version four!!
Indded...and pesonally I would not go near MT as a place of permenant residence. The discussion are purile and as and when the residents set against one there is nothing that can be done...they all think that they know one better than the other...but I digress.

Hopefully he will heed the advice.  ;)
I should have listened to you guys ;).  It is time that everyone hears the truth.  I will send my full response to the mods on here, and if they approve of everything, then we will post it.

Here is a short summary of the MT incident...

The incident at MT all started because Lockdown posted “SEP suxx” (Symantec Endpoint Protection).  This is completely unprofessional and how this kind of thing is allowed at MT is beyond me.

Then Umbra falsely accused me of “using another account”.  Umbra knows full well that planting a seed like this is exactly how rumors get started, and months later, they become “fact”.  So I simply pointed out that for years now, Umbra and his buddies have been harassing and messing with me, and that try as they might, they almost always end up losing where it really counts… in the polls.  If this is the kind of thing that is allowed at MT, then I want nothing to do with it.

Then Umbra has the nerve to post "Yes of course; the few members discussing on this thread at that time witnessed all of it."  Umbra is acting like he has no idea why I was upset.  Well, when you falsely accuse someone of dirty tricks, they are going to be upset... especially when I have NEVER pulled a dirty trick, and Umbra does it constantly.  If you ask me, Umbra should be banned for propagating rumors... especially since he has admitted to me that he works as an agent for a competitor.

Also, I found out that the "Private" conversations at MT are not exactly private.  That being the case, I have no problem with releasing some interesting private conversations, if the COU mods approve.  When I discovered that the conversations are not actually private, I knew I would not be sticking around MT long.

If I cannot release them on here, then I will find a place.  Either way, the truth is going to be revealed once and for all.
Title: Re: Ok Dan...4.0 Lets roll
Post by: bootmgfw.efi on December 03, 2017, 04:57:20 pm
If I cannot release them on here, then I will find a place.  Either way, the truth is going to be revealed once and for all.
You could always just drop the motivation to sabotage and simply provide support for your project. People who use VoodooShield care about support for the software, not about the mess you got yourself into.

Instead of taking your bans on other forums negatively, migrating to another forum to do the exact same thing that got you banned in the first place, forget about what happened and move on with your life.

If you keep behaving like this then you will bury your project into the ground even further than you already have and get another forum ban - you have an opportunity to resolve things by putting an end to referencing other individuals positioned at other forums negatively and working more on your project than talking, but the path you take must be your own decision. If the moderators here care about their forum and their reputation they will ban you here for trying to cause drama.

I wish you all the best with your software and I will be very disappointed if I check back in here 2 weeks from now to find you took the unnecessary, useless path for drama.
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 03, 2017, 05:24:01 pm
If I cannot release them on here, then I will find a place.  Either way, the truth is going to be revealed once and for all.
You could always just drop the motivation to sabotage and simply provide support for your project. People who use VoodooShield care about support for the software, not about the mess you got yourself into.

Instead of taking your bans on other forums negatively, migrating to another forum to do the exact same thing that got you banned in the first place, forget about what happened and move on with your life.

If you keep behaving like this then you will bury your project into the ground even further than you already have and get another forum ban - you have an opportunity to resolve things by putting an end to referencing other individuals positioned at other forums negatively and working more on your project than talking, but the path you take must be your own decision. If the moderators here care about their forum and their reputation they will ban you here for trying to cause drama.

I wish you all the best with your software and I will be very disappointed if I check back in here 2 weeks from now to find you took the unnecessary, useless path for drama.
Great advice... thank you.  Although I do not believe that I got myself into a mess... I stood up for myself.  I am not trying to cause drama... I just believe that users are entitled to the truth.

I certainly agree that the conversation should be kept to support for VS, and as long as no one else creates any drama, I will be sure to do the same.

BTW, when I mentioned that VS's direction is "up in the air", this is not a bad thing at all.  I am just trying to choose the absolute best path for VS.
Title: Re: Ok Dan...4.0 Lets roll
Post by: Triple Helix on December 03, 2017, 05:47:25 pm
@VoodooShield feel free to say what you like as you had enough from the other two forums! But if Trolls just want to come here it's best if they not as they will be Banned but it's time to have professional VS discussions on any topic from testing, to learning more about VS as I have been using VS before v1 came out!

Daniel
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 03, 2017, 08:42:04 pm
Here Here Daniel! Its a great program and welcome back home Voodoo Dan let (as the late great Marvin Gaye..said lets get it on)
Title: Re: Ok Dan...4.0 Lets roll
Post by: Jasper The Rasper on December 03, 2017, 09:10:13 pm
Welcome back to CoU VoodooShield.
Title: Re: Ok Dan...4.0 Lets roll
Post by: Gandalf on December 03, 2017, 10:36:48 pm
Hi Dan, I hope we can have discussions about VS here now.
Version 4.12b is rock solid in my opinion.
Any news about translating VS in other languages?
I would like to help with the Dutch translation.
Title: Re: Ok Dan...4.0 Lets roll
Post by: simmerskool on December 03, 2017, 10:59:54 pm
here!
/simmerskool
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 03, 2017, 11:35:46 pm
Gandalf & simmerskool  Welcome :)
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 04, 2017, 12:03:40 am
Here Here Daniel! Its a great program and welcome back home Voodoo Dan let (as the late great Marvin Gaye..said lets get it on)
Very cool, thank you guys!
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 04, 2017, 12:04:50 am
Hi Dan, I hope we can have discussions about VS here now.
Version 4.12b is rock solid in my opinion.
Any news about translating VS in other languages?
I would like to help with the Dutch translation.
Very cool... I hope we will be able to work on language translations in the first half of 2018, thank you!
Title: Re: Ok Dan...4.0 Lets roll
Post by: YoWhatsUp on December 04, 2017, 12:06:39 am
I'm using VS 3.59, does anyone know what the command "/c w32tm.exe /stripchart /computer:time.windows.com /dataonly /samples:1" does? I get it every 1-2 hours, and every time I click allow and then next time it's like I've never gotten it before, same with the dismhosts which I remember dan said will fix for VS 4, also dashlaneplugin.exe and plugins-setup.exe from kaspersky also pop-up every time I open chrome
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 04, 2017, 12:18:38 am
I'm using VS 3.59, does anyone know what the command "/c w32tm.exe /stripchart /computer:time.windows.com /dataonly /samples:1" does? I get it every 1-2 hours, and every time I click allow and then next time it's like I've never gotten it before, same with the dismhosts which I remember dan said will fix for VS 4, also dashlaneplugin.exe and plugins-setup.exe from kaspersky also pop-up every time I open chrome
Here is some info on w32tm.exe...
https://technet.microsoft.com/en-us/library/ff799054%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396
I am not sure why it is not being remembered... does it show up in the VoodooShield Settings / Command Line tab?  If so, is it listed as Allow or Block?  Also, you might try to delete the entry in the Command Lines tab and have VS learn it again the next time it is blocked.

This is probably fixed in VS 4.0, which we will be releasing to the public soon.  Dismhost is fixed in VS 4.0 as well, but if something delays the 4.0 release, I will release a special build of 3.0 to at least fix the dismhost issue.

Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 04, 2017, 01:01:27 am
Shaar, welcome all threads will be reviewed, I edited one word for now its a family forum you know :)
I will say one thing though this forum will alllow and bend but if it turns into a war and payback all post will be removed
and of course bans will happen..I will probably move these to a separate section
Gordon
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 04, 2017, 01:10:38 am
Done and thank you
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 04, 2017, 01:14:18 am
For tech support or further questions on Voodoo Shield  program please start another thread..thank you
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 04, 2017, 01:17:20 am
Maybe my post will be deleted since im not so welcomed here but things must be said and put under the right perspective.


Here is a short summary of the MT incident...
The incident at MT all started because Lockdown posted “SEP suxx” (Symantec Endpoint Protection).  This is completely unprofessional and how this kind of thing is allowed at MT is beyond me.
Maybe for you but it was his opinion, he is free to say it, MT is all about freedom of opinion, aka the "war room".
You just jumped on him like a Vigilante when people like me told you to stay away from interacting with him, bet you couldn't resist; you felt the urge to go on clash with him...


Quote
Then Umbra falsely accused me of “using another account”.  Umbra knows full well that planting a seed like this is exactly how rumors get started, and months later, they become “fact”.  So I simply pointed out that for years now, Umbra and his buddies have been harassing and messing with me, and that try as they might, they almost always end up losing where it really counts… in the polls.  If this is the kind of thing that is allowed at MT, then I want nothing to do with it.
Harass you, come on, i have better to do than that.
Polls, seriously Dan; only you cares of it, i don't care one minute about polls.
Obviously you got banned when you wrote " Aholes", when i saw it, i already knew what may happen... Nobody pushes you to insult people or twisting the meanings of posts, you came on that thread arguing with Jeff and you didn't even care of the OP questions.
wake up! You insult him dude! You knew you and Lockdown were closely watched because of your dramas; that day you just shot yourself on the foot when you insulted him...don't blame others.
My joke came way after the insults, at that point it was already too late for you...
Unfortunately for you,  i wasn't mod anymore, if i was i would delete your posts right away, and  you would be still on MT...


Quote
Then Umbra has the nerve to post "Yes of course; the few members discussing on this thread at that time witnessed all of it."  Umbra is acting like he has no idea why I was upset.  Well, when you falsely accuse someone of dirty tricks, they are going to be upset... especially when I have NEVER pulled a dirty trick, and Umbra does it constantly.  If you ask me, Umbra should be banned for propagating rumors... especially since he has admitted to me that he works as an agent for a competitor.
Agent of What?  because i use a product i'm an agent, you are clearly paranoid, so i was an agent of VS too :p
Honestly you would be still on MT if you behaved properly, i told you last time by PM after the previous dramas on MT and  on wilders countless times; "focus on VS instead of arguing with people", but you never listened to me, you keep going after him ; and now you blame others for you  mistakes...

Quote
I knew I would not be sticking around MT long.
if you didn't insult people or created dramas when something doesn't please you, you would still be on Wilders and MT.


And now you keep going doing the same, you have to prove you are right to the universe when nobody really cares, luckily this time , you are on you buddies forums, so you have free speech.

My advice: Focus on VS instead of people's life. Your customers doesn't care if you are right or wrong, they just care of VS.


Someone knowing you very well  :)

Hopefully , this will be my only post here, i don't have any plan to debate with you or anyone for childish and stupid dramas i don't even care about, but i won't let anyone step on me.

If you have something to say to me you are welcome to PM me

Best Regards
OMG!!!  Umbra, will you ever stop stalking me? 

You know that you admitted that you act as their agent... here is the actual conversation:

Dan: BTW, you better be extremely careful that what you say publicly is true... you and Jeff are best friends and you are acting as an agent of BRN. You can say whatever you want... just make sure that it is true.

Umbra: i know that , my words are always weighted before i talk about AG, if i have a doubt i ask Jeff.

I really hoped you would stop harassing me once you here hired at Emsisoft, but apparently you are going to keep it up.
Title: Re: Ok Dan...4.0 Lets roll
Post by: hayc59 on December 04, 2017, 01:23:09 am
I moved this here until we get some sort of something goin on..I cannot in good faith
go to sleep and see this go sideways... Dan please hold back for now and be a better man
I will ban Shaar in a new york minute if I see him post more bull crap!!
Title: RE:VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 04, 2017, 02:34:01 am
I moved this here until we get some sort of something goin on..I cannot in good faith
go to sleep and see this go sideways... Dan please hold back for now and be a better man
I will ban Shaar in a new york minute if I see him post more bull crap!!

Umbra aka Shaar will be on a very short leash and anyone that's starts arguments and or trolling will be banned without notice!

I will repeat to what I said earlier and that's what's going to happen:

"But if Trolls just want to come here it's best if they not as they will be Banned but it's time to have professional VS discussions on any topic from testing, to learning more about VS as I have been using VS before v1 came out!

Daniel"
Title: Re: Ok Dan...4.0 Lets roll
Post by: VoodooShield on December 04, 2017, 02:52:37 am
I moved this here until we get some sort of something goin on..I cannot in good faith
go to sleep and see this go sideways... Dan please hold back for now and be a better man
I will ban Shaar in a new york minute if I see him post more bull crap!!
Yeah, I think it is important that people see this.  Please do not worry... I will just ignore stuff like this from now on.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 04, 2017, 03:04:01 am
I moved this here until we get some sort of something goin on..I cannot in good faith
go to sleep and see this go sideways... Dan please hold back for now and be a better man
I will ban Shaar in a new york minute if I see him post more bull crap!!
Yeah, I think it is important that people see this.  Please do not worry... I will just ignore stuff like this from now on.  Thank you!
We got you covered so no worries!
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 04, 2017, 04:09:12 am
I moved this here until we get some sort of something goin on..I cannot in good faith
go to sleep and see this go sideways... Dan please hold back for now and be a better man
I will ban Shaar in a new york minute if I see him post more bull crap!!
Yeah, I think it is important that people see this.  Please do not worry... I will just ignore stuff like this from now on.  Thank you!
We got you covered so no worries!

Thank you hayc59, let's hope the dust settles on this matter from here.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 04, 2017, 05:16:27 am
Shaar aka Umbra is now gone and is not welcomed here at all. Trolls will not be Tolerated at COU. Lets carry on with the discussion of VS v4 Beta.

Thanks,

Daniel
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 04, 2017, 01:43:58 pm
Thank you TH... that got old quick, huh?  Just imagine dealing with trolls for years.  You guys were right, I should have come here years ago.
Title: Re: VoodooShield v4 Beta Discussion
Post by: pavo on December 04, 2017, 03:27:47 pm
Ehhhh... Dan.
I had to create account on another forums just to follow VS discussion but VS is worth it :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 04, 2017, 03:43:24 pm
Ehhhh... Dan.
I had to create account on another forums just to follow VS discussion but VS is worth it :)
Thank you, I certainly appreciate that!  I think this forum will be a lot more productive for everyone, and hopefully we can set an example of how forums should operate.

The ironic thing is that most of the bugs are fixed... so there may not be too much to talk about ;).

I will post a link to the next version in the next couple of days... hopefully it will be the last version before the public release.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 04, 2017, 04:49:14 pm
Hello Dan

I am thinking even if you get all the bugs out of VS, there will still be newbies that are still going to need help but am pretty sure now that the word got out you are here, more of the old users will start showing up. Wow Last night I thought this forum was the hardest ever to sign up for but I think it might have been I had a few too many. I saw what you meant about private messages not being private on MT. I went to look at a conversation I was having with a member and noticed it was locked. I am not sure but think only a mod or admin can do that. This morning it was unlocked again.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 04, 2017, 05:15:04 pm
Hello Dan

I am thinking even if you get all the bugs out of VS, there will still be newbies that are still going to need help but am pretty sure now that the word got out you are here, more of the old users will start showing up. Wow Last night I thought this forum was the hardest ever to sign up for but I think it might have been I had a few too many. I saw what you meant about private messages not being private on MT. I went to look at a conversation I was having with a member and noticed it was locked. I am not sure but think only a mod or admin can do that. This morning it was unlocked again.

Very sad that there forum software would allow Admins or Mods to read PM's, the forum software we use here we cannot read PM's and we shouldn't be able to as they are Private Messages.  :o
Title: Re: Ok Dan...4.0 Lets roll
Post by: Baldrick on December 04, 2017, 06:58:22 pm
@VoodooShield feel free to say what you like as you had enough from the other two forums! But if Trolls just want to come here it's best if they not as they will be Banned but it's time to have professional VS discussions on any topic from testing, to learning more about VS as I have been using VS before v1 came out!

Daniel
Well said, Daniel...that is spot on!

Baldrick
Title: Re: VoodooShield v4 Beta Discussion
Post by: DeltaOne on December 04, 2017, 07:37:13 pm
 :) dearest Dan 
Having used VoodooShield on and off for some time, its nice to see u here ,
I looking forward to V 4 public release,
and to see VoodooShield Grow,     

Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 04, 2017, 08:26:19 pm
It looks like I have missed the action.
Hopefully things will be calmer for you here Dan and we can get down to some serious discussions.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 04, 2017, 09:58:32 pm
Hey Dan, follow Triple Helix message on the other forum and I just register here. Gee I am really glad I found you here again. :) :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 04, 2017, 10:08:00 pm
Very cool, it is great to hear from all of you guys, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 04, 2017, 10:45:58 pm
question related to v4.12b & cuckoo on my pc. running win7.  recently uninstalled EAM (very solid, like it) and trying cylance (again).  Cy is fast and light from what I can see.  & cy is not causing any problems that are obvious.  It did quarantine 8 files shortly after install with a "background detection" ie those files were not running, and it seems you don't really tell cy to run a scan, although you can tell it to scan a specific folder, etc.  So... I wanted to check some file with VS/VAi as I think it had a score of 99 but no VT flags!  tried to send the file to cuckoo sandbox via VS and no response from my browser.   ???  Cy has very detailed reports and I'm not seeing that it is blocking some aspect of VS/cuckoo, and also not seeing that my firewall is blocking cuckoo (& it never has in the past).  Any way to get help from VS logs to show what's going on with cuckoo, will the logs, can they, do they show what might be blocking VS sending to cuckoo.  The features in VS are great, not only pc lock, VT info, and cuckoo sandbox.  ;D Dan told me that cy+vs is a solid combo.   8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 04, 2017, 10:56:13 pm
Ehhhh... Dan.
I had to create account on another forums just to follow VS discussion but VS is worth it :)

+1  8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 04, 2017, 10:59:23 pm
Hello Dan

I am thinking even if you get all the bugs out of VS, there will still be newbies that are still going to need help but am pretty sure now that the word got out you are here, more of the old users will start showing up. Wow Last night I thought this forum was the hardest ever to sign up for but I think it might have been I had a few too many.

it took me several attempts over 2 days to register here. Not sure why? Don't care now. 
I do miss the flags that show new NEW posts.  is that a forum software thing?
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 04, 2017, 11:04:55 pm
I'm so pc clueless, how do I set my avatar here? I can find it. thanks!
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 04, 2017, 11:16:19 pm
Just click on profile at the top.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 12:09:29 am
question related to v4.12b & cuckoo on my pc. running win7.  recently uninstalled EAM (very solid, like it) and trying cylance (again).  Cy is fast and light from what I can see.  & cy is not causing any problems that are obvious.  It did quarantine 8 files shortly after install with a "background detection" ie those files were not running, and it seems you don't really tell cy to run a scan, although you can tell it to scan a specific folder, etc.  So... I wanted to check some file with VS/VAi as I think it had a score of 99 but no VT flags!  tried to send the file to cuckoo sandbox via VS and no response from my browser.   ???  Cy has very detailed reports and I'm not seeing that it is blocking some aspect of VS/cuckoo, and also not seeing that my firewall is blocking cuckoo (& it never has in the past).  Any way to get help from VS logs to show what's going on with cuckoo, will the logs, can they, do they show what might be blocking VS sending to cuckoo.  The features in VS are great, not only pc lock, VT info, and cuckoo sandbox.  ;D Dan told me that cy+vs is a solid combo.   8)
Great to see you here!  Hmmm, it is really difficult to say for sure... is there any chance you can send me the files in a zipped file... you might need to rename the .zip to .zi1 or something so it is not blocked.  The DeveloperLog.log would probably tell you something if there was as an exception / error... so right after you try to upload one to Cuckoo, check the last log entries and if you do not see the word "Exception", then nothing went wrong.  Also, you might check the file size... is it 0?  If so, that might be what is going on.

Let me ask you this... do some files work with Cuckoo, and some do not?

What kind of files are they?  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 05, 2017, 06:15:22 am
Just click on profile at the top.  :)

thanks... I'm sure I did that earlier and did not see it. I clicked profile again and I get a dropdown of 3 options.  Not sure what's next, but I'll hunt again, at least I'm getting closer or think  I am.  I just have to get use to this forum software.  wilders and MT are sorta similar. 
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 05, 2017, 06:33:43 am
question related to v4.12b & cuckoo on my pc. running win7.  recently uninstalled EAM (very solid, like it) and trying cylance (again).  Cy is fast and light from what I can see.  & cy is not causing any problems that are obvious.  It did quarantine 8 files shortly after install with a "background detection" ie those files were not running, and it seems you don't really tell cy to run a scan, although you can tell it to scan a specific folder, etc.  So... I wanted to check some file with VS/VAi as I think it had a score of 99 but no VT flags!  tried to send the file to cuckoo sandbox via VS and no response from my browser.   ???  Cy has very detailed reports and I'm not seeing that it is blocking some aspect of VS/cuckoo, and also not seeing that my firewall is blocking cuckoo (& it never has in the past).  Any way to get help from VS logs to show what's going on with cuckoo, will the logs, can they, do they show what might be blocking VS sending to cuckoo.  The features in VS are great, not only pc lock, VT info, and cuckoo sandbox.  ;D Dan told me that cy+vs is a solid combo.   8)
Great to see you here!  Hmmm, it is really difficult to say for sure... is there any chance you can send me the files in a zipped file... you might need to rename the .zip to .zi1 or something so it is not blocked.  The DeveloperLog.log would probably tell you something if there was as an exception / error... so right after you try to upload one to Cuckoo, check the last log entries and if you do not see the word "Exception", then nothing went wrong.  Also, you might check the file size... is it 0?  If so, that might be what is going on.

Let me ask you this... do some files work with Cuckoo, and some do not?

What kind of files are they?  Thank you!

cuckoo has always worked here until a day or 2 ago, so the timing is suspicious with cylance install, but I had not uploaded to cuckoo for a few weeks, and I know firewall updated, browser may have too.  file was an exe.  I'll try again and look in the log.log.  Could be any of at least 4 different things here.  thanks! 

EDIT: ok I just tried up upload to cuckoo a Phrozen app RunPEDetector32.exe 6.1 mb, (not the same file from previous failure to cuckoo) got a VS/Ai score of 66. browser stayed dead.  I do see something in the log, I'm sure it's related:

[12-05-2017 00:44:48] [INFO ] - Blacklisted Item allowed by parent process: c:\program files\voodooshield\voodooshield.exe
[12-05-2017 00:44:48] [INFO ] - Process allowed by Allowed Program Files: c:\program files\voodooshield\voodooshield.exe
[12-05-2017 00:45:21] [INFO ] - Cuckoo Analysis: c:\downloads\runpedetector32.exe
[12-05-2017 00:45:21] [INFO ] - Blocked: c:\downloads\runpedetector32.exe |  |
[12-05-2017 00:45:43] [ERROR] - Exception in UserPrompt_postTask: Unable to connect to the remote server.    at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at VoodooShield.FormUpload.?(String ?, String ?, String ?, Byte[] ?)
   at VoodooShield.FormUpload.MultipartFormDataPost(String postUrl, String userAgent, Dictionary`2 postParameters)
   at VoodooShield.UserPrompt.??()

hope that means more to you than it does to me
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 05, 2017, 12:46:21 pm
Hi Dan,
With version 3.59 the VS icon is always first to appear in the taskbar but with 4.12 it will always show like a good 30 second later. My only other security application is EAM.
Thanks and have a nice day. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 03:02:32 pm

cuckoo has always worked here until a day or 2 ago, so the timing is suspicious with cylance install, but I had not uploaded to cuckoo for a few weeks, and I know firewall updated, browser may have too.  file was an exe.  I'll try again and look in the log.log.  Could be any of at least 4 different things here.  thanks! 

EDIT: ok I just tried up upload to cuckoo a Phrozen app RunPEDetector32.exe 6.1 mb, (not the same file from previous failure to cuckoo) got a VS/Ai score of 66. browser stayed dead.  I do see something in the log, I'm sure it's related:

[12-05-2017 00:44:48] [INFO ] - Blacklisted Item allowed by parent process: c:\program files\voodooshield\voodooshield.exe
[12-05-2017 00:44:48] [INFO ] - Process allowed by Allowed Program Files: c:\program files\voodooshield\voodooshield.exe
[12-05-2017 00:45:21] [INFO ] - Cuckoo Analysis: c:\downloads\runpedetector32.exe
[12-05-2017 00:45:21] [INFO ] - Blocked: c:\downloads\runpedetector32.exe |  |
[12-05-2017 00:45:43] [ERROR] - Exception in UserPrompt_postTask: Unable to connect to the remote server.    at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at VoodooShield.FormUpload.?(String ?, String ?, String ?, Byte[] ?)
   at VoodooShield.FormUpload.MultipartFormDataPost(String postUrl, String userAgent, Dictionary`2 postParameters)
   at VoodooShield.UserPrompt.??()

hope that means more to you than it does to me

Thank you for letting me know... it looks like the Cuckoo server is down.  I took a quick look at it, but there was nothing simple and obvious, so I will take a look at it later today.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 03:04:38 pm
Hi Dan,
With version 3.59 the VS icon is always first to appear in the taskbar but with 4.12 it will always show like a good 30 second later. My only other security application is EAM.
Thanks and have a nice day. :)
Thank you for letting me know... off the top of my head, I think the only thing that will slow VS 4 down on startup compared to VS 3 is the internet check.  Does this computer have an always on internet connection that is stable?
Title: Re: VoodooShield v4 Beta Discussion
Post by: bootmgfw.efi on December 05, 2017, 03:17:19 pm
EDIT: ok I just tried up upload to cuckoo a Phrozen app RunPEDetector32.exe 6.1 mb, (not the same file from previous failure to cuckoo) got a VS/Ai score of 66.

If you downloaded RunPE Detector from the official website then you do not need to sandbox it. The software will be of no use to you if you sandbox it... It needs to access the list of processes running on your system and then query information about them so it can function as it is supposed to.

The software is clean and safe. If you downloaded it from another source other than the official, delete it and get the official copy.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 05, 2017, 03:23:39 pm
Hi Dan,
With version 3.59 the VS icon is always first to appear in the taskbar but with 4.12 it will always show like a good 30 second later. My only other security application is EAM.
Thanks and have a nice day. :)
Thank you for letting me know... off the top of my head, I think the only thing that will slow VS 4 down on startup compared to VS 3 is the internet check.  Does this computer have an always on internet connection that is stable?

Thanks for your reply. Yes, Internet is always on and it has been very stable for the last 10 years. Well, it's not a big deal I guess but I was just curious...
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 03:45:34 pm
Real quick (I am running late)... the Cuckoo Server is up and running again.  A simple router reboot fixed the issue.  I used to have my second browser tab set to the Cuckoo Sandbox so I could monitor it, but it never failed, so I removed it a few weeks ago.  Maybe I should add it again :).
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 05:27:41 pm
EDIT: ok I just tried up upload to cuckoo a Phrozen app RunPEDetector32.exe 6.1 mb, (not the same file from previous failure to cuckoo) got a VS/Ai score of 66.

If you downloaded RunPE Detector from the official website then you do not need to sandbox it. The software will be of no use to you if you sandbox it... It needs to access the list of processes running on your system and then query information about them so it can function as it is supposed to.

The software is clean and safe. If you downloaded it from another source other than the official, delete it and get the official copy.

I am guessing that he does not want to actually run the file sandboxed… he probably just wants to explode the file in Cuckoo sandbox so he can review the indicators of compromise.

Like this… http://voodooshield.ddns.net:8080/analysis/10195/

But I completely agree with your point… which is why I have never been a fan of traditional sandboxing or other methods that restrict other processes.

Especially with anti-sandboxing methods… it is quite difficult to be completely sure that all of the code executed properly.  So in the end, you have a potentially broken system, and you are not even 100% sure of the sandbox result.  VS has a local sandbox, but in my opinion, it is not all that useful.

I have been removing malware for local clients for close to 20 years, and almost 100% of the time, the user remarked that the malware pretty much came out of nowhere when they were browsing the web, or they clicked on an attachment that surprised them.  This is what led to the idea for VS… just lock the computer when it is at risk.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 05, 2017, 05:28:43 pm
Hi Dan,
With version 3.59 the VS icon is always first to appear in the taskbar but with 4.12 it will always show like a good 30 second later. My only other security application is EAM.
Thanks and have a nice day. :)
Thank you for letting me know... off the top of my head, I think the only thing that will slow VS 4 down on startup compared to VS 3 is the internet check.  Does this computer have an always on internet connection that is stable?

Thanks for your reply. Yes, Internet is always on and it has been very stable for the last 10 years. Well, it's not a big deal I guess but I was just curious...
Cool, thank you... I will look at the startup code and see if there is anything else that could be slowing it down.
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 06, 2017, 02:08:37 am
EDIT: ok I just tried up upload to cuckoo a Phrozen app RunPEDetector32.exe 6.1 mb, (not the same file from previous failure to cuckoo) got a VS/Ai score of 66.

If you downloaded RunPE Detector from the official website then you do not need to sandbox it. The software will be of no use to you if you sandbox it... It needs to access the list of processes running on your system and then query information about them so it can function as it is supposed to.

The software is clean and safe. If you downloaded it from another source other than the official, delete it and get the official copy.

you misunderstood. I just picked a random exe to upload to the VS_cuckoo sandbox for analysis as that VS_function was not working here.  was not trying to run runpedetector32, just using it as a test file.  I think Dan got the gist.  but appreciate your thoughts and concern. 
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 06, 2017, 02:16:29 am
Real quick (I am running late)... the Cuckoo Server is up and running again.  A simple router reboot fixed the issue.  I used to have my second browser tab set to the Cuckoo Sandbox so I could monitor it, but it never failed, so I removed it a few weeks ago.  Maybe I should add it again :).

yes VS_cuckoo just opened in my browser  ;D  VS/Ai= 66, cuckoo_malscore= 4.5 suspicious
always happy (happier) when the snafu is not on my stuff  ::)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 08, 2017, 08:10:27 am
I was hoping to have the next version for you guys by Friday, but it looks like we might be delayed to Saturday or Sunday.  As soon as it is ready, I will post a link on this thread.

Have a great weekend everyone, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on December 08, 2017, 12:06:09 pm
I was hoping to have the next version for you guys by Friday, but it looks like we might be delayed to Saturday or Sunday.  As soon as it is ready, I will post a link on this thread.

Have a great weekend everyone, thank you!
Will test the new version when it's ready, have a great weekend Dan!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 08, 2017, 03:30:31 pm
I was hoping to have the next version for you guys by Friday, but it looks like we might be delayed to Saturday or Sunday.  As soon as it is ready, I will post a link on this thread.

Have a great weekend everyone, thank you!

Take a good rest Dan you deserved it! :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 08, 2017, 05:02:43 pm
Hey Dan, Welcome back to CoU Forum. I had to uninstall your Beta software a few months ago because I couldn't handle the Trolls on the other forums and what they were doing to you. So I couldn't follow any of your posts. You're in good hands here at CoU, we have one of the best Troll Hunters here on the forum. LOL This weekend I'll install the Beta VS and it's back to business. :)

Dave.
Title: Re: VoodooShield v4 Beta Discussion
Post by: hayc59 on December 08, 2017, 07:39:20 pm
Welcome back Dave :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 08, 2017, 09:16:43 pm
Back to 3.59 for now. It's much snappier on my system than V4.12 which takes about 50 seconds to load on the taskbar.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 08, 2017, 09:35:45 pm
Hey Dan, Welcome back to CoU Forum. I had to uninstall your Beta software a few months ago because I couldn't handle the Trolls on the other forums and what they were doing to you. So I couldn't follow any of your posts. You're in good hands here at CoU, we have one of the best Troll Hunters here on the forum. LOL This weekend I'll install the Beta VS and it's back to business. :)

Dave.

Welcome back Dave.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 08, 2017, 09:40:16 pm
I am still running v4.10b  and it loads quickly in the taskbar at boot. I held off with further updates, probably because of the confusion and reading of something, that was latterly said in the MalwareTips forum for VoodooShield.  I knew I was right in not joining that forum, as hindsight, now shows. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 08, 2017, 09:45:32 pm
Hey Dan, Welcome back to CoU Forum. I had to uninstall your Beta software a few months ago because I couldn't handle the Trolls on the other forums and what they were doing to you. So I couldn't follow any of your posts. You're in good hands here at CoU, we have one of the best Troll Hunters here on the forum. LOL This weekend I'll install the Beta VS and it's back to business. :)

Dave.

Welcome back Dave.


I didn't know he'd been gone, to be welcomed back in the first place.  ;)    But, I've been gone, too, from CoU for quite awhile, so I hadn't noticed.  ;D
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 08, 2017, 09:46:56 pm
In that case, welcome back to you as well Tarnak  ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 08, 2017, 09:50:07 pm
Thanks.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: TroyN on December 09, 2017, 04:44:16 pm
Hi,
     I'm new to this board Just bought 3 year's of VoodooShield Pro. ;D

I've been reading allot on the other boards and decided to finally support a great program and register on COD.

Thanks again Dan for the register help. I'm still on 3.59 but will be switching to the 4.12 beta soon.

I hope i can contribute to the beta testing.

Thank you

Windows Defender with Windows 10 Fall Creators Update
Malwarebytes Pro 3.3.1.2183
Sandboxie PAID 5.22
ublock Origin
VoodooShield Pro v3.59 ...soon going 4.12b

TroyN
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 10, 2017, 11:51:43 am
G'day all.  Installed 4.12b a couple of days ago, but :(

I think the problem is VS phoning home for every app, every time I light that app up, even though almost all my apps have been whitelisted.  I can understand VS might be cautious about (for instance) Lotus, as that resides outside the Program Files system... but so does edexter, which loads as a proxy very smartly on Startup, no delays there.

FWIW, I have a Core i5 2400 @3.10GHz Sandy Bridge CPU in Win7 x64 Home Premium, an allegedly heavy duty router and a 25Gb fiber connection.  Unfortunately, something is gumming up the works, as I always have time to put sugar and 43 beans in my cup while waiting for almost any app to make its way to my screen.  The behaviour is not fixed by rebooting the router.

If I exit VS, I'm back to real-time app startups.

Important: VS does NOT noticeably slow my account login.

@Dan, what logs do you need?  Or possibly, what Rules should I set so VS doesn't use the Cloud so much?  (I'm not a fan of Cloud Computing BTW.)
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 10, 2017, 05:27:14 pm
Thanks for the "Welcome Back", but I actually didn't go anywhere. LOL
VoodooShield Beta installed yesterday on the Win 7 and running like a Swiss Watch.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Denis on December 10, 2017, 05:35:07 pm
Last beta link down? Always getting a time out. :-\
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 10, 2017, 06:40:49 pm
Last beta link down? Always getting a time out. :-\
Same here, even though I have it downloaded already.....
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 10, 2017, 06:59:57 pm
Last beta link down? Always getting a time out. :-\
Same here, even though I have it downloaded already.....
I'm getting the time out also. I didn't get it yesterday when I downloaded and installed VS. Server must be on a coffee break.  ::)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 10, 2017, 07:04:58 pm
Last beta link down? Always getting a time out. :-\
Same here, even though I have it downloaded already.....
I'm getting the time out also. I didn't get it yesterday when I downloaded and installed VS. Server must be on a coffee break.  ::)

This could be the reason, but we will have to wait to hear from Dan!

I was hoping to have the next version for you guys by Friday, but it looks like we might be delayed to Saturday or Sunday.  As soon as it is ready, I will post a link on this thread.

Have a great weekend everyone, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 10, 2017, 07:20:49 pm
It's great to see you guys!  I will catch up soon, but I wanted to mention that VS might have been super slow to start or analyze files the last 12 hours or so...  we hit our spending limit with Azure again.  I changed this setting to automatically increase the spending limit, so this should not happen again.  Sorry about that!

I am getting close to wrapping up the latest version, and I hope to have it for you guys sometime tonight, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 10, 2017, 07:22:36 pm
Thank you for keeping us updated Dan.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Petrovic on December 10, 2017, 08:37:42 pm
Last beta link down? Always getting a time out. :-\
works now
https://www.voodooshield.co/Download/InstallVoodooShield412beta.exe

mirror
https://www.upload.ee/files/7755306/InstallVoodooShield412beta.exe.html

CRC32: A6A9804C
MD5: 10F6BB6E48F0F9CC5066D34887DCBC13
SHA-1: 8FF88C033DDFADB830E1728D8B35D70BC3A1BDCB
SHA-256: EBF9A8EB849B85EFB0084EB2DC47C1B3CAC8AFF42448532E5888B66B0EA8FD0A
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 10, 2017, 08:42:51 pm
Hi Petr, Welcome to the CoU.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 10, 2017, 08:44:04 pm
Welcome to CoU Petr.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 10, 2017, 10:24:35 pm
Hello

Just wanted to mention I was like the 600 member at Wilders. Even though if you look at my profile it show me at 2002. I know for a fact I was there in 1997 on dialup. I was crapped on twice in that time by the mods. Most of whom were there much later. My nick was controller with one L.
I can still log in there but can not post. I guess I should have logged in here and at MT as controller with one L but thought everybody know me now as boredog and didn't want to confuse. A few of the old members I sent a what I thought was a private message to explaining who I was and hope to see some of them here.
That is my confession.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 10, 2017, 10:49:07 pm
Hello

Just wanted to mention I was like the 600 member at Wilders. Even though if you look at my profile it show me at 2002. I know for a fact I was there in 1997 on dialup. I was crapped on twice in that time by the mods. Most of whom were there much later. My nick was controller with one L.
I can still log in there but can not post. I guess I should have logged in here and at MT as controller with one L but thought everybody know me now as boredog and didn't want to confuse. A few of the old members I sent a what I thought was a private message to explaining who I was and hope to see some of them here.
That is my confession.
I remember controler so that's what happened to you at Wilders. But now you are boredog at Wilders so do they know? I use to visit Wilders for along time before I joined in 2004 and ever since they closed down Ten Forward many people left as it was a fun place at that time. https://www.wilderssecurity.com/threads/ten-forward.137078/

https://www.wilderssecurity.com/forums/ten-forward.50/
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 11, 2017, 01:30:00 am
... but I wanted to mention that VS might have been super slow to start or analyze files the last 12 hours or so...

Hi Dan - that looks like it could have been the source of my woes.

Cheers  :D
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 11, 2017, 03:10:58 am
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!



Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 11, 2017, 03:11:40 am
BTW, I should be able to catch up on the posts tonight or tomorrow, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 11, 2017, 03:37:40 am
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!

Thanks Dan!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on December 11, 2017, 10:21:57 am
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!
Did a clean install of version 4.13b. Nothing to report so far.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 11, 2017, 12:26:30 pm
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!

Hi Dan, As I am one of those who is experiencing slow start, I am looking forward to install the new beta version. Thanks :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 11, 2017, 02:12:04 pm
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!




Thank you Dan.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 11, 2017, 03:08:00 pm
I hate starting my postings here by mentioning a problem, but here goes.  ;D

I mentioned in another Board that I keep having a problem with VS causing other running programs to freeze. The only solution is to exit VS and as soon as I do that the affected programs start working again. I actually notice the mouse clicks that I made when a program is frozen, being executed as if they were in a buffer until VS exited.

Some additional (useful?) information: I have Bitdefender Antivirus, HitManPro Alert, Zemana AntiMalware (on demand) and Sandboxie.
This problem did not exist with VS version 3.59.

I am going to do a clean install of version 4.13b (desperately) hoping that perhaps the problem I mentioned will be overcome.

Another issue: Most of the times VS starts with Windows, but it remains in its "Off" state for several minutes. Then it wakes up and asks whether is should be turned On.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 11, 2017, 03:51:36 pm
Thank you guys for letting me know!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 11, 2017, 04:05:13 pm
I hate starting my postings here by mentioning a problem, but here goes.  ;D

I mentioned in another Board that I keep having a problem with VS causing other running programs to freeze. The only solution is to exit VS and as soon as I do that the affected programs start working again. I actually notice the mouse clicks that I made when a program is frozen, being executed as if they were in a buffer until VS exited.

Some additional (useful?) information: I have Bitdefender Antivirus, HitManPro Alert, Zemana AntiMalware (on demand) and Sandboxie.
This problem did not exist with VS version 3.59.

I am going to do a clean install of version 4.13b (desperately) hoping that perhaps the problem I mentioned will be overcome.

Another issue: Most of the times VS starts with Windows, but it remains in its "Off" state for several minutes. Then it wakes up and asks whether is should be turned On.
It's cool, thank you for bringing this up!  I think there is actually a pretty good chance that the first issue you mentioned is fixed in 4.13b.  Basically, since VS is largely web based, it has to check to see if it has access to the internet before it scans with the blacklist scanner and VoodooAi.  There are several things that can prevent VS from accessing the necessary web resources, and the .net WebClient method that I have been using did not have a built in timeout, but 4.13b does now.  I think what was happening was that VS would keep trying to check to see if there was an internet connection, and it was using the default 100 second timeout... but now the timeout is set to 3 seconds.  I hope that makes sense, if not, please let me know.  Also, if this happens again, please open the DeveloperLog.log and scroll to the bottom, and see if there are any entries that have the word "Exception".  If there is one, please post it and I will take a look at it.

As far as VS being in the Off state for several minutes... that is quite odd.  You should be able to choose Smart, Always ON or AutoPilot, and it should remember the mode for next time.  If either of these continue to be an issue, you might want to exit out of VS and delete all of the .db files in the C:\ProgramData\VoodooShield folder, then start VS again.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 11, 2017, 08:10:50 pm
Yeah, the outage from last night would have caused several weird issues, sorry about that.  I also fixed this in the 4.13b code, just in case something like that were to happen again.  This should also speed up VS's start for the users who were experiencing a slow start.

Here is the latest version, I think we are close, but if you guys find anything, please let me know!

www.voodooshield.co/Download/InstallVoodooShield413beta.exe

Thank you guys!

Hi Dan, I have been testing it for a couple of hours and indeed it fixes my slow start problems! :) You are truly amazing, thanks for this fantastic software!
Have a nice day!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 11, 2017, 09:29:17 pm
Thank you Dan, I have updated it now so will see how it goes.
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 11, 2017, 11:48:59 pm
After 2 shutdowns and startups the startup is perfect  :D the shutdown is still hanging.
Good to hear from you again Dan.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 12, 2017, 01:18:14 am
Thank you guys, it is great to hear from you guys as well!  I will focus on the shutdown issue the next couple of days while we wait to see if there are any other bugs.

For me, VS shuts down properly on Windows 8.1 and 10, but not Windows 7.  Is this what you guys are seeing too?  If so, I will test mainly with Windows 7, and that will help a lot.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 12, 2017, 01:25:26 am
Good Morning, Dan... Still morning here. ;)

I am still running v4.10b on Windows 10 Pro.  Is it OK for me to update install to v4.13, over-the-top? 

I prefer to do that, rather than to uninstall the previous version first, i.e. v4.10b
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 12, 2017, 01:56:15 am
For me, VS shuts down properly on Windows 8.1 and 10, but not Windows 7.  Is this what you guys are seeing too?  If so, I will test mainly with Windows 7, and that will help a lot.

Yep, that's what I'm seeing here on Win 7. Hangs about 5 to 10 seconds on shutdown on the latest Beta.
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 12, 2017, 02:52:22 am
Thank you guys, it is great to hear from you guys as well!  I will focus on the shutdown issue the next couple of days while we wait to see if there are any other bugs.

For me, VS shuts down properly on Windows 8.1 and 10, but not Windows 7.  Is this what you guys are seeing too?  If so, I will test mainly with Windows 7, and that will help a lot.

I'm running win7_64 and I don't notice any slow shutdowns, but I don't shut it down very often. What's slow exactly in a slow shutdown.  Something hangs??
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 12, 2017, 03:08:51 am
Yes simmerskool, when I shutdown the system hesitates as ProTruckDriver said for several seconds and then I get the windows built in program manager, an elevated screen similar to UAC elevation showing a program is preventing windows from shutting down properly but it doesn't reveal what program it is, just blank. I'm running win 7 64bit.

Thanks for your efforts Danl
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 12, 2017, 04:05:19 am
Thank you guys for letting me know!

Yeah, you can install VS 4.13b over the top.
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 12, 2017, 10:12:21 am
OFF-TOPIC (but please bear with me!)

I have Bitdefender Antivirus, HitManPro Alert, Zemana AntiMalware (on demand) and Sandboxie.

G'day Colonel - FWIW, both MBAM and ZAM leave a service running even if you don't use real-time protection.  It seemed to me that these services were in some way interfering with VS and with each other, and I did notice an improvement when I manually stopped the services and set their startups to "Manual".  Of course, this means that when I do my monthly on-demand search-and-destroy, I still have to manually stop the services...  I think it's a good idea to let one of them do its thing, stop the service, then let the other do its work.  And then stop that service :)

BACK ON-TOPIC! :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 12, 2017, 10:21:15 am
For me, VS shuts down properly on Windows 8.1 and 10, but not Windows 7.  Is this what you guys are seeing too?

Yes, Win7 x64 Home Premium.  Exactly as described by @BryanB.  I'm sure Windows does or can log these hangs as an event, but I have no idea where to look, and HP is very short on industrial-quality diagnostics.  I wish I had known that when I ordered this box: I was offered Pro, but...  Thank you Microsoft.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 12, 2017, 02:38:56 pm
Also, if this happens again, please open the DeveloperLog.log and scroll to the bottom, and see if there are any entries that have the word "Exception".  If there is one, please post it and I will take a look at it.

Thank you Dan.

Here is what I see in the DeveloperLog.log:
Quote
[ERROR] - Exception in DriverCommunicationService_HandleSingleProcess: There was an error writing to the pipe: Unrecognized error 232 (0xe8)..
Server stack trace:
   at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
   at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.OnSend(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.OutputChannel.Send(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.Send(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at
  • :

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at VoodooShieldService.IHandleProcessCallback.OnProcessCreation(ProcessCreationCtx context)
   at VoodooShieldService.DriverCommunicationService.HandleSingleProcess(Object threadContext)
[12-11-2017 17:28:26] [DEBUG] - DriverCommunicationService::Exit main loop
[12-11-2017 17:28:26] [DEBUG] - Thread 8 Failed to stop
[12-11-2017 17:28:26] [DEBUG] - DriverCommunicationService::Disconnected
[12-11-2017 17:28:26] [INFO ] - VoodooShieldService.OnSessionChange: SessionLogoff
[12-11-2017 17:28:27] [INFO ] - VoodooShieldService.OnSessionChange: ConsoleDisconnect
[12-11-2017 17:28:27] [INFO ] - VoodooShieldService.OnSessionChange: ConsoleConnect
[12-11-2017 17:28:39] [INFO ] - VoodooShieldService.OnSessionChange: SessionLogon
[12-11-2017 17:28:56] [DEBUG] - DriverCommunicationService::Connect 10 threads
[12-11-2017 17:28:56] [DEBUG] - ->DriverCommunication.ctor
[12-11-2017 17:28:56] [DEBUG] - DriverCommunicationService::Enter main loop
[12-11-2017 17:40:49] [DEBUG] - DriverCommunicationService::Disconnect
[12-11-2017 17:40:49] [DEBUG] - DriverCommunicationService::Exit main loop
[12-11-2017 17:40:49] [DEBUG] - DriverCommunicationService::Disconnected
[12-11-2017 17:40:49] [DEBUG] - DriverCommunicationService::Client disconnected
[12-11-2017 17:50:10] [DEBUG] - DriverCommunicationService::Connect 10 threads
[12-11-2017 17:50:10] [DEBUG] - ->DriverCommunication.ctor
[12-11-2017 17:50:10] [DEBUG] - DriverCommunicationService::Enter main loop
[12-11-2017 18:33:55] [DEBUG] - DriverCommunicationService::Disconnect
[12-11-2017 18:33:55] [DEBUG] - DriverCommunicationService::Exit main loop
[12-11-2017 18:33:55] [ERROR] - Wait For response error 0x00000000
[12-11-2017 18:33:55] [ERROR] - Wait For response error 0x00000000
[12-11-2017 18:33:55] [DEBUG] - DriverCommunicationService::Disconnected
[12-11-2017 18:33:55] [DEBUG] - DriverCommunicationService::Client disconnected
[12-11-2017 18:55:31] [INFO ] - VoodooShieldService.OnSessionChange: SessionLock
[12-11-2017 19:01:24] [INFO ] - VoodooShieldService.OnSessionChange: SessionUnlock
[12-11-2017 19:40:31] [INFO ] - VoodooShieldService.OnSessionChange: SessionLock
[12-11-2017 22:12:10] [INFO ] - VoodooShieldService.OnSessionChange: SessionUnlock
[12-11-2017 22:28:39] [INFO ] - VoodooShieldService.OnSessionChange: SessionLock
[12-11-2017 23:33:04] [INFO ] - VoodooShieldService.OnSessionChange: SessionLogoff
[12-12-2017 14:59:07] [INFO ] - User Log Initialized
[12-12-2017 14:59:07] [INFO ] - Snapshot file Initialized
[12-12-2017 14:59:07] [INFO ] - Service started
[12-12-2017 14:59:09] [INFO ] - Driver communication service started
[12-12-2017 15:11:58] [INFO ] - VoodooShieldService.OnSessionChange: SessionLogon
[12-12-2017 15:12:12] [DEBUG] - DriverCommunicationService::Connect 10 threads
[12-12-2017 15:12:12] [DEBUG] - ->DriverCommunication.ctor
[12-12-2017 15:12:12] [DEBUG] - DriverCommunicationService::Enter main loop
[12-12-2017 15:16:07] [DEBUG] - DriverCommunicationService::Disconnect
[12-12-2017 15:16:07] [DEBUG] - DriverCommunicationService::Exit main loop
[12-12-2017 15:16:07] [DEBUG] - DriverCommunicationService::Disconnected
[12-12-2017 15:16:07] [DEBUG] - DriverCommunicationService::Client disconnected
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 12, 2017, 04:38:40 pm
Not sure which thread to post in but for some reason when I select to move shield, VS forgets this on reboot. Installed over 4.12 and had same issue in 4.12.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 12, 2017, 09:13:48 pm
Update:

I have selected move shield numerous time and rebooted and every time the shield moves back to bottom right and can not be move until selecting move shield again.

Title: Re: VoodooShield v4 Beta Discussion
Post by: russ0408 on December 12, 2017, 09:36:12 pm
Glad to see you up and posting again Dan. Joined the forum to follow you and Voodooshield, keep up the great work my friend.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 12, 2017, 11:21:29 pm
Update:

I have selected move shield numerous time and rebooted and every time the shield moves back to bottom right and can not be move until selecting move shield again.

I agree, this is also the problem I am having. Other than that in W10 it seems to be working perfectly from what I have seen.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 12, 2017, 11:23:45 pm
I am using Win 10 also.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 13, 2017, 04:46:35 am
Very cool, it's great to see you guys on COU!  The desktop shield gadget position issue is fixed and I am getting close to fixing the shutdown issue as well.  If everything goes right, I will be able to release 4.14b tomorrow and then we will wait a few days to see if anyone finds any other bugs.  Thank you guys for all of your help!
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 13, 2017, 05:10:54 am
The desktop shield gadget position issue is fixed and I am getting close to fixing the shutdown issue as well.  If everything goes right, I will be able to release 4.14b tomorrow and then we will wait a few days to see if anyone finds any other bugs.

Thanks Dan. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 13, 2017, 06:41:36 am
gotta ask (no intent to create problems) 4.13b crashed overnight when my pc should have been idling doing "nothing," but tricky week, MS might have tried to push updates. Also running AppGuard along with VS, sent logs to Dan who saw no logged problems or conflicts, but did suggest a compatibility conflict might have caused the VS crash.  I had the exact same thing happen recently, within 6 weeks but with a previous beta version.  And this has only happened within first day of an install of VS beta version, and then it runs for weeks rock solid.  Is AG unnecessarily redundant protection and can be uninstalled or disabled without losing a layer of protection?  Normally I see no issues, and I use my pc a lot.  I think of AG as another layer of protection, but wondering what is it protecting with VS onguard and solid av running.  And could an MS pushed update have caused the VS crash?  Also wondering, would it be beneficial to publish hash of installed VS and its service, just to confirm that we're all running exactly what we think we are running (& nothing more).  Thanks. (unexplained crashes make me a tad "anxious")
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 13, 2017, 10:19:59 pm
I have been running Appguard along with VS forever with no issues. WE problem don't need both. Appguard is higher up on the food chain. By that is always reacts before VS. I will run them both together anyway.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Schank873-2 on December 14, 2017, 01:38:30 am
I'm running appcheck, EAM, HMP.A and no issues issues with VS or no slow-downs...
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 14, 2017, 01:40:11 am
I have been running Appguard along with VS forever with no issues. WE problem don't need both. Appguard is higher up on the food chain. By that is always reacts before VS. I will run them both together anyway.

yeah, I've run AG on and off for several years, and more recently continuously along with VS.  Dan suggested possible conflict in memory with AG...  :-\ (my gut tells me it's something else...  For the moment I've disabled AG and the last 2 or 3 crashes I've had with VS have been spaced very far apart, and like I mentioned shortly after & within a day of installing a new version of VS, but seems like those times also coincided with MS update push.  So infrequent, I don't really consider it a problem, other than it happened at least twice under same circumstances for no apparent or logged reason.

Dan, why not publish the hash for the installer, and also for voodooshield and voodooshieldservice once isntalled? Or does each pc's whitelist create a different hash??
 
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 14, 2017, 01:54:06 am
Glad to see this thread... I'm still seeing notification laggy responsiveness, both when I choose to "Allow" a program, and when I tick the "report false positive" box. Generally, there is a 5-second delay before the notification disappears (and the program is allowed) or the "report false positive" box accepts a mouse click. This is what I classify as an "annoyance" and it has been present for quite some time.

v4.13b, Win 8.1 (x64)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 14, 2017, 02:49:09 am
I have been running Appguard along with VS forever with no issues. WE problem don't need both. Appguard is higher up on the food chain. By that is always reacts before VS. I will run them both together anyway.

yeah, I've run AG on and off for several years, and more recently continuously along with VS.  Dan suggested possible conflict in memory with AG...  :-\ (my gut tells me it's something else...  For the moment I've disabled AG and the last 2 or 3 crashes I've had with VS have been spaced very far apart, and like I mentioned shortly after & within a day of installing a new version of VS, but seems like those times also coincided with MS update push.  So infrequent, I don't really consider it a problem, other than it happened at least twice under same circumstances for no apparent or logged reason.

Dan, why not publish the hash for the installer, and also for voodooshield and voodooshieldservice once isntalled? Or does each pc's whitelist create a different hash??
You are running Comodo as well, right?  I wonder if anyone has had any luck running all three products together.  I will be curious to see what is causing this because the logs are not showing anything, and no one else has reported this issue.  If it continues, maybe you can send me a crash dump and I can take a look at it.

I am not sure what you mean by publish the hash... do you mean post the hash of the installer when I post a new version?  The hash will be the same for each file on every computer.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 14, 2017, 02:52:28 am
Glad to see this thread... I'm still seeing notification laggy responsiveness, both when I choose to "Allow" a program, and when I tick the "report false positive" box. Generally, there is a 5-second delay before the notification disappears (and the program is allowed) or the "report false positive" box accepts a mouse click. This is what I classify as an "annoyance" and it has been present for quite some time.

v4.13b, Win 8.1 (x64)
Very cool, great to see you here as well!  Hmmm, that is very odd.  If you look in your DeveloperLog.log, are there any entries with the word "Exception"?  If so, can you post the exception?  Thank you!

Edit:  Also, are there any special settings other than default that you use that might help me reproduce this error?
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 14, 2017, 02:55:16 am
BTW, I figured out what is causing the Windows 7 shutdown issue, I just need to figure out how to fix it now, so hopefully it will not be to long.  I will also see if we can fix the other couple of bugs that people have reported for the next version.  Thank you!

Edit:  I think the Windows 7 shutdown issue is fixed... I will double check it in the morning and look at these last couple of bugs.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 14, 2017, 11:58:16 pm
I was monitoring Windows Updates, i.e. those automatically offered for December.  This process had started about 10 hours earlier, when I noticed that NVIDIA was updating, and I got this popup in VS. As you can see nothing informative to see, but I allowed it.





Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 15, 2017, 12:16:26 am
These are the folders created in C:\Program Files\NVIDIA Corporation...  I hope they are OK.



Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 15, 2017, 12:18:20 am
Very cool, great to see you here as well!  Hmmm, that is very odd.  If you look in your DeveloperLog.log, are there any entries with the word "Exception"?  If so, can you post the exception?  Thank you!

Here are the DeveloperLog "exceptions" from yesterday (12/13)

[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 10:20:26] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-13-2017 14:26:44] [ERROR] - Exception in GetSHA256c: The filename, directory name, or volume label syntax is incorrect.
[12-13-2017 14:26:57] [ERROR] - Exception in GetSHA256c: The filename, directory name, or volume label syntax is incorrect.
[12-13-2017 14:58:31] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 22:51:55] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)

Quote
Edit:  Also, are there any special settings other than default that you use that might help me reproduce this error?

Nothing very exciting. Unchecked "Deny by Default"; Sensitivity: 120%; one added web app (nitropdf).

Another question... I saw this in the Developer Log...

[12-14-2017 19:04:37] [INFO ] - Blacklisted Item allowed by parent process: c:\program files (x86)\sticky password\stpass.exe
[12-14-2017 19:04:37] [INFO ] - Process allowed by Allowed Program Files: c:\program files (x86)\sticky password\stpass.exe
[12-14-2017 19:04:38] [INFO ] - Blacklisted Item allowed by parent process: c:\program files (x86)\sticky password\stpass.exe

What's the "Blacklisted Item" thingy? I didn't do this. How can I see what is "blacklisted" on my system? I looked these up under User Log and found only Auto Allowed. So I don't understand the "blacklist" or the "allowed by parent" deal here.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 15, 2017, 06:53:49 am
These are the folders created in C:\Program Files\NVIDIA Corporation...  I hope they are OK.
Yeah, I am sure they are fine.  I am guessing that NVIDIA created a temporary executable, then deleted it for whatever reason.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 15, 2017, 06:57:43 am
Very cool, great to see you here as well!  Hmmm, that is very odd.  If you look in your DeveloperLog.log, are there any entries with the word "Exception"?  If so, can you post the exception?  Thank you!

Here are the DeveloperLog "exceptions" from yesterday (12/13)

[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:31:34] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 07:37:20] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 10:20:26] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-13-2017 14:26:44] [ERROR] - Exception in GetSHA256c: The filename, directory name, or volume label syntax is incorrect.
[12-13-2017 14:26:57] [ERROR] - Exception in GetSHA256c: The filename, directory name, or volume label syntax is incorrect.
[12-13-2017 14:58:31] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 19:40:24] [ERROR] - Exception in RealtimeScanner_IsFileInVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[12-13-2017 21:17:56] [ERROR] - Exception in NewProcessHandler_GetStatsFromVoodooAiSQLDatabase: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[12-13-2017 22:51:55] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)

Quote
Edit:  Also, are there any special settings other than default that you use that might help me reproduce this error?

Nothing very exciting. Unchecked "Deny by Default"; Sensitivity: 120%; one added web app (nitropdf).

Another question... I saw this in the Developer Log...

[12-14-2017 19:04:37] [INFO ] - Blacklisted Item allowed by parent process: c:\program files (x86)\sticky password\stpass.exe
[12-14-2017 19:04:37] [INFO ] - Process allowed by Allowed Program Files: c:\program files (x86)\sticky password\stpass.exe
[12-14-2017 19:04:38] [INFO ] - Blacklisted Item allowed by parent process: c:\program files (x86)\sticky password\stpass.exe

What's the "Blacklisted Item" thingy? I didn't do this. How can I see what is "blacklisted" on my system? I looked these up under User Log and found only Auto Allowed. So I don't understand the "blacklist" or the "allowed by parent" deal here.
Cool, thank you, I researched this error and it seems there are a couple of fixes.  Do you use a VPN, or is there a firewall that might be blocking VS's connection with the web?

Blacklisted items are basically items that should never be permanently whitelisted, such as cmd and powershell.  A few months ago I added whitelisting by parent process as well (in addition to process name, path, hash, etc.), so we might be able to remove the blacklist feature altogether.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 15, 2017, 07:03:30 am
I have been running Appguard along with VS forever with no issues. WE problem don't need both. Appguard is higher up on the food chain. By that is always reacts before VS. I will run them both together anyway.

yeah, I've run AG on and off for several years, and more recently continuously along with VS.  Dan suggested possible conflict in memory with AG...  :-\ (my gut tells me it's something else...  For the moment I've disabled AG and the last 2 or 3 crashes I've had with VS have been spaced very far apart, and like I mentioned shortly after & within a day of installing a new version of VS, but seems like those times also coincided with MS update push.  So infrequent, I don't really consider it a problem, other than it happened at least twice under same circumstances for no apparent or logged reason.

Dan, why not publish the hash for the installer, and also for voodooshield and voodooshieldservice once isntalled? Or does each pc's whitelist create a different hash??
You are running Comodo as well, right?  I wonder if anyone has had any luck running all three products together.  I will be curious to see what is causing this because the logs are not showing anything, and no one else has reported this issue.  If it continues, maybe you can send me a crash dump and I can take a look at it.

I am not sure what you mean by publish the hash... do you mean post the hash of the installer when I post a new version?  The hash will be the same for each file on every computer.  Thank you!

Yes, you are correct running comodo firewall 10 @ cruelsister, AG4 & VS 4.13b. Reference the VS overnight crash a couple days ago, that was extremely rare event, and both recent crashes were about a month apart and seemed to coincide with an install of a new beta version along with MS update push overnight while I was sleeping.  Otherwise and 99.999% of time those 3 are rock solid and seem not to conflict with each other at all.  If I was seeing crashes more often, sure could be conflict.  But once a month.  And I'll go weeks without a shutdown.  I did disable AG for about 36 hours, and then re-enabled it.  Everything's been rock solid except the the rare VS crash the other day.

hash, I mean eg sha1 for
InstallVoodooShield413beta.exe   4f9899e5d2c81d9b9507167c4224e4178437452b
VoodooShield.exe   cbe1ae31152d0ddf7f4be9577522ed713c69d46a
VoodooShieldService.exe   609de367da0e3b3ab70cbc728031fffc15c75cef

These are the sha1 hashes for those files after install of 4.13b running on my win7.  If you published the hashes on your end, then user would have a good idea that he got a clean untampered with file.  Many publishers do that.  Just wondering...  ;)

 
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 15, 2017, 07:08:49 am
I was monitoring Windows Updates, i.e. those automatically offered for December.  This process had started about 10 hours earlier, when I noticed that NVIDIA was updating, and I got this popup in VS. As you can see nothing informative to see, but I allowed it.

Maybe a clue to my unattended overnight crash the other day. Also have nvidia, and I think nvidia may have installed something when I wasn't looking based on opening revo_pro and noticing several nvidia apps I had not noticed before...  ???
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 15, 2017, 07:45:05 am
These are the folders created in C:\Program Files\NVIDIA Corporation...  I hope they are OK.
Yeah, I am sure they are fine.  I am guessing that NVIDIA created a temporary executable, then deleted it for whatever reason.  Thank you!


I was monitoring Windows Updates, i.e. those automatically offered for December.  This process had started about 10 hours earlier, when I noticed that NVIDIA was updating, and I got this popup in VS. As you can see nothing informative to see, but I allowed it.

Maybe a clue to my unattended overnight crash the other day. Also have nvidia, and I think nvidia may have installed something when I wasn't looking based on opening revo_pro and noticing several nvidia apps I had not noticed before...  ???

@VoodooShield, @simmerskool

I checked in "Programs and Features", and it seems all is OK.  ;)





Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 15, 2017, 02:57:59 pm
I have been running Appguard along with VS forever with no issues. WE problem don't need both. Appguard is higher up on the food chain. By that is always reacts before VS. I will run them both together anyway.

yeah, I've run AG on and off for several years, and more recently continuously along with VS.  Dan suggested possible conflict in memory with AG...  :-\ (my gut tells me it's something else...  For the moment I've disabled AG and the last 2 or 3 crashes I've had with VS have been spaced very far apart, and like I mentioned shortly after & within a day of installing a new version of VS, but seems like those times also coincided with MS update push.  So infrequent, I don't really consider it a problem, other than it happened at least twice under same circumstances for no apparent or logged reason.

Dan, why not publish the hash for the installer, and also for voodooshield and voodooshieldservice once isntalled? Or does each pc's whitelist create a different hash??
You are running Comodo as well, right?  I wonder if anyone has had any luck running all three products together.  I will be curious to see what is causing this because the logs are not showing anything, and no one else has reported this issue.  If it continues, maybe you can send me a crash dump and I can take a look at it.

I am not sure what you mean by publish the hash... do you mean post the hash of the installer when I post a new version?  The hash will be the same for each file on every computer.  Thank you!

Yes, you are correct running comodo firewall 10 @ cruelsister, AG4 & VS 4.13b. Reference the VS overnight crash a couple days ago, that was extremely rare event, and both recent crashes were about a month apart and seemed to coincide with an install of a new beta version along with MS update push overnight while I was sleeping.  Otherwise and 99.999% of time those 3 are rock solid and seem not to conflict with each other at all.  If I was seeing crashes more often, sure could be conflict.  But once a month.  And I'll go weeks without a shutdown.  I did disable AG for about 36 hours, and then re-enabled it.  Everything's been rock solid except the the rare VS crash the other day.

hash, I mean eg sha1 for
InstallVoodooShield413beta.exe   4f9899e5d2c81d9b9507167c4224e4178437452b
VoodooShield.exe   cbe1ae31152d0ddf7f4be9577522ed713c69d46a
VoodooShieldService.exe   609de367da0e3b3ab70cbc728031fffc15c75cef

These are the sha1 hashes for those files after install of 4.13b running on my win7.  If you published the hashes on your end, then user would have a good idea that he got a clean untampered with file.  Many publishers do that.  Just wondering...  ;)
Yeah, I agree... if the crash is that infrequent, then it is probably not a compatibility problem between the three products.  If it crashes again, can you please take a screenshot of the crash and send it to me?

Yeah, I should probably start posting the hashes of the installers when I post new versions of VS.

I hope to have the Telos and ColonelMal bugs fixed soon, then I will release the last version before we go public.

Thank you guys, have a great weekend!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 15, 2017, 03:02:26 pm
I hate starting my postings here by mentioning a problem, but here goes.  ;D

I mentioned in another Board that I keep having a problem with VS causing other running programs to freeze. The only solution is to exit VS and as soon as I do that the affected programs start working again. I actually notice the mouse clicks that I made when a program is frozen, being executed as if they were in a buffer until VS exited.

Some additional (useful?) information: I have Bitdefender Antivirus, HitManPro Alert, Zemana AntiMalware (on demand) and Sandboxie.
This problem did not exist with VS version 3.59.

I am going to do a clean install of version 4.13b (desperately) hoping that perhaps the problem I mentioned will be overcome.

Another issue: Most of the times VS starts with Windows, but it remains in its "Off" state for several minutes. Then it wakes up and asks whether is should be turned On.
Do you think there is a chance that there is a conflict between HitManPro Alert and VS?  Does these issues go away if you temporarily disable HitManPro Alert?  I know VS works great with the other products you mentioned, so I am just guessing.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 15, 2017, 06:47:35 pm
I hate starting my postings here by mentioning a problem, but here goes.  ;D

I mentioned in another Board that I keep having a problem with VS causing other running programs to freeze. The only solution is to exit VS and as soon as I do that the affected programs start working again. I actually notice the mouse clicks that I made when a program is frozen, being executed as if they were in a buffer until VS exited.

Some additional (useful?) information: I have Bitdefender Antivirus, HitManPro Alert, Zemana AntiMalware (on demand) and Sandboxie.
This problem did not exist with VS version 3.59.

I am going to do a clean install of version 4.13b (desperately) hoping that perhaps the problem I mentioned will be overcome.

Another issue: Most of the times VS starts with Windows, but it remains in its "Off" state for several minutes. Then it wakes up and asks whether is should be turned On.
Do you think there is a chance that there is a conflict between HitManPro Alert and VS?  Does these issues go away if you temporarily disable HitManPro Alert?  I know VS works great with the other products you mentioned, so I am just guessing.  Thank you!

Well in my case I definitely had a conflict between HitmanPro.Alert and VS (Program freeze or slowdown) I did remove HitmanPro.Alert and problems are gone.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 15, 2017, 06:56:03 pm
Do you think there is a chance that there is a conflict between HitManPro Alert and VS?  Does these issues go away if you temporarily disable HitManPro Alert?  I know VS works great with the other products you mentioned, so I am just guessing.  Thank you!
It's ironic that after I disabled every setting in HitManPro Alert, then switched windows, and then returned back to the HMPA settings window in order to close it, it was frozen! It became active again as soon as I exited VS.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 16, 2017, 08:14:09 pm
Do you use a VPN, or is there a firewall that might be blocking VS's connection with the web?

VPN use is sporadic. I don't think any of these exceptions occurred with VPN. I use Comodo Firewall and created a do not block rule for VS. Since then I still have a few exceptions:

[12-15-2017 14:11:00] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-15-2017 20:11:03] [ERROR] - Exception in BlacklistlScanner_GetReport: The remote server returned an error: (500) Internal Server Error..    at System.Net.HttpWebRequest.GetResponse()
[12-16-2017 13:47:42] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-16-2017 14:58:46] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)

Looks like a program line issue (in 3 cases). I'm not sure about the server error. No VPN (or proxy) was in use at these times.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 17, 2017, 02:55:39 am
That is interesting about HMPA and VS... I think I will buy a license and test to see what might be going on.  Thank you for letting me know!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 17, 2017, 03:06:12 am
Do you use a VPN, or is there a firewall that might be blocking VS's connection with the web?

VPN use is sporadic. I don't think any of these exceptions occurred with VPN. I use Comodo Firewall and created a do not block rule for VS. Since then I still have a few exceptions:

[12-15-2017 14:11:00] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-15-2017 20:11:03] [ERROR] - Exception in BlacklistlScanner_GetReport: The remote server returned an error: (500) Internal Server Error..    at System.Net.HttpWebRequest.GetResponse()
[12-16-2017 13:47:42] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)
[12-16-2017 14:58:46] [ERROR] - Exception in Main_Shown: File '' not found..    at Microsoft.VisualBasic.FileSystem.FileLen(String PathName)

Looks like a program line issue (in 3 cases). I'm not sure about the server error. No VPN (or proxy) was in use at these times.
Cool, please let me know what VPN you use and I will test it with VS to make sure it works properly.

As far as the file not found error goes, this is quite odd, but I can add some debugging code in the next version that will tell us more.  I should have the next version for you guys in a day or two.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 17, 2017, 03:16:03 am
Cool, please let me know what VPN you use
AirVPN & Windscribe
Title: Re: VoodooShield v4 Beta Discussion
Post by: j9ksf on December 17, 2017, 06:33:20 am
I use Windscribe alongside VS without problems.
Title: Re: VoodooShield v4 Beta Discussion
Post by: djg05 on December 17, 2017, 11:08:21 am
Upgraded to 4.13 yesterday and no issues so far.
Title: Re: VoodooShield v4 Beta Discussion
Post by: M_G_H on December 17, 2017, 03:24:00 pm
I also use Windscribe along VS without issues.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 17, 2017, 04:12:54 pm
That is interesting about HMPA and VS... I think I will buy a license and test to see what might be going on.  Thank you for letting me know!
It may be useful to see what HMPA may do in relation to VS.

However, I think that one should go back to the past when I stated (in a different forum) what I noticed almost at the very beginning of this problem, that is that VS did not cause any program to freeze in v.3.59. Since before VS v.3.59 I have been using an application toolbar called Powerpro which shows many commands and running programs as buttons on it. A program freezes (and I assume this is caused by VS), when I click on its corresponding toolbar button. The toolbar itself becomes unresponsive too, until I exit VS. In conclusion, I think there is an incompatibility between Powerpro and VS which results in running programs that are shown as buttons on the toolbar to freeze until I actually exit Voodooshield. I tested this by opening many programs not directly by using the toolbar menus, but from the Windows Start menu instead. There was no program freezing until I tried accessing (focusing on) any running programs using their respective toolbar buttons on Powerpro. The freezing problem went away (as usual) after I exited VS. Since you may ask, the frozen programs also become unfrozen if I exit Powerpro. This having been said, no program is frozen when VS is not running.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 17, 2017, 04:22:28 pm
VS Service is the largest contributor element of my boot time, contributing approximately 5.4 seconds. I'm using an SSD.

FWIW, AdGuard is a close second. All other services load under 1 second (each).
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 17, 2017, 05:19:44 pm
Dan, I am still having the ongoing problem I have been having since moving beyond 3.59 That is various forms (depending on beta) of VS shutting down when moving from admin account to another. 3.59 will work for me after a small tweak prior to switching accounts.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 03:40:39 am
Thank you guys for letting me know about Windscribe... I tried it as well and it seemed to work great.  I tried AirVPN a while back and it seemed to work great as well.  Although, when I looked in my log while using Windscribe, I did see the same errors that Telos posted... so all I have to do is debug VS with Windscribe running and it will be a quick fix.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 03:42:57 am
That is interesting about HMPA and VS... I think I will buy a license and test to see what might be going on.  Thank you for letting me know!
It may be useful to see what HMPA may do in relation to VS.

However, I think that one should go back to the past when I stated (in a different forum) what I noticed almost at the very beginning of this problem, that is that VS did not cause any program to freeze in v.3.59. Since before VS v.3.59 I have been using an application toolbar called Powerpro which shows many commands and running programs as buttons on it. A program freezes (and I assume this is caused by VS), when I click on its corresponding toolbar button. The toolbar itself becomes unresponsive too, until I exit VS. In conclusion, I think there is an incompatibility between Powerpro and VS which results in running programs that are shown as buttons on the toolbar to freeze until I actually exit Voodooshield. I tested this by opening many programs not directly by using the toolbar menus, but from the Windows Start menu instead. There was no program freezing until I tried accessing (focusing on) any running programs using their respective toolbar buttons on Powerpro. The freezing problem went away (as usual) after I exited VS. Since you may ask, the frozen programs also become unfrozen if I exit Powerpro. This having been said, no program is frozen when VS is not running.
Cool, this will help a lot... can you please post a link to the exact version of Powerpro you are using, and let me know what browsers to test / debug with?  Please keep in mind that a lot has changed from VS 3 to 4, so there might be a couple of bugs that I have missed.  But if we work with specific examples like Powerpro, it should be quite easy to fix these last couple of bugs.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 03:45:12 am
VS Service is the largest contributor element of my boot time, contributing approximately 5.4 seconds. I'm using an SSD.

FWIW, AdGuard is a close second. All other services load under 1 second (each).
Cool, can you please let me know what program you are using to benchmark the startup items?  VS's service is tiny and should load very quickly, but I will take a look at it and make sure it is not running unnecessary code on startup.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 03:47:41 am
Dan, I am still having the ongoing problem I have been having since moving beyond 3.59 That is various forms (depending on beta) of VS shutting down when moving from admin account to another. 3.59 will work for me after a small tweak prior to switching accounts.
Hmmm, this is odd... the 4.13beta should work really well with user switching.  Can you please describe the error in detail?  What small tweak do you have to perform to make 3.59 work properly?  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 03:50:52 am
I also wanted to mention... if anyone is having any kind of slowdown issue, can you please temporarily disable the "Automatically scan blocked files with VoodooAi" setting in VoodooShield Settings / Advanced, and let me know if the problem persists.  Also, you might try to temporarily disable the "Automatically scan blocked files with the mulit engine blacklist scanner" option to see if that makes a difference.  This will help narrow down what might be causing the issue.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 18, 2017, 07:27:04 am
That is interesting about HMPA and VS... I think I will buy a license and test to see what might be going on.  Thank you for letting me know!
It may be useful to see what HMPA may do in relation to VS.

However, I think that one should go back to the past when I stated (in a different forum) what I noticed almost at the very beginning of this problem, that is that VS did not cause any program to freeze in v.3.59. Since before VS v.3.59 I have been using an application toolbar called Powerpro which shows many commands and running programs as buttons on it. A program freezes (and I assume this is caused by VS), when I click on its corresponding toolbar button. The toolbar itself becomes unresponsive too, until I exit VS. In conclusion, I think there is an incompatibility between Powerpro and VS which results in running programs that are shown as buttons on the toolbar to freeze until I actually exit Voodooshield. I tested this by opening many programs not directly by using the toolbar menus, but from the Windows Start menu instead. There was no program freezing until I tried accessing (focusing on) any running programs using their respective toolbar buttons on Powerpro. The freezing problem went away (as usual) after I exited VS. Since you may ask, the frozen programs also become unfrozen if I exit Powerpro. This having been said, no program is frozen when VS is not running.
Cool, this will help a lot... can you please post a link to the exact version of Powerpro you are using, and let me know what browsers to test / debug with?  Please keep in mind that a lot has changed from VS 3 to 4, so there might be a couple of bugs that I have missed.  But if we work with specific examples like Powerpro, it should be quite easy to fix these last couple of bugs.  Thank you!

I'm using Powerpro version 5.3.37h, downloaded from http://www.powerpro.cresadu.com. The developer is very active in supporting this program in a Yahoo Group.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 02:28:23 pm
That is interesting about HMPA and VS... I think I will buy a license and test to see what might be going on.  Thank you for letting me know!
It may be useful to see what HMPA may do in relation to VS.

However, I think that one should go back to the past when I stated (in a different forum) what I noticed almost at the very beginning of this problem, that is that VS did not cause any program to freeze in v.3.59. Since before VS v.3.59 I have been using an application toolbar called Powerpro which shows many commands and running programs as buttons on it. A program freezes (and I assume this is caused by VS), when I click on its corresponding toolbar button. The toolbar itself becomes unresponsive too, until I exit VS. In conclusion, I think there is an incompatibility between Powerpro and VS which results in running programs that are shown as buttons on the toolbar to freeze until I actually exit Voodooshield. I tested this by opening many programs not directly by using the toolbar menus, but from the Windows Start menu instead. There was no program freezing until I tried accessing (focusing on) any running programs using their respective toolbar buttons on Powerpro. The freezing problem went away (as usual) after I exited VS. Since you may ask, the frozen programs also become unfrozen if I exit Powerpro. This having been said, no program is frozen when VS is not running.
Cool, this will help a lot... can you please post a link to the exact version of Powerpro you are using, and let me know what browsers to test / debug with?  Please keep in mind that a lot has changed from VS 3 to 4, so there might be a couple of bugs that I have missed.  But if we work with specific examples like Powerpro, it should be quite easy to fix these last couple of bugs.  Thank you!

I'm using Powerpro version 5.3.37h, downloaded from http://www.powerpro.cresadu.com. The developer is very active in supporting this program in a Yahoo Group.
Very cool, thank you... I downloaded and installed 5.3.37h.  So now how do I reproduce the freeze?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 18, 2017, 02:40:16 pm
Cool, can you please let me know what program you are using to benchmark the startup items?  VS's service is tiny and should load very quickly, but I will take a look at it and make sure it is not running unnecessary code on startup.  Thank you!
It's a feature that comes with Wise Care 365 (found under System Tuneup/Speedup)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 18, 2017, 04:29:52 pm
Cool, can you please let me know what program you are using to benchmark the startup items?  VS's service is tiny and should load very quickly, but I will take a look at it and make sure it is not running unnecessary code on startup.  Thank you!
It's a feature that comes with Wise Care 365 (found under System Tuneup/Speedup)
Cool, thank you... I installed Wise Care 365, and here are the results.

https://voodooshield.co/artwork/WiseCare.PNG

I will look through the service code to see what might be slowing it down.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 18, 2017, 05:00:39 pm
@Dan
I reported this early last spring and mentioned again in early June at which time you wrote "Yeah, sorry about that, I will have this fixed soon... hopefully within a week, maybe sooner. Thank you"!. I also wrote about the issue continuing a couple of months later. I have reported in the past what happens in detail from a users point of view. All betas work fine in admin account. In order to get it to work in another account I first need to disable VS in admin, switch and re-enable. This is successful only with 3.59. The newer betas will only work in admin. When I switch accounts VS will open then quickly close. The errors have been related to MS Visual Basic and with latest betas, only typeinitialization. I have been not using VS for a week or more now. Thank you.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 18, 2017, 05:26:31 pm
Very cool, thank you... I downloaded and installed 5.3.37h.  So now how do I reproduce the freeze?
In the configuration settings click on the button "Properties" of the Bar, and a window titled "Command List Properties" will come up. Click on the "Active Buttons" tab and enable the "Show buttons for active windows" entry. This will show the active windows (running programs) at the end of the toolbar. Please refer to the attached image.

With VS running, try and switch from one program to another by clicking the respective button on the toolbar. You will probably see that at some point one of the programs will be frozen until you exit VS.

The attachment shows the relevant Powerpro settings on my PC.
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 18, 2017, 11:48:28 pm
... if anyone is having any kind of slowdown issue, can you please temporarily disable the "Automatically scan blocked files with VoodooAi" setting in VoodooShield Settings / Advanced, and let me know if the problem persists.  Also, you might try to temporarily disable the "Automatically scan blocked files with the mulit engine blacklist scanner" option to see if that makes a difference.

Hi Dan - 4.12b on W7x64 HP SP1 here, unchecked both of the above, and  :-* back to 3.59 snappiness :-*.  Checking only one of them produces a small gumminess, only a little annoying.  The test was staged with a full reboot between settings, and checking both common apps and those less used.

I wish I could comment on shutdown hangs, but those are mostly in the decisecond class, too short to wory about--the worst was around 3 seconds, maybe one in a hundred?  And in the blink of an eye, I can't tell if the AI/scan is affecting it or not.
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 18, 2017, 11:59:25 pm
@DanI have reported in the past what happens in detail from a users point of view. All betas work fine in admin account. In order to get it to work in another account I first need to disable VS in admin, switch and re-enable. This is successful only with 3.59. The newer betas will only work in admin. When I switch accounts VS will open then quickly close.

G'day Rainwalker - Forgive me, but a really dumb question: In the attachment, have you clicked on this button?

(I'll figure out how to do in-line images later.)

EDIT: Oh.  Wow!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 19, 2017, 03:13:10 am
G'day gorblimey- Yes, I had the same setting. Made no difference. Gorblimey, remember, there are no dumb questions  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 19, 2017, 04:22:31 pm
Cool, thank you... I installed Wise Care 365, and here are the results.

https://voodooshield.co/artwork/WiseCare.PNG

I will look through the service code to see what might be slowing it down.

WOW. I wish I had that result. Wondering if this is because I'm on a wi-fi connection...
Title: Re: VoodooShield v4 Beta Discussion
Post by: scootnod on December 19, 2017, 06:35:17 pm
Unchecking Automatically scan blocked files with VoodooAi for me was probably a 10 second difference. A lot faster. I still get an NVcontainerXyz message but doesn't affect anything.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 05:34:55 am
@Dan
I reported this early last spring and mentioned again in early June at which time you wrote "Yeah, sorry about that, I will have this fixed soon... hopefully within a week, maybe sooner. Thank you"!. I also wrote about the issue continuing a couple of months later. I have reported in the past what happens in detail from a users point of view. All betas work fine in admin account. In order to get it to work in another account I first need to disable VS in admin, switch and re-enable. This is successful only with 3.59. The newer betas will only work in admin. When I switch accounts VS will open then quickly close. The errors have been related to MS Visual Basic and with latest betas, only typeinitialization. I have been not using VS for a week or more now. Thank you.
Yeah, this really should be fixed... back then I rewrote all of the session code and spent tons of time on it so that it would work perfectly.  I believe no one else is having this issue, so I am thinking it is something very specific to your system.  Here are a couple of possibilities.   

1.  Do you happen to maybe have an old / manual startup entry for VS that should not be there?  You might leave VS uninstalled and run autoruns to check.

https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

2.  Also, after you uninstall VS, can you make sure that the VoodooShieldService is not listed as a service in services?

3.  If the first two items do not work out, can you please post the exact exception from the DeveloperLog.log?

4.  What OS are you running?  I can test again to make sure everything is working properly.

Thank you!

Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 05:38:02 am
Very cool, thank you... I downloaded and installed 5.3.37h.  So now how do I reproduce the freeze?
In the configuration settings click on the button "Properties" of the Bar, and a window titled "Command List Properties" will come up. Click on the "Active Buttons" tab and enable the "Show buttons for active windows" entry. This will show the active windows (running programs) at the end of the toolbar. Please refer to the attached image.

With VS running, try and switch from one program to another by clicking the respective button on the toolbar. You will probably see that at some point one of the programs will be frozen until you exit VS.

The attachment shows the relevant Powerpro settings on my PC.
I tried to reproduce the error... but it was difficult to make sure I was doing everything correctly.  I found and fixed a command line bug in VS (that would cause several different command line bugs), that I will release with the next version (soon).  If that does not fix it, maybe we can do a remote session, and you can remote in to one of my computers and show me how to reproduce the error?  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 05:46:19 am
... if anyone is having any kind of slowdown issue, can you please temporarily disable the "Automatically scan blocked files with VoodooAi" setting in VoodooShield Settings / Advanced, and let me know if the problem persists.  Also, you might try to temporarily disable the "Automatically scan blocked files with the mulit engine blacklist scanner" option to see if that makes a difference.

Hi Dan - 4.12b on W7x64 HP SP1 here, unchecked both of the above, and  :-* back to 3.59 snappiness :-*.  Checking only one of them produces a small gumminess, only a little annoying.  The test was staged with a full reboot between settings, and checking both common apps and those less used.

I wish I could comment on shutdown hangs, but those are mostly in the decisecond class, too short to wory about--the worst was around 3 seconds, maybe one in a hundred?  And in the blink of an eye, I can't tell if the AI/scan is affecting it or not.
Cool... yeah, see if an item is already whitelisted, it will not be scanned with VoodooAi or the blacklist, so it should not slow down at all for items that are already whitelisted.  If it is a new, non-whitelisted item, it will need to be scanned by both VoodooAi and the blacklist, which can take 2-5 seconds or so.

Also, VS 4.0 scans child processes of newly allowed items, so this will cause the same delay.  For example, if you run an installer, VS will scan all of the child processes automatically.  I added the scanning of child processes because some users were concerned with packed installers.

Having said that, if you notice a scan taking longer than usual, can you please check the bottom of the DeveloperLog.log to see if there are any exceptions?  There seems to be an intermittent error that I need to figure out... it is the same error that Telos was experiencing.

The shutdown issue is completely resolved with the next release ;).  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 05:49:35 am
Cool, thank you... I installed Wise Care 365, and here are the results.

https://voodooshield.co/artwork/WiseCare.PNG

I will look through the service code to see what might be slowing it down.

WOW. I wish I had that result. Wondering if this is because I'm on a wi-fi connection...
Hmmmm, great point... that might have been the problem with this issue and the others all along.  Tomorrow I will test with my laptop and see what happens.  If I can reproduce any given error, it is almost always extremely easy to fix... the hard part is accurately reproducing the error... the fix is usually less than 5 minutes.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 05:50:11 am
Unchecking Automatically scan blocked files with VoodooAi for me was probably a 10 second difference. A lot faster. I still get an NVcontainerXyz message but doesn't affect anything.
Very cool, thank you for letting me know.  Are you on wifi too?
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 20, 2017, 12:41:23 pm
Cool... yeah, see if an item is already whitelisted, it will not be scanned with VoodooAi or the blacklist, so it should not slow down at all for items that are already whitelisted.  If it is a new, non-whitelisted item, it will need to be scanned by both VoodooAi and the blacklist, which can take 2-5 seconds or so.

Also, VS 4.0 scans child processes of newly allowed items, so this will cause the same delay.  For example, if you run an installer, VS will scan all of the child processes automatically.  I added the scanning of child processes because some users were concerned with packed installers.

Having said that, if you notice a scan taking longer than usual, can you please check the bottom of the DeveloperLog.log to see if there are any exceptions?  There seems to be an intermittent error that I need to figure out... it is the same error that Telos was experiencing.

Hi Dan - Ummmm.  OK, I checked DeveloperLog.log for exceptions, there are none outside of December 10...  I'm about to email it to you.

However, I am puzzled by the number of Blacklisted Items Allowed, for example:
Code: [Select]
[12-07-2017 07:02:28] [INFO ] - Snapshot Allowed: org5.exe, c:\lotus\organize\org5.exe, c5b15d9e33482ad04f0678fd70908fe06b102180d444bcda5c5c23857ea46750

[12-07-2017 07:02:39] [INFO ] - Snapshot Allowed: org5.exe, c:\lotus\organize\org5.exe, c5b15d9e33482ad04f0678fd70908fe06b102180d444bcda5c5c23857ea46750

[12-07-2017 07:06:16] [INFO ] - Blacklisted Item allowed by parent process: c:\lotus\organize\org5.exe

[12-11-2017 16:44:23] [INFO ] - Blacklisted Item allowed by parent process: c:\lotus\organize\org5.exe

There are others, TedNPad, Cobbler...  FWIW, Lotus lives outside the Program Files as do several other apps, but TedNPad and Cobbler both have apartments in Program Files.

I was happily imagining that a Snapshot would result in Whitelisting...  Especially as I often do a Snapshot, and gracefully allow the Advanced Snapshot to be done as well.

Given that all programs were suffering a significant delay with Auto-scanning checked, I'm leaving both unchecked for the time being.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 20, 2017, 02:06:56 pm
I tried to reproduce the error... but it was difficult to make sure I was doing everything correctly.  I found and fixed a command line bug in VS (that would cause several different command line bugs), that I will release with the next version (soon).  If that does not fix it, maybe we can do a remote session, and you can remote in to one of my computers and show me how to reproduce the error?  Thank you!
Thanks Dan! I should mention that since I last made a posting here the program freezing only happened once. However, this is not necessarily good news, because I had a period in the past (with a different VS v.4x) when it was like that before the problem suddenly reappeared. Anyway, I'll wait for the newer VS version and we shall see.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 03:41:05 pm
Cool... yeah, see if an item is already whitelisted, it will not be scanned with VoodooAi or the blacklist, so it should not slow down at all for items that are already whitelisted.  If it is a new, non-whitelisted item, it will need to be scanned by both VoodooAi and the blacklist, which can take 2-5 seconds or so.

Also, VS 4.0 scans child processes of newly allowed items, so this will cause the same delay.  For example, if you run an installer, VS will scan all of the child processes automatically.  I added the scanning of child processes because some users were concerned with packed installers.

Having said that, if you notice a scan taking longer than usual, can you please check the bottom of the DeveloperLog.log to see if there are any exceptions?  There seems to be an intermittent error that I need to figure out... it is the same error that Telos was experiencing.

Hi Dan - Ummmm.  OK, I checked DeveloperLog.log for exceptions, there are none outside of December 10...  I'm about to email it to you.

However, I am puzzled by the number of Blacklisted Items Allowed, for example:
Code: [Select]
[12-07-2017 07:02:28] [INFO ] - Snapshot Allowed: org5.exe, c:\lotus\organize\org5.exe, c5b15d9e33482ad04f0678fd70908fe06b102180d444bcda5c5c23857ea46750

[12-07-2017 07:02:39] [INFO ] - Snapshot Allowed: org5.exe, c:\lotus\organize\org5.exe, c5b15d9e33482ad04f0678fd70908fe06b102180d444bcda5c5c23857ea46750

[12-07-2017 07:06:16] [INFO ] - Blacklisted Item allowed by parent process: c:\lotus\organize\org5.exe

[12-11-2017 16:44:23] [INFO ] - Blacklisted Item allowed by parent process: c:\lotus\organize\org5.exe

There are others, TedNPad, Cobbler...  FWIW, Lotus lives outside the Program Files as do several other apps, but TedNPad and Cobbler both have apartments in Program Files.

I was happily imagining that a Snapshot would result in Whitelisting...  Especially as I often do a Snapshot, and gracefully allow the Advanced Snapshot to be done as well.

Given that all programs were suffering a significant delay with Auto-scanning checked, I'm leaving both unchecked for the time being.
Sorry about that... I should explain VS's blacklist a little better.  The blacklist in VS is very different than a traditional AV blacklist.  In VS, what I mean by blacklist is that the item is not permanently whitelisted... but if the parent process is whitelisted, it can and will allow a blacklisted item (but it will not permanently whitelist the item).  For example, if a whitelisted program needs to run a command line, VS will not block the command line since the parent is whitelisted... BUT VS will not permanently whitelist cmd.exe, since it is a "blacklisted" item.  It is actually even more complex than this because it depends on other hardwired rules / behaviors. 

It actually becomes even more complex / cool / user-friendly when you factor in VS's toggling with web apps.  When the computer is at risk (and VS toggles to ON), these hardwired rules / behaviors are locked down, and VS does not take any unnecessary risks... basically if there is a doubt at all, VS is going to block the new item because the computer is at risk.  But if the computer is not at risk, a lot of the hardwired rules / behaviors are relaxed so that VS is able to automatically and silently build the tiny, customized whitelist for the user.  The only downside to this complexity is that it can lead to bugs in the software that take a while to identify, reproduce and fix... but if you are going to build a deny by default solution for the masses, we have no choice but to do the hard work that is necessary to make this happen.  Especially when the end result is a pre-execution, deny by default solution that has significantly less blocks than products with post-execution behavior blockers.

Some people who have underestimated the significance of VS's toggling are now starting to see what I have been talking about all along.  It really is quite simple... when the computer is at risk, it needs to be locked... and only items that were previously allowed (when the computer was not at risk) are allowed.  Then when the computer is no longer at risk, it is vital to reduce the security posture (while maintaining the necessary rules / behaviors), so that VS can automatically build the tiny, customized whitelist for the user... so that these items are not blocked once the computer is again at risk.

So basically, I can see where the DeveloperLog might be confusing at times, the only thing that really matters is that good stuff is auto allowed and bad stuff is blocked.  If you are seeing something that is being blocked that should not be, please let me know!

Also, can you guys please provide me some specific examples (along with download links of the exact versions you are running), of programs that experience the "scan delay" from VoodooAi and the blacklist?  I think if we work from specific examples, we can reproduce and fix this bug much quicker.  If so, can you provide some that live in Program Files, and some that do not?  I will also test with wifi today... I think that might have something to do with it as well.

Thank you guys!

Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 03:43:59 pm
I tried to reproduce the error... but it was difficult to make sure I was doing everything correctly.  I found and fixed a command line bug in VS (that would cause several different command line bugs), that I will release with the next version (soon).  If that does not fix it, maybe we can do a remote session, and you can remote in to one of my computers and show me how to reproduce the error?  Thank you!
Thanks Dan! I should mention that since I last made a posting here the program freezing only happened once. However, this is not necessarily good news, because I had a period in the past (with a different VS v.4x) when it was like that before the problem suddenly reappeared. Anyway, I'll wait for the newer VS version and we shall see.
Very cool... thank you.  I was going to wait to see if we can fix the "scan delay" bug before releasing the next version, but this is probably going to take a couple of days, so I will release the next version in a couple of hours.  Hopefully the command line fix will fix your issue... the shutdown issue is fixed, along with a couple of other small issues.  Please let me know how it does!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 06:50:48 pm
Here is 4.14b... the shutdown and command line issues should all be fixed.

I am going to focus on the intermittent internet / VPN "scan delay" issue.  Although I will say, I have tried several VPN's and a lot of softs (like Outlook, Visual Studio (in general)) do not work correctly with several of the VPN's that I have tried.  So it might not be that straightforward.

www.voodooshield.co/Download/InstallVoodooShield414beta.exe

Thank you guys!
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 20, 2017, 07:07:03 pm
I did a clean install of V4.14b on Win 7. Shutdown all fixed at this end. Thanks for the fix Dan, working good now. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 20, 2017, 07:23:57 pm
I did a clean install of V4.14b on Win 7. Shutdown all fixed at this end. Thanks for the fix Dan, working good now. :)
Very cool, thank you for letting me know... we are getting there!

BTW, if someone is running 3.59 and is experiencing the Windows 10 dismhost issue, please upgrade to 4.14b, this will fix the issue.

Here is the deal... VS 3.59 is installed on a lot of small to medium sized business endpoints, and most of them are not running the latest version of Windows 10 (most of them run Windows 7)... which is the cause of the dismhost issue, since it has not been updated in 3.59.  Since we are about to release 4.0 to the public, it would not be cool to force entire companies to upgrade twice in a row... they would be quite upset.

Patients is a virtue.
Title: Re: VoodooShield v4 Beta Discussion
Post by: hayc59 on December 20, 2017, 07:32:23 pm
I did a clean install of V4.14b on Win 7. Shutdown all fixed at this end. Thanks for the fix Dan, working good now. :)
Very cool, thank you for letting me know... we are getting there!

BTW, if someone is running 3.59 and is experiencing the Windows 10 dismhost issue, please upgrade to 4.14b, this will fix the issue.

Here is the deal... VS 3.59 is installed on a lot of small to medium sized business endpoints, and most of them are not running the latest version of Windows 10 (most of them run Windows 7)... which is the cause of the dismhost issue, since it has not been updated in 3.59.  Since we are about to release 4.0 to the public, it would not be cool to force entire companies to upgrade twice in a row... they would be quite upset.

Patients is a virtue.
Amen to that brother!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 20, 2017, 07:45:43 pm
I just installed the latest beta, over the top:



Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 20, 2017, 07:56:03 pm
"1.  Do you happen to maybe have an old / manual startup entry for VS that should not be there?  You might leave VS uninstalled and run autoruns to check.

https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

2.  Also, after you uninstall VS, can you make sure that the VoodooShieldService is not listed as a service in services?

3.  If the first two items do not work out, can you please post the exact exception from the DeveloperLog.log?

4.  What OS are you running?  I can test again to make sure everything is working properly".

Thanks for getting back Dan. None of the above is an issue with me. Win7/64. I have thought for sometime the problem is with my system. I can live with 3.59 should I decide to re-install it. Thanks again.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 20, 2017, 08:17:04 pm
Here is 4.14b... the shutdown and command line issues should all be fixed.

I am going to focus on the intermittent internet / VPN "scan delay" issue.  Although I will say, I have tried several VPN's and a lot of softs (like Outlook, Visual Studio (in general)) do not work correctly with several of the VPN's that I have tried.  So it might not be that straightforward.

www.voodooshield.co/Download/InstallVoodooShield414beta.exe

Thank you guys!

Thanks a lot Dan. Installed over the top and no problem to report so far. Good job! :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 20, 2017, 10:44:47 pm
Thank you Dan.
I have just updated it over the top with no problems at all, it is all running well.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Denis on December 20, 2017, 11:00:38 pm
Plus 1 Dan 8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 20, 2017, 11:20:31 pm
Hi to everyone...

I just registered on this forum ( thanks Dan for invite )  :D

Installed new beta 4.14b and all working fine!


Windows 10 pro x64 f.c.u.
Windows Defender
Title: Re: VoodooShield v4 Beta Discussion
Post by: ssherjj on December 20, 2017, 11:40:41 pm
Here is 4.14b... the shutdown and command line issues should all be fixed.

I am going to focus on the intermittent internet / VPN "scan delay" issue.  Although I will say, I have tried several VPN's and a lot of softs (like Outlook, Visual Studio (in general)) do not work correctly with several of the VPN's that I have tried.  So it might not be that straightforward.

www.voodooshield.co/Download/InstallVoodooShield414beta.exe

Thank you guys!

Thank you Dan, I have updated.

I am having an issue with VoodooShields not turning blue when on the internet. I have it set to SMART (default) It stays red. So I have to run VS in AUTO PILOT or ALWAYS ON for VS to change to blue? Am I doing something wrong in the settings?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 20, 2017, 11:58:13 pm
Here is 4.14b... the shutdown and command line issues should all be fixed.

I am going to focus on the intermittent internet / VPN "scan delay" issue.  Although I will say, I have tried several VPN's and a lot of softs (like Outlook, Visual Studio (in general)) do not work correctly with several of the VPN's that I have tried.  So it might not be that straightforward.

www.voodooshield.co/Download/InstallVoodooShield414beta.exe

Thank you guys!

Thank you Dan, I have updated.

I am having an issue with VoodooShields not turning blue when on the internet. I have it set to SMART (default) It stays red. So I have to run VS in AUTO PILOT or ALWAYS ON for VS to change to blue? Am I doing something wrong in the Settings perhaps?

What browser do you use?
Maybe it is not in "web apps list"
Try this:


Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 21, 2017, 12:36:50 am
BTW, if someone is running 3.59 and is experiencing the Windows 10 dismhost issue, please upgrade to 4.14b, this will fix the issue.
Confirmed. Thank you.
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 21, 2017, 01:53:44 am
Tada, good for you mister, it's running snappy both at boot up and down, only thing I can report is that the tray icon is not joining the party, 3 reboots and shutdowns and a no show. Have a nice Christmas Dan.

Merry Christmas too all of you here at Calendar of Updates. :) All the best.

Edit: Tray icon is working correctly this morning. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 21, 2017, 02:46:52 am
Just downloaded 4.14b...  SHA256: 33b3616d3efeb7ddca5dfc04c6c4ba1364620bedeee784176864e7e6a1cde654 yes?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 21, 2017, 03:01:19 am
Yes, it is. :) 
  https://www.virustotal.com/en/file/33b3616d3efeb7ddca5dfc04c6c4ba1364620bedeee784176864e7e6a1cde654/analysis/1513797812/
Title: Re: VoodooShield v4 Beta Discussion
Post by: Flyingdog on December 21, 2017, 03:29:28 am
Dan,
Installed over the top on both machines and everything is running well.
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 21, 2017, 05:01:46 am
Yes, it is. :)

:D
Title: Re: VoodooShield v4 Beta Discussion
Post by: ssherjj on December 21, 2017, 02:30:25 pm
Here is 4.14b... the shutdown and command line issues should all be fixed.

I am going to focus on the intermittent internet / VPN "scan delay" issue.  Although I will say, I have tried several VPN's and a lot of softs (like Outlook, Visual Studio (in general)) do not work correctly with several of the VPN's that I have tried.  So it might not be that straightforward.

www.voodooshield.co/Download/InstallVoodooShield414beta.exe

Thank you guys!

Thank you Dan, I have updated.

I am having an issue with VoodooShields not turning blue when on the internet. I have it set to SMART (default) It stays red. So I have to run VS in AUTO PILOT or ALWAYS ON for VS to change to blue? Am I doing something wrong in the Settings perhaps?

What browser do you use?
Maybe it is not in "web apps list"
Try this:

Thank you so much ..that did the trick! I use Firefox... I also did not have Firefox checked...not sure why it wasn't.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 21, 2017, 05:17:24 pm
VS 4.14b flagged c:\windows\system32\rundll32.exe startupscan.dll,susruntask and blocked it. Should it be blocked or is this a false positive?
Title: Re: VoodooShield v4 Beta Discussion
Post by: fax on December 21, 2017, 06:12:32 pm
Sorry I am joining late the party ;D ...updated to 4.14b and, so far, all is fine.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 21, 2017, 08:10:29 pm
VS 4.14b flagged c:\windows\system32\rundll32.exe startupscan.dll,susruntask and blocked it. Should it be blocked or is this a false positive?


I have that command line, and it is allowed.  Don't ask me why it was created, because I don't know. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 21, 2017, 08:29:00 pm
OK, thanks Tarnak, so I guess this susruntask thing is nothing to worry about. Thanks for reply. Much appreciated. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 21, 2017, 08:30:50 pm
Is WebClient service required for VS to function properly?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on December 21, 2017, 08:31:24 pm
VS 4.14b flagged c:\windows\system32\rundll32.exe startupscan.dll,susruntask and blocked it. Should it be blocked or is this a false positive?


I have that command line, and it is allowed.  Don't ask me why it was created, because I don't know. ;)
If I understand the info in this webpage it's part of windows 10 automatic maintenance:
https://superuser.com/questions/884839/windows-8-1-automatic-maintenance-whats-really-going-on-under-the-hood
The best info i could find...
It's enabled on my laptop.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 21, 2017, 08:53:11 pm
Thanks, Gandalf. So I guess it's nothing malicious, and it can therefore be allowed.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 21, 2017, 08:56:05 pm
OK, thanks Tarnak, so I guess this susruntask thing is nothing to worry about. Thanks for reply. Much appreciated. :)

You're welcome. :)

P.S. Also, thanks to Gandolf for his subsequent post. He has enlightened us, both. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mr.GumP on December 22, 2017, 12:37:54 am
4.14b working great on Windows 10 Home 64bit
Title: Re: VoodooShield v4 Beta Discussion
Post by: djg05 on December 22, 2017, 09:27:39 am
4.14 installed over the top yesterday. So far no problems have arisen.

Have a good Christmas Dan and get a bit of time with Molly.


Regards

David
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 22, 2017, 11:49:05 am
Hey Dan, it seems we are getting close to the final version :) Thank you for your hard work and Merry Christmas!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 22, 2017, 11:58:31 am
VoodooAi: Error?

Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 22, 2017, 02:12:51 pm
I installed v.4.14b over the previous beta. No problems so far, especially no program freezing as has been my recent experience.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 22, 2017, 09:43:18 pm
Installed 14b and also got the command line blocked. Also was wondering about the GUI.
 When I look in User Log it shows red = blocked but when I look in command lines it shows Zero blocked.


EDIT: after returning home after a few hours, VS the blocked disappeared and was replaced with allowed. See screen shots.

Title: Re: VoodooShield v4 Beta Discussion
Post by: scootnod on December 22, 2017, 09:44:41 pm
so dont download peerblock?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 23, 2017, 12:38:27 am
so dont download peerblock?

Why not?
1.Download legit version of program
2.Threat NOT DETECTED in 67 scan engines
3.Windows Defender also quiet

VoodooAI was unable (for some reason) to check the file and give feedback so this issue I was try to adress!
PeerBlock is irrelevant here.
 ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 23, 2017, 12:49:36 am
Well, I just found out what PeerBlock is used for: "PeerBlock is a popular 'solution' for downloading torrents safely, largely because it's free."

I don't think it's for me. Just saying. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 23, 2017, 12:57:49 am
I don't think it's for me. Just saying. :)
+1 Just saying.
PS: Hi, Tarnak. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 23, 2017, 01:03:08 am
Well, I just found out what PeerBlock is used for: "PeerBlock is a popular 'solution' for downloading torrents safely, largely because it's free."

I don't think it's for me. Just saying. :)

From time to time I download stuff from torrents and this little bugger is just what I need  ;)

I uninstalled it later but like I say, he is unimportant here!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 23, 2017, 01:09:20 am
I don't think it's for me. Just saying. :)
+1 Just saying.
PS: Hi, Tarnak. :)

Hey, Hi to you, too. We are posting in a particular thread at Wilder's right now, too. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 23, 2017, 05:55:17 pm
4.14b  Very nice  Dan
Thanks again for your generosity!
Have a safe Festive season! 8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Alexhousek on December 23, 2017, 08:08:52 pm
For those of us who are still running 3.59 and are thinking about making the plunge to 4.14b, what are the recommendations?  Should we install over-top or should we uninstall, reboot, and then install 4.14b?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 23, 2017, 08:23:18 pm
For those of us who are still running 3.59 and are thinking about making the plunge to 4.14b, what are the recommendations?  Should we install over-top or should we uninstall, reboot, and then install 4.14b?

In my oppinion is better that you uninstall old version!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 23, 2017, 08:29:47 pm
In my oppinion is better that you uninstall old version!
This is what I did, just to be on the safe side.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 24, 2017, 03:51:55 pm
For those of us who are still running 3.59 and are thinking about making the plunge to 4.14b, what are the recommendations?  Should we install over-top or should we uninstall, reboot, and then install 4.14b?

Uninstall 3.59 and any remnants.
Install 4.14b (you will have to enter registration info)
Enjoy.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 25, 2017, 01:08:05 am
@Dan... What are the required Services for VS? Win7/64. Thank you.
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on December 25, 2017, 03:24:26 am
What are the required Services for VS? Win7/64.

Hi @Rainwalker - VS Service has no dependencies either way in 7x64--at least on my box :), and I checked as Admin.  Its path is "C:\Program Files\VoodooShield\VoodooShieldService.exe".

OFF TOPIC: Please drive safely, your loved ones want you home in one piece 8)  And in West Oz, we're on double demerits...  :(
ON TOPIC
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 25, 2017, 03:36:23 pm
OK thanks gorblimey. Had to be sure in that I have me services seriously tweaked from default. Enjoy the rest of you Christmas.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:11:16 pm
Merry Christmas everyone!  Sorry I have been away… I have been merging the databases and getting everything ready for the public release.

This version (4.15) is using the final merged database on the final database server, so hopefully everything will work correctly.

Hopefully all of the accounts are correct, but if something is not right, please email me at support at voodooshield.com!  There will be quite a few accounts where your endpoint quantity (number of licenses) is less than what it should be, so if this is the case, shoot me a quick email and let me know how many you need.  Or if your account is missing altogether, shoot me an email as well.

If something goes wrong, you can always reinstall 4.14b... it is using the old database.

www.voodooshield.co/Download/InstallVoodooShield415.exe

Thanks again for all of your help, Merry Christmas and Happy New Year!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:12:47 pm
@Dan... What are the required Services for VS? Win7/64. Thank you.
Yeah, there should not be any service dependencies... could it possibly be something .net related?  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:14:53 pm
VoodooAi: Error?
Hmmm, that is odd... thank you for letting me know!

Is it only PeerBlock that has a VoodooAi error?  Or only files from your D drive?

This should be pretty easy to reproduce and fix.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:16:08 pm
Installed 14b and also got the command line blocked. Also was wondering about the GUI.
 When I look in User Log it shows red = blocked but when I look in command lines it shows Zero blocked.


EDIT: after returning home after a few hours, VS the blocked disappeared and was replaced with allowed. See screen shots.
Yeah, that one command line is a real pain... it is even hardwired in, and it still does that.  If we can figure out what is triggering that command line, we can reproduce and fix it easily.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:17:52 pm
VS 4.14b flagged c:\windows\system32\rundll32.exe startupscan.dll,susruntask and blocked it. Should it be blocked or is this a false positive?
Yeah... that is the one command line that is a real pain, you can allow it.  Let me see what I can do, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:21:00 pm
Is WebClient service required for VS to function properly?
Well, my WebClient service is stopped and VS is working normally, so I do not think this is causing the issue.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:23:22 pm
I just finished reading through the posts that I missed... please let me know if I missed any others.

It is great to see the "old guys" that have been with VS for years now, along with the "new guys" who recently discovered VS!

Merry Christmas!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 04:23:55 pm
Can I install v4.15 on top of v4.14 or should the previous VS version be uninstalled first?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 04:25:09 pm
It is great to see the "old guys" that have been with VS for years now, along with the "new guys" who recently discovered VS!
Merry Christmas!
Merry Christmas from one of the "new guys". ;D
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on December 25, 2017, 04:30:51 pm
Merry Christmas everyone!  Sorry I have been away… I have been merging the databases and getting everything ready for the public release.

This version (4.15) is using the final merged database on the final database server, so hopefully everything will work correctly.

Hopefully all of the accounts are correct, but if something is not right, please email me at support at voodooshield.com!  There will be quite a few accounts where your endpoint quantity (number of licenses) is less than what it should be, so if this is the case, shoot me a quick email and let me know how many you need.  Or if your account is missing altogether, shoot me an email as well.

If something goes wrong, you can always reinstall 4.14b... it is using the old database.

www.voodooshield.co/Download/InstallVoodooShield415.exe

Thanks again for all of your help, Merry Christmas and Happy New Year!
Did a clean install of version 4.15. So far so good.
I have less time at the moment to test because I have to visit my father who is in hospital this Christmas  :(
Many thanks for your amazing program and support. Merry Christmas and Happy New Year to all!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 04:33:18 pm
VS 4.14b flagged c:\windows\system32\rundll32.exe startupscan.dll,susruntask and blocked it. Should it be blocked or is this a false positive?
Yeah... that is the one command line that is a real pain, you can allow it.  Let me see what I can do, thank you!
Cool. Thank you. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:33:32 pm
It is great to see the "old guys" that have been with VS for years now, along with the "new guys" who recently discovered VS!
Merry Christmas!
Merry Christmas from one of the "new guys". ;D
Thank you!  You can just install over the top... but if something were to go wrong, please do what Telos suggested in post 209.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 04:35:34 pm
OK, I'll first try an over-the-top install of the new version. Thank you.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 04:35:49 pm
Merry Christmas everyone!  Sorry I have been away… I have been merging the databases and getting everything ready for the public release.

This version (4.15) is using the final merged database on the final database server, so hopefully everything will work correctly.

Hopefully all of the accounts are correct, but if something is not right, please email me at support at voodooshield.com!  There will be quite a few accounts where your endpoint quantity (number of licenses) is less than what it should be, so if this is the case, shoot me a quick email and let me know how many you need.  Or if your account is missing altogether, shoot me an email as well.

If something goes wrong, you can always reinstall 4.14b... it is using the old database.

www.voodooshield.co/Download/InstallVoodooShield415.exe

Thanks again for all of your help, Merry Christmas and Happy New Year!
Did a clean install of version 4.15. So far so good.
I have less time at the moment to test because I have to visit my father who is in hospital this Christmas  :(
Many thanks for your amazing program and support. Merry Christmas and Happy New Year to all!
Thank you Gandalf, I wish you and your father the best this Christmas.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 04:53:14 pm
I tried to install over top, which froze my computer. Then I tried a clean install, which was not successful either because I'm told that the total number of license activations has been reached. I guess I will have to write an e-mail to VS support. :(

Edit: My e-mail is on its way to VS support. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 05:07:53 pm
I tried to install over top, which froze my computer. Then I tried a clean install, which was not successful either because I'm told that the total number of license activations has been reached. I guess I will have to write an e-mail to VS support. :(

Edit: My e-mail is on its way to VS support. :)
I forgot to mention, you need to exit out of VS before installing the new version.  The updater is now active for the next version, so this will not be an issue moving forward.

For some reason, your account was in our database twice, but it is fixed now.  If anyone else has this kind of problem, please email me at support at voodooshield.com, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 25, 2017, 05:09:12 pm
@Dan... What are the required Services for VS? Win7/64. Thank you.
BTW... if you try VS 415 and it still does not work, can you email me (or post on here) the exact exception / error?  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 25, 2017, 05:17:50 pm
I forgot to mention, you need to exit out of VS before installing the new version.

I did but installing over the old version didn't work here.

For some reason, your account was in our database twice, but it is fixed now. 

Confirmed. I only lost one day (license was valid until 17 Dec 2020 with v4.14, with v4.15 it is valid only until 16 Dec 2020).
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 25, 2017, 05:50:24 pm
Installed 415 over 4.14b
Very smooth and so far, no issues that I've noticed
Title: Re: VoodooShield v4 Beta Discussion
Post by: Flyingdog on December 25, 2017, 06:22:15 pm
Did a clean install of 415. Everything is running fine and no registration issues.
Thanks Dan.
Title: Re: VoodooShield v4 Beta Discussion
Post by: pavo on December 25, 2017, 07:10:18 pm
4.15 here and everything is up and running. No issues so far.
Merry Christmas Dan!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 25, 2017, 07:22:49 pm
VoodooAi: Error?
Hmmm, that is odd... thank you for letting me know!

Is it only PeerBlock that has a VoodooAi error?  Or only files from your D drive?

This should be pretty easy to reproduce and fix.  Thank you!

This is only Error that I got. I uninstalled PeerBlock later.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 25, 2017, 09:07:02 pm
Updated to 4.15 over the top. No problems. Merry Christmas. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: hayc59 on December 25, 2017, 09:59:12 pm
Installed latest version on my laptop(windows seven) and all is smokin, thank you
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 25, 2017, 10:51:28 pm
WOW...ya fixed it Dan. At least it is working as it should be at the moment. Did receive a notice with this latest beta informing me my usage allowance or something to that effect has run out. As I was writing this VS crashed with this error...........   Problem Signature 09:   System.TypeInitialization. I was able to restart it without closing and reopening browser. I will keep you informed. Thank you. Enjoy the holidays.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 26, 2017, 12:43:47 am
I'm just having a closer look at v4.15. When I click the button "Update Check", I get the following message:

An internet connection was not detected.
Please ensure that you are connected to the internet to check for an update.


I am connected to the internet, and neither VS nor VS Service.exe is blocked by my firewall. I know I'm using the latest version, but I would have expected a message that tells me that updates are currently not available or something along those lines. Telling me I'm not connected to the internet, however, is something I did not expect. :o
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 26, 2017, 01:19:02 am
I'm just having a closer look at v4.15. When I click the button "Update Check", I get the following message:

An internet connection was not detected.
Please ensure that you are connected to the internet to check for an update.


I am connected to the internet, and neither VS nor VS Service.exe is blocked by my firewall. I know I'm using the latest version, but I would have expected a message that tells me that updates are currently not available or something along those lines. Telling me I'm not connected to the internet, however, is something I did not expect. :o
Win 7 here, I get running the latest version of VoodooShield after clicking the update check.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 26, 2017, 01:49:07 am
Thanks for checking. I still get the weird message I posted above. Hm...
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 26, 2017, 02:07:36 am
I uninstalled, rebooted my computer and reinstalled VS 4.15 - same result. I cannot even right-click an app to scan it with VS. According to VS, I am not connected to the internet. Uninstalled Voodooshield for now. :-[
Title: Re: VoodooShield v4 Beta Discussion
Post by: pavo on December 26, 2017, 07:57:20 am
I'm just having a closer look at v4.15. When I click the button "Update Check", I get the following message:

An internet connection was not detected.
Please ensure that you are connected to the internet to check for an update.


I am connected to the internet, and neither VS nor VS Service.exe is blocked by my firewall. I know I'm using the latest version, but I would have expected a message that tells me that updates are currently not available or something along those lines. Telling me I'm not connected to the internet, however, is something I did not expect. :o
Win 7 here, I get running the latest version of VoodooShield after clicking the update check.
Win 10 x64 - no problems with update check as I also got the message about running the latest version after manual update check.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on December 26, 2017, 09:54:57 am
Merry Christmas everyone!  Sorry I have been away… I have been merging the databases and getting everything ready for the public release.

This version (4.15) is using the final merged database on the final database server, so hopefully everything will work correctly.

Hopefully all of the accounts are correct, but if something is not right, please email me at support at voodooshield.com!  There will be quite a few accounts where your endpoint quantity (number of licenses) is less than what it should be, so if this is the case, shoot me a quick email and let me know how many you need.  Or if your account is missing altogether, shoot me an email as well.

If something goes wrong, you can always reinstall 4.14b... it is using the old database.

www.voodooshield.co/Download/InstallVoodooShield415.exe

Thanks again for all of your help, Merry Christmas and Happy New Year!
Did a clean install of version 4.15. So far so good.
I have less time at the moment to test because I have to visit my father who is in hospital this Christmas  :(
Many thanks for your amazing program and support. Merry Christmas and Happy New Year to all!
Thank you Gandalf, I wish you and your father the best this Christmas.
Thanks Dan.
On the registration tab I see:
Thank you for choosing VoodooShield Pro! Your subscription expired on 1-1-0001.
When I log in to the Web Management Console I see that my account expires on 08/07/2019.
Something not right with my account?
I have sent an email to support at voodooshield.com.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 26, 2017, 11:14:40 am
I'm still on v4.14 and I try to "check for updates" from "settings" but it tell me that I have the latest version???

Is that kind of check are working only for "stable releases" but not for "Betas"?


Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 26, 2017, 11:19:42 am
It would be also nice that I can see what are those files that Voodoo was blocked...

Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 26, 2017, 03:01:47 pm
It would be also nice that I can see what are those files that Voodoo was blocked...
See User Log...
(http://cloud.screenpresso.com/6DTI/2017-12-26_09h58_34.png)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 26, 2017, 03:10:25 pm
Hey guys, I wanted to mention really quick... I am having a few issues with the new database, but it should be fixed and up and running in the next 20 minutes or so.  During this time you might experience a few odd issues, but I hope everything will be resolved soon.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 26, 2017, 03:31:21 pm
Ok, we should be good to go, please let me know if you guys have any other issues... I will catch up soon, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 26, 2017, 04:10:41 pm
Ok, we should be good to go, please let me know if you guys have any other issues... I will catch up soon, thank you!
A few hours ago when I looked at the VS GUI I had an extra year to the license. Now I look at the GUI and and it's back to what it was, expires in about 90 days. Also when I look at the Management Console nothing is filled in, it's blank, everything gone even devices. It was filled in last week when I looked.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 26, 2017, 04:44:06 pm
Ok, we should be good to go, please let me know if you guys have any other issues... I will catch up soon, thank you!
A few hours ago when I looked at the VS GUI I had an extra year to the license. Now I look at the GUI and and it's back to what it was, expires in about 90 days. Also when I look at the Management Console nothing is filled in, it's blank, everything gone even devices. It was filled in last week when I looked.
Sorry about that... yeah, that is the main problem we are experiencing (the management console is reading from the old database), I hope to have it resolved in the next hour or so.
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 26, 2017, 05:59:55 pm
After upgrading to 4.15, I think I'm a year short but I've been known to be wrong..    ;)

Dan, Also I should mention  I just went through ' Web management console' and when I viewed my account I noticed the Username and Email was not me??
Something weird for sure ???
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 26, 2017, 06:54:26 pm
I have not been able to fix the web server issues (I am not great with web server stuff), so Alex is going to take a look at it ASAP... sorry for the delay.

For now, there is no reason to log into the management console... it is not working properly, but it should be fixed soon.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 26, 2017, 07:05:14 pm
I have not been able to fix the web server issues (I am not great with web server stuff), so Alex is going to take a look at it ASAP... sorry for the delay.

For now, there is no reason to log into the management console... it is not working properly, but it should be fixed soon.  Thank you!

Thanks, no worries
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 26, 2017, 07:35:00 pm
I have not been able to fix the web server issues (I am not great with web server stuff), so Alex is going to take a look at it ASAP... sorry for the delay.

For now, there is no reason to log into the management console... it is not working properly, but it should be fixed soon.  Thank you!
No worries buddy.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 26, 2017, 08:15:18 pm
Thank you for keeping us informed Dan.
Mine currently says that it has expired on 01/01/0001 but I will check again when everything is working properly.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 12:31:12 am
Sure, thank you guys!  Yeah, it is going to be all wacky until Alex fixes it... it shouldn't take him long.

Once we think it is fixed, everyone who has an account can check to see if everything is right, and if something is wrong, I will be happy to fix it.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 27, 2017, 12:38:26 am
Thank you Dan.  ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mx on December 27, 2017, 02:35:48 am
Hi,

If I have VS I need OSArmor?

Thanks.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 03:42:11 am
Hi,

If I have VS I need OSArmor?

Thanks.
That depends… OSArmor is extremely lightweight and NVT are great coders who write amazing software, and it should be completely compatible with VS, so it certainly would not hurt.

When VS toggles to ON, it should easily block everything that is not already whitelisted… the computer is locked down since it is at risk, so very few hardwired “allow” rules are required.  As I always say, “There is never a good reason to let new, non-whitelisted executable code run while a web app is running.”

When VS toggles to OFF (or is on AutoPilot), it is essentially performing either identical or similar functions as OSArmor, or functions that are handled by a different method.

Since when VS is ON the computer is locked down, what we really need to do is compare OSArmor to VS when it is OFF or on AutoPilot.  VS has had its own hardwired rules that I have added and refined for several years now… I always try to explain to people that there is a lot more going on under then hood than they imagine.

Hopefully I did not forget any vital hardwired rules… but this would be a great opportunity for people to see if they can bypass VS, by testing OSArmor’s rules against VS.  Just please keep in mind that usability is the key for deny by default products, so VS applies rules differently, depending on the toggle state.  That is, if VS can auto allow certain items when it is OFF (or on AutoPilot), and automatically lock the computer when it is at risk, that is the optimal scenario.

On a side note… for years trolls have been giving me c*&# about our anti-exploit feature that I created years ago… I am happy that it has now been implemented in another security product and therefore validated as significant and useful ;).

I read on one of the forums that ERP and OSArmor would be an interesting combo… or something to that affect.  Think how magical that would be if the computer automatically locked when it was at risk, and applied different rules based on the toggling ;).

If only a product like that existed ;).
Title: Re: VoodooShield v4 Beta Discussion
Post by: hayc59 on December 27, 2017, 04:00:10 am
Mx hello, Some folks say they are great together like peas and carrots
Title: Re: VoodooShield v4 Beta Discussion
Post by: hayc59 on December 27, 2017, 04:01:09 am
Dan please read pm :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 04:13:59 am
Mx hello, Some folks say they are great together like peas and carrots
Yeah, I can certainly see where a lot of people might really like that combo, in case I forgot a rule when VS is OFF or on AutoPilot.  I have been saying for years now that I am certain that there is not a chance that I covered every single possible attack.  So yeah, they are probably a great combo... I might even install OSArmor on my main computer just for the heck of it ;).

Also, please keep in mind, and this is not a knock against NVT or VS, but both products hardwired rules are not proprietary and can be implemented into any security product... many of them probably already have been implemented in several other products.

My ONLY goal all along has been to lock the computer when it is at risk, which is proprietary, patented, and can be added to pretty much any security product.

It would be quite compelling for any major cybersecurity vendor to be able to claim that their product automatically locks the computer when the user is surfing the web or checking email, and then automatically unlocks when it is no longer at risk.  Basically "we are going to offer you the same great protection that we always have, but now we are also going to start locking the computer when it is at risk.  And we are going to provide you a tangible, user-friendly desktop shield gadget lock".

The security industry has completely rejected the full time lockdown approach... but that is not a good enough excuse to not lock the computer when it is at risk ;).

Which is why I always say... just lock the computer when it is at risk.
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 27, 2017, 05:31:15 am
installed 4.15 over 4.14b after disabling and closing 4.14b, and 4.15 seems aok after 2 days running, have not checked the console yet, waiting for server fix per Dan.

PS some savvy foiks at MT are waiting for OSarmor to "ripen" a little before they install it.  NVT has been doing a lot of work to osa from what I can see. Waiting for a more polished version with some "needed" features. 
Title: Re: VoodooShield v4 Beta Discussion
Post by: Jasper The Rasper on December 27, 2017, 11:14:17 am
Sure, thank you guys!  Yeah, it is going to be all wacky until Alex fixes it... it shouldn't take him long.

Once we think it is fixed, everyone who has an account can check to see if everything is right, and if something is wrong, I will be happy to fix it.

I have just checked my installation and it appears to be correct with the installation date now Dan, give my thanks to Alex please.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Schank873-2 on December 27, 2017, 01:51:12 pm
VS 4.15 working great with EAM, HMPro and HMPro.Alert...no slow-downs...no hiccups.....thanks Dan
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 01:54:35 pm
Sure, thank you guys!  Yeah, it is going to be all wacky until Alex fixes it... it shouldn't take him long.

Once we think it is fixed, everyone who has an account can check to see if everything is right, and if something is wrong, I will be happy to fix it.

I have just checked my installation and it appears to be correct with the installation date now Dan, give my thanks to Alex please.
I am not sure if he has fixed it yet or not (typically he emails me when he starts to work on something)... you might have just closed VS and opened it again, that will fix it temporarily.  I just do not want to give people the wrong impression if it is not fixed yet.

But either way, I will certainly be thanking him for fixing the issue, and I will let you guys know when I hear from him and the issue is fixed.  Thank you!

Great to hear Schank873-2!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 27, 2017, 05:36:52 pm
@Dan... What happens when we tick the box "Report False Positive"?  ...just curious.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 27, 2017, 05:37:23 pm
I have a VS license that is valid until December 2020. I don't need it any more. No, I don't want a refund. I would like to give it away to someone who may need it (e.g. to some friendly guy who is also a member here). Is this possible?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 27, 2017, 05:52:28 pm
It seems like new users get confused by the red color of the VS shield/icon, it makes them think that protection is disabled.
I suggest that the color should toggle between blue and green, rather than between red and blue. That would give a more accurate visual representation of the protection level.
My apologies in advance if this issue was already discussed to death once upon a time, in some other forum. If so, please just ignore my comment.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mx on December 27, 2017, 05:58:54 pm
Hi,

If I have VS I need OSArmor?

Thanks.
That depends… OSArmor is extremely lightweight and NVT are great coders who write amazing software, and it should be completely compatible with VS, so it certainly would not hurt.

When VS toggles to ON, it should easily block everything that is not already whitelisted… the computer is locked down since it is at risk, so very few hardwired “allow” rules are required.  As I always say, “There is never a good reason to let new, non-whitelisted executable code run while a web app is running.”

When VS toggles to OFF (or is on AutoPilot), it is essentially performing either identical or similar functions as OSArmor, or functions that are handled by a different method.

Since when VS is ON the computer is locked down, what we really need to do is compare OSArmor to VS when it is OFF or on AutoPilot.  VS has had its own hardwired rules that I have added and refined for several years now… I always try to explain to people that there is a lot more going on under then hood than they imagine.

Hopefully I did not forget any vital hardwired rules… but this would be a great opportunity for people to see if they can bypass VS, by testing OSArmor’s rules against VS.  Just please keep in mind that usability is the key for deny by default products, so VS applies rules differently, depending on the toggle state.  That is, if VS can auto allow certain items when it is OFF (or on AutoPilot), and automatically lock the computer when it is at risk, that is the optimal scenario.

On a side note… for years trolls have been giving me c*&# about our anti-exploit feature that I created years ago… I am happy that it has now been implemented in another security product and therefore validated as significant and useful ;).

I read on one of the forums that ERP and OSArmor would be an interesting combo… or something to that affect.  Think how magical that would be if the computer automatically locked when it was at risk, and applied different rules based on the toggling ;).

If only a product like that existed ;).


 Thank you Dan for your kind response  :D  ............. In fact, I think that this product exists and its name starts with V  ;)


Mx hello, Some folks say they are great together like peas and carrots


Hi hayc59 Thank you!

Title: Re: VoodooShield v4 Beta Discussion
Post by: Mx on December 27, 2017, 06:06:33 pm
Dan, could you give us the ip ranges for outbound connections of VS?

Thanks.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 07:24:37 pm
@Dan... What happens when we tick the box "Report False Positive"?  ...just curious.
Whenever VS blocks a file, it scans it with the blacklist and VoodooAi, and the results are stored on the VoodooAi server, which allows us to do a few things.  First, the next time a different user blocks the exact same file, the blacklist scan is performed again (because it might have changed since the initial scan), but the VoodooAi scan results will not have changed (until we update the models / algos every 4-6 months), so instead of performing a complete VoodooAi scan again (which can take 2-5 seconds), VS just does a quick lookup in the VoodooAi server and returns the results very quickly.

So anyway, when you check the report false positive box, this info is stored along with the other data in the VoodooAi server, and if a file has enough false positive votes from users, VS will know it is a good file.  I can also manually change files that are reported as false positives... kind of like when you report a false positive to AV vendors.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 07:36:41 pm
I have a VS license that is valid until December 2020. I don't need it any more. No, I don't want a refund. I would like to give it away to someone who may need it (e.g. to some friendly guy who is also a member here). Is this possible?
That's cool with me, just let me know and I will make the change to the account.

On a side note... dude, it takes a lot of patients to be a beta tester for security software, so if you are not willing to put up with a few quirks here and there, in exchange for the opportunity to run the bleeding edge security products, then you might consider not running betas.  I see there are several products that you tried and are not happy with, and if you were a developer, you would understand the hard work and dedication it takes to build cool new stuff.  You would also understand that bugs are simply part of the process, and the more advanced a product is, the more bugs we are going to experience.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 07:44:03 pm
It seems like new users get confused by the red color of the VS shield/icon, it makes them think that protection is disabled.
I suggest that the color should toggle between blue and green, rather than between red and blue. That would give a more accurate visual representation of the protection level.
My apologies in advance if this issue was already discussed to death once upon a time, in some other forum. If so, please just ignore my comment.
Yeah, I certainly see what you mean, and we have discussed it quite a bit, and I am open to any suggestion that makes sense for everyone.  Besides, the color is super easy to change ;).

When I install VS on someone's computer for them, and show them how it works, basically I tell them that the desktop shield gadget is their computer lock.  Then I start a web browser and show them how the lock toggles from OFF to ON... so then they understand immediately that the BLUE / ON and the RED / OFF represent the status of the lock, which is either ON or OFF.  And keep in mind that we also have Training mode, which is red as well ;).

A lot of people have suggested using several different colors for all the different modes, but I think everyone came to the consensus that would be too confusing for everyone.

So if you think of the ON and OFF telling you the status of the lock itself, then I think it makes sense.  It simply tells you whether the computer is actually locked or not.  But as I was saying, I am open to suggestions, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 27, 2017, 07:49:51 pm
On a side note... dude, it takes a lot of patients to be a beta tester for security software, so if you are not willing to put up with a few quirks here and there, in exchange for the opportunity to run the bleeding edge security products, then you might consider not running betas. 
I had the connection issues with ALL versions of VS: 3.59, all B.E.T.A. versions of VS 4 and version 4.15, so it doesn't have anything to do with B.E.T.A. testing. VS just won't connect to the internet here, so I can't use it.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 07:55:14 pm
Hi,

If I have VS I need OSArmor?

Thanks.
That depends… OSArmor is extremely lightweight and NVT are great coders who write amazing software, and it should be completely compatible with VS, so it certainly would not hurt.

When VS toggles to ON, it should easily block everything that is not already whitelisted… the computer is locked down since it is at risk, so very few hardwired “allow” rules are required.  As I always say, “There is never a good reason to let new, non-whitelisted executable code run while a web app is running.”

When VS toggles to OFF (or is on AutoPilot), it is essentially performing either identical or similar functions as OSArmor, or functions that are handled by a different method.

Since when VS is ON the computer is locked down, what we really need to do is compare OSArmor to VS when it is OFF or on AutoPilot.  VS has had its own hardwired rules that I have added and refined for several years now… I always try to explain to people that there is a lot more going on under then hood than they imagine.

Hopefully I did not forget any vital hardwired rules… but this would be a great opportunity for people to see if they can bypass VS, by testing OSArmor’s rules against VS.  Just please keep in mind that usability is the key for deny by default products, so VS applies rules differently, depending on the toggle state.  That is, if VS can auto allow certain items when it is OFF (or on AutoPilot), and automatically lock the computer when it is at risk, that is the optimal scenario.

On a side note… for years trolls have been giving me c*&# about our anti-exploit feature that I created years ago… I am happy that it has now been implemented in another security product and therefore validated as significant and useful ;).

I read on one of the forums that ERP and OSArmor would be an interesting combo… or something to that affect.  Think how magical that would be if the computer automatically locked when it was at risk, and applied different rules based on the toggling ;).

If only a product like that existed ;).


 Thank you Dan for your kind response  :D  ............. In fact, I think that this product exists and its name starts with V  ;)


Mx hello, Some folks say they are great together like peas and carrots


Hi hayc59 Thank you!
Very cool, thank you as well!  I installed OSArmor on my main computer late last night and have been running it all day today along side VS... and yeah, they are a great combo!  A lot of the rules are redundant, but as long as I do not receive too many blocks with OSArmor I will probably leave it installed...  You can never be too careful ;).

I have learned throughout the years how to test VS for false positives, so I ran a few quick FP tests and OSArmor did really well. 

So far, the only FP's I have seen are:

Date/Time: 12/27/2017 1:44:53 PM
Process: [1924]C:\Program Files (x86)\Notepad++\notepad++.exe
Parent: [1772]C:\Windows\explorer.exe
Rule: BlockSuspiciousCmdlines
Rule Name: Block execution of suspicious command-line strings
Command Line: "C:\Program Files (x86)\Notepad++\notepad++.exe"  "C:\Users\UserName\Desktop\New Text Document.bat"
Signer: Notepad++
Parent Signer: Microsoft Windows
 
Date/Time: 12/27/2017 1:44:59 PM
Process: [5696]C:\Windows\System32\notepad.exe
Parent: [1772]C:\Windows\explorer.exe
Rule: BlockSuspiciousCmdlines
Rule Name: Block execution of suspicious command-line strings
Command Line: "C:\Windows\System32\NOTEPAD.EXE" C:\Users\UserName\Desktop\New Text Document.bat
Signer:
Parent Signer: Microsoft Windows

Edit:  BTW, the above FP's were a result of me right clicking on the file and choosing Edit / Edit with Notepad ++
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 07:59:45 pm
Dan, could you give us the ip ranges for outbound connections of VS?

Thanks.
Hmmm, if I had a list of all of them I would certainly post them, but I do not have a list.  Once the database is fixed we will be moving it to our new server and it will be live on voodooshield.com (not .co)... so they are going to change anyway.

There are several tools that you can use that will help determine what IP's are used...

https://techtalk.gfi.com/the-top-20-free-network-monitoring-and-analysis-tools-for-sys-admins/
 
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 08:04:26 pm
On a side note... dude, it takes a lot of patients to be a beta tester for security software, so if you are not willing to put up with a few quirks here and there, in exchange for the opportunity to run the bleeding edge security products, then you might consider not running betas. 
I had the connection issues with ALL versions of VS: 3.59, all B.E.T.A. versions of VS 4 and version 4.15, so it doesn't have anything to do with B.E.T.A. testing. VS just won't connect to the internet here, so I can't use it.
You must be using a VPN or a firewall that is blocking VS's ability to communicate to the internet.  Or you have a bad internet connection, or whatever.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 27, 2017, 08:06:22 pm
It seems like new users get confused by the red color of the VS shield/icon, it makes them think that protection is disabled.
I suggest that the color should toggle between blue and green, rather than between red and blue. That would give a more accurate visual representation of the protection level.
My apologies in advance if this issue was already discussed to death once upon a time, in some other forum. If so, please just ignore my comment.
Yeah, I certainly see what you mean, and we have discussed it quite a bit, and I am open to any suggestion that makes sense for everyone.  Besides, the color is super easy to change ;).

When I install VS on someone's computer for them, and show them how it works, basically I tell them that the desktop shield gadget is their computer lock.  Then I start a web browser and show them how the lock toggles from OFF to ON... so then they understand immediately that the BLUE / ON and the RED / OFF represent the status of the lock, which is either ON or OFF.  And keep in mind that we also have Training mode, which is red as well ;).

A lot of people have suggested using several different colors for all the different modes, but I think everyone came to the consensus that would be too confusing for everyone.

So if you think of the ON and OFF telling you the status of the lock itself, then I think it makes sense.  It simply tells you whether the computer is actually locked or not.  But as I was saying, I am open to suggestions, thank you!
The problem is that people believe what they see, and they see red, which tells them, "danger ahead!"
As you said, and rightly so, the current color scheme makes perfect sense to everyone -- but only after you explain it to them. And experience shows that most folks don't read instructions, no matter how clear and concise they are. They are too eager to see how this cool new thing works!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 27, 2017, 08:34:17 pm
It seems like new users get confused by the red color of the VS shield/icon, it makes them think that protection is disabled.
I suggest that the color should toggle between blue and green, rather than between red and blue. That would give a more accurate visual representation of the protection level.
My apologies in advance if this issue was already discussed to death once upon a time, in some other forum. If so, please just ignore my comment.
Yeah, I certainly see what you mean, and we have discussed it quite a bit, and I am open to any suggestion that makes sense for everyone.  Besides, the color is super easy to change ;).

When I install VS on someone's computer for them, and show them how it works, basically I tell them that the desktop shield gadget is their computer lock.  Then I start a web browser and show them how the lock toggles from OFF to ON... so then they understand immediately that the BLUE / ON and the RED / OFF represent the status of the lock, which is either ON or OFF.  And keep in mind that we also have Training mode, which is red as well ;).

A lot of people have suggested using several different colors for all the different modes, but I think everyone came to the consensus that would be too confusing for everyone.

So if you think of the ON and OFF telling you the status of the lock itself, then I think it makes sense.  It simply tells you whether the computer is actually locked or not.  But as I was saying, I am open to suggestions, thank you!
The problem is that people believe what they see, and they see red, which tells them, "danger ahead!"
As you said, and rightly so, the current color scheme makes perfect sense to everyone -- but only after you explain it to them. And experience shows that most folks don't read instructions, no matter how clear and concise they are. They are too eager to see how this cool new thing works!
I see what you are saying and it makes perfect sense, but we also need to keep in mind that we need to maintain a clear distinction between locked and unlocked, by using blue and red.

Think of it this way... when VS was first released 6 or so years ago, there were zero protections when VS toggled to OFF... so it was basically toggling between ON and Training Mode.  In that case, blue and red make perfect sense.  Then we started adding protections to the unlocked mode, and at some point, the blue and red no longer made sense, unless the user understands that the the ON / Blue and OFF / Red is a description of the lock's state.

Either way, this is very interesting to me, and maybe someone will think of something that makes even more sense with the colors, and if so we will change it ;).  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 27, 2017, 08:55:29 pm
You must be using a VPN or a firewall that is blocking VS's ability to communicate to the internet.  Or you have a bad internet connection, or whatever.
No VPN here, and my firewall is not blocking VS. And no, my internet connection isn't bad at all, no problems here - with the exception of VS.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 27, 2017, 09:52:12 pm
That's cool with me, just let me know and I will make the change to the account.
PM sent.
Title: Re: VoodooShield v4 Beta Discussion
Post by: simmerskool on December 27, 2017, 11:17:28 pm
You must be using a VPN or a firewall that is blocking VS's ability to communicate to the internet.  Or you have a bad internet connection, or whatever.
No VPN here, and my firewall is not blocking VS. And no, my internet connection isn't bad at all, no problems here - with the exception of VS.

I have the same problem with VS connecting to internet from my office, but that is because the head IT there instructed the office firewall to block it.  VS connects aok from from home and so I wonder if your network got a bad or incorrect instruction somehow??
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 28, 2017, 12:20:51 am
I wonder if your network got a bad or incorrect instruction somehow??
I really don't know. VS is the only application that's unable to connect to the internet. Anyway, I removed all VS traces from my computer and I'm currently in the process of giving away my license, which I don't need any more. Still waiting for feedback from the VS developer. 8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 28, 2017, 12:37:13 am
Hello Buddel, have you tried connecting in safe mode with networking enabled?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on December 28, 2017, 12:56:10 am
Hello Buddel, have you tried connecting in safe mode with networking enabled?
Excellent suggestion. Thank you. Maybe I should have tried it, but it's too late now, anyway. I'm not willing to install VS again (well, maybe in four or five years, who knows). I really don't want to invest more time on VS, it would be like flogging a dead horse for me. What's more, I have found an alternative to VS that works very well for me, so my "VS era" is definitely over. 8) Just for the record: I did not say that VS doesn't work. What I said is that VS didn't work for me.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mx on December 28, 2017, 01:34:18 am
Dan, have you seen this?

https://www.youtube.com/watch?v=rGYdlmgMOwk
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 02:17:46 am
No, I had not seen that actually, thank you!

It’s quite funny… I think we need more Metasploit based test videos, that way people who are unable to test for themselves will understand that a command line is usually required in the attack chain, which VS will block, and successfully stop the attack.

BTW, I am aware of the specific script that kills VS 4.0, and now that VS is stable and we have pretty much all of the bugs worked out, we can add self-protection soon, which will fix the script issue.
Title: Re: VoodooShield v4 Beta Discussion
Post by: djg05 on December 28, 2017, 11:28:38 am
It seems like new users get confused by the red color of the VS shield/icon, it makes them think that protection is disabled.
I suggest that the color should toggle between blue and green, rather than between red and blue. That would give a more accurate visual representation of the protection level.
My apologies in advance if this issue was already discussed to death once upon a time, in some other forum. If so, please just ignore my comment.
Yeah, I certainly see what you mean, and we have discussed it quite a bit, and I am open to any suggestion that makes sense for everyone.  Besides, the color is super easy to change ;).

When I install VS on someone's computer for them, and show them how it works, basically I tell them that the desktop shield gadget is their computer lock.  Then I start a web browser and show them how the lock toggles from OFF to ON... so then they understand immediately that the BLUE / ON and the RED / OFF represent the status of the lock, which is either ON or OFF.  And keep in mind that we also have Training mode, which is red as well ;).

A lot of people have suggested using several different colors for all the different modes, but I think everyone came to the consensus that would be too confusing for everyone.

So if you think of the ON and OFF telling you the status of the lock itself, then I think it makes sense.  It simply tells you whether the computer is actually locked or not.  But as I was saying, I am open to suggestions, thank you!
The problem is that people believe what they see, and they see red, which tells them, "danger ahead!"
As you said, and rightly so, the current color scheme makes perfect sense to everyone -- but only after you explain it to them. And experience shows that most folks don't read instructions, no matter how clear and concise they are. They are too eager to see how this cool new thing works!
I see what you are saying and it makes perfect sense, but we also need to keep in mind that we need to maintain a clear distinction between locked and unlocked, by using blue and red.

Think of it this way... when VS was first released 6 or so years ago, there were zero protections when VS toggled to OFF... so it was basically toggling between ON and Training Mode.  In that case, blue and red make perfect sense.  Then we started adding protections to the unlocked mode, and at some point, the blue and red no longer made sense, unless the user understands that the the ON / Blue and OFF / Red is a description of the lock's state.

Either way, this is very interesting to me, and maybe someone will think of something that makes even more sense with the colors, and if so we will change it ;).  Thank you!

We have had this discussion before Dan and the logic seems wrong to me. The natural understanding from me it that when you turn a switch on it goes to RED, however I realise that the argument can go both ways and you are probably too far down the line now to reverse it. Maybe you could think in terms of traffic lights where green would mean (VS on) safe to go, and amber (VS off) proceed with caution.

Regards

David
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 28, 2017, 01:38:49 pm
I think that average users who is not familiar with how Voodoo inform users through the desktop shield gadget is confuzed a bit except someone explain them with little bit of effort!

It is little confuzing to them when they see a red gadget with big OFF, it is no wonder that they think that protection is OFF!

Experienced users knows that they are protected and how are protected so for them that gadget is not that important but novice users will need that gadget much more and for them it should be more clearer what's going on.

So I suggest a little change in gadget notifications with only a three state, maybe something like this...
1. Green ON ( protection is on )
2. Red OFF ( protection is off )
3. Blue LOCK ( highest protection and computer is in LOCK state )
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 28, 2017, 01:48:55 pm
I think that average users who is not familiar with how Voodoo inform users through the desktop shield gadget is confuzed a bit except someone explain them with little bit of effort!

It is little confuzing to them when they see a red gadget with big OFF, it is no wonder that they think that protection is OFF!

Experienced users knows that they are protected and how are protected so for them that gadget is not that important but novice users will need that gadget much more and for them it should be more clearer what's going on.

So I suggest a little change in gadget notifications with only a three state, maybe something like this...
1. Green ON ( protection is on )
2. Red OFF ( protection is off )
3. Blue LOCK ( highest protection and computer is in LOCK state )
Good explanation and good suggestion. The "unlocked" state as displayed on the shield is definitely overstated and misleading to the untrained eye. It's sort of a relic from the early stages of VS.

Another possibility would be to put the image of a lock on the shield. When it is locked, of course.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Telos on December 28, 2017, 02:42:01 pm
I doubt there will be consensus on a shield color scheme. I'm content with how things are now (although I'd like to see the "install mode' colored a throbbing yellow} 8)  :P
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 28, 2017, 03:10:42 pm
Well...I have no problem with that too but I have novice users on my mind!

To us, that shield gadget is not even needed and most of his purpose (I think) is mostly for novice users and if we have that on mind, that gadget should be easy to understand.

This is just my opinion  ::)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 28, 2017, 04:36:20 pm
I doubt there will be consensus on a shield color scheme. I'm content with how things are now (although I'd like to see the "install mode' colored a throbbing yellow} 8)  :P

I know this has been talked about in the [original] VS Wilders' topic/thread, before. Then, I pointed out that I was color blind, i.e red/green.  So, I am happy to go a little "mellow yellow". ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 28, 2017, 04:44:49 pm
Personally, I think @Andi is hitting the nail on the head.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 28, 2017, 05:08:56 pm
If we are talking about experience...I guess I prefer to be a novice, and not a novitiate. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 05:18:40 pm

We have had this discussion before Dan and the logic seems wrong to me. The natural understanding from me it that when you turn a switch on it goes to RED, however I realise that the argument can go both ways and you are probably too far down the line now to reverse it. Maybe you could think in terms of traffic lights where green would mean (VS on) safe to go, and amber (VS off) proceed with caution.

Regards

David
Hey David, how are you?  Great to see you here!  I totally agree, the argument can go both ways.

What if we did something like this... instead of having the shield display "ON" or "OFF" in big letters, it would look something like this, in smaller letters... (we have to pretend there is a shield around these).


Lock
 ON


Lock
 OFF


Or, as someone suggested in the past, have a padlock, either locked or not.

These are just some ideas... I would love to hear other people's ideas as well.

Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 05:20:16 pm
I think that average users who is not familiar with how Voodoo inform users through the desktop shield gadget is confuzed a bit except someone explain them with little bit of effort!

It is little confuzing to them when they see a red gadget with big OFF, it is no wonder that they think that protection is OFF!

Experienced users knows that they are protected and how are protected so for them that gadget is not that important but novice users will need that gadget much more and for them it should be more clearer what's going on.

So I suggest a little change in gadget notifications with only a three state, maybe something like this...
1. Green ON ( protection is on )
2. Red OFF ( protection is off )
3. Blue LOCK ( highest protection and computer is in LOCK state )
Thank you Andi!  Yeah, maybe something like Andi did... what do other people think?
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 28, 2017, 05:21:00 pm
VoodooShield said>

Quote:  ["Very cool, thank you as well!  I installed OSArmor on my main computer late last night and have been running it all day today along side VS... and yeah, they are a great combo!  A lot of the rules are redundant, but as long as I do not receive too many blocks with OSArmor I will probably leave it installed...  You can never be too careful".]

Interestingly, I have been running OSArmor for a few weeks and have found it quite quiet so far along side of VS.
Absolutely, you can never be to careful!
Which is why imho "specialized software" that use very little resources like VS and OSArmor along with some other choice proggies is the  basis for an effective "layered security profile"
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 05:22:38 pm
I think that average users who is not familiar with how Voodoo inform users through the desktop shield gadget is confuzed a bit except someone explain them with little bit of effort!

It is little confuzing to them when they see a red gadget with big OFF, it is no wonder that they think that protection is OFF!

Experienced users knows that they are protected and how are protected so for them that gadget is not that important but novice users will need that gadget much more and for them it should be more clearer what's going on.

So I suggest a little change in gadget notifications with only a three state, maybe something like this...
1. Green ON ( protection is on )
2. Red OFF ( protection is off )
3. Blue LOCK ( highest protection and computer is in LOCK state )
Good explanation and good suggestion. The "unlocked" state as displayed on the shield is definitely overstated and misleading to the untrained eye. It's sort of a relic from the early stages of VS.

Another possibility would be to put the image of a lock on the shield. When it is locked, of course.
Yeah, it must have been you who mentioned the lock image before... I am not sure, it has been so long.

But yeah, I think if we brainstorm we will figure out the best answer.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 05:36:12 pm
VoodooShield said>

Quote:  ["Very cool, thank you as well!  I installed OSArmor on my main computer late last night and have been running it all day today along side VS... and yeah, they are a great combo!  A lot of the rules are redundant, but as long as I do not receive too many blocks with OSArmor I will probably leave it installed...  You can never be too careful".]

Interestingly, I have been running OSArmor for a few weeks and have found it quite quiet so far along side of VS.
Absolutely, you can never be to careful!
Which is why imho "specialized software" that use very little resources like VS and OSArmor along with some other choice proggies is the  basis for an effective "layered security profile"
Yeah, if you ask me, it is an amazing combo... in my opinion, OSArmor is a much better combo with VS than any other deny-by-default / AE / SRP product, simply because the other products will be blocking everything full time, so OSArmor will probably never get a chance to block or do anything ;).

Whereas when OSArmor is paired with VS, it essentially fortifies VS's OFF and AutoPilot Mode rules / policies, while VS locks the computer when it is at risk... it is a win-win.

It would be quite similar to a scenario where OSArmor would be able automatically lock the computer down when it was at risk, and run its current rules / policies when the computer is not at risk.  Well, there are some that would run when the computer is at risk, but you get my point ;).

BTW, I only found the FP's because I was testing for them... I am familiar with the various actions that can trigger FP's (since I test VS all of the time), and that is all I have found so far.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 05:48:04 pm
BTW, I do not want to give anyone the impression that VS is insufficient in anyway in OFF or AutoPilot Mode...  these modes have stood the test of time and from my testing, have truly unmatched blocking efficiencies for a allow-by-default mode, so if you only want to run VS, you should be more than protected.

I just like to run the two together because it is interesting for me to test and compare the differences in the rules / policies, and it is interesting for me to see how they handle different things in different ways.

Having said that, I encourage everyone to give OSArmor a try, I think you will like it.
 
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 28, 2017, 08:09:50 pm
Ok Dan, will try it...

Hmmm...I've got some error in installation process but installation still ends successfully.

I disable Voodoo before installation ofcourse.

Any idea what would be the problem and should I be concerned about it?


Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 28, 2017, 08:25:16 pm
Ok Dan, will try it...

Hmmm...I've got some error in installation process but installation still ends successfully.

I disable Voodoo before installation ofcourse.

Any idea what would be the problem and should I be concerned about it?
It might mean there is a file still in use at that memory area, and you are not allowed to overwrite it.
Maybe you tried twice to install, and you didn't reboot in between? Just guessing.

The other possibility is that you simply don't have sufficient rights for that action. If you are installing in a standard (limited) user account, try installing from the admin account.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 28, 2017, 08:40:13 pm
Ok Dan, will try it...

Hmmm...I've got some error in installation process but installation still ends successfully.

I disable Voodoo before installation ofcourse.

Any idea what would be the problem and should I be concerned about it?
It might mean there is a file still in use at that memory area, and you are not allowed to overwrite it.
Maybe you tried twice to install, and you didn't reboot in between? Just guessing.

The other possibility is that you simply don't have sufficient rights for that action. If you are installing in a standard (limited) user account, try installing from the admin account.
This error could also be caused by Windows Defender Controlled folder access
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 28, 2017, 08:41:53 pm
It quickly come in my mind what was the problem...
I'm on Admin acc. but installer was unable to write needed ink file because I have "turned on" in Windows Defender "Controlled Folder Access", first I was try to "exclude" OSA installation pakage but it not worked and again I have got that error.

As soon as I turned it off, installation was successful without errors  :)

Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 28, 2017, 08:45:07 pm
Hahaha Shmu26 we think alike  :D
You beat me for a few seconds... ;)

btw: @Dan 
Do I leave OSA on default settings or you have some additional advice with those unchecked checkmarks...
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 09:45:48 pm
Hahaha Shmu26 we think alike  :D
You beat me for a few seconds... ;)

btw: @Dan 
Do I leave OSA on default settings or you have some additional advice with those unchecked checkmarks...
I am just running with all defaults... it is probably the best config.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 28, 2017, 09:49:53 pm
Ok, I think the database and web server is completely squared away.

You might have to click the Confirm Registration button or exit out of VS for it to act normal.  After you click the button and restart VS, please check to make sure your expiration date and endpoint quantity is correct.  Anyone with a license from any of the security forums should have an endpoint quantity of 10... but if something is not correct, just email me at support @ voodooshield.com and I will fix it asap.

I deleted all of the endpoints and whitelists from the database for a couple of different reasons, so basically we are starting with a clean slate.  Thank you guys!
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 29, 2017, 12:42:13 am
4.15 is running very well for me, only 1 thing to mention. Occasionally VS remains locked when I close the browser. I noticed this in other 4. betas but it would correct itself when I opened and closed a browser, now it takes a restart. Doesn't matter if I use Chrome or IE.

Win7 64
Crystal security
System default security
Nothing else

Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on December 29, 2017, 12:48:51 am
Ok, I think the database and web server is completely squared away.

You might have to click the Confirm Registration button or exit out of VS for it to act normal.  After you click the button and restart VS, please check to make sure your expiration date and endpoint quantity is correct.  Anyone with a license from any of the security forums should have an endpoint quantity of 10... but if something is not correct, just email me at support @ voodooshield.com and I will fix it asap.

I deleted all of the endpoints and whitelists from the database for a couple of different reasons, so basically we are starting with a clean slate.  Thank you guys!

Like this? ...Hey presto!   Dan, thanks for the extension of licence. :)


Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 29, 2017, 01:02:53 am
Hi Dan,

Clean install v4.15 and reset registration and now I have problem...
 It says "Maximum number of SEATS reached" What is this? I have Voodoo on just one PC.
Can you help?



Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 29, 2017, 01:36:45 am
4.15 is running very well for me, only 1 thing to mention. Occasionally VS remains locked when I close the browser. I noticed this in other 4. betas but it would correct itself when I opened and closed a browser, now it takes a restart. Doesn't matter if I use Chrome or IE.

Win7 64
Crystal security
System default security
Nothing else
That's funny that you mentioned this... I am actually working on this issue as we speak with Krusty from Wilders ;).  We should have a fix for this soon, thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 29, 2017, 01:38:24 am
Ok, I think the database and web server is completely squared away.

You might have to click the Confirm Registration button or exit out of VS for it to act normal.  After you click the button and restart VS, please check to make sure your expiration date and endpoint quantity is correct.  Anyone with a license from any of the security forums should have an endpoint quantity of 10... but if something is not correct, just email me at support @ voodooshield.com and I will fix it asap.

I deleted all of the endpoints and whitelists from the database for a couple of different reasons, so basically we are starting with a clean slate.  Thank you guys!
Sure, thank you!  If you or any of the other "old guys" or "new guys" need a license or extension, just email me as support at voodooshield.com.
Like this? ...Hey presto!   Dan, thanks for the extension of licence. :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 29, 2017, 01:40:12 am
Hi Dan,

Clean install v4.15 and reset registration and now I have problem...
 It says "Maximum number of SEATS reached" What is this? I have Voodoo on just one PC.
Can you help?
Sorry about that, I will fix it tonight after dinner.  Can you please email me the email address that you use for your account, and I will add some seats.  Thank you!

BTW... this is the kind of stuff that I was talking about that might happen.  If this happens to anyone else, just email me and I will fix it.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Alexhousek on December 29, 2017, 05:00:08 am
Just converted from 3.59 to 4.15.  Uninstalled 3.59, reboooted laptop and then installed 4.15.  I entered in my registration information and BINGO, all was well!  (Windows 10 Home)

Great, great piece of software Dan!!!
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on December 29, 2017, 05:30:41 am
Management Console and GUI information match up now. Thanks Dan.  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: ColonelMal on December 29, 2017, 06:36:20 am
Apologies for some redundancy here, but after a clean install of v4.15 and reset registration now I have a message that says "Maximum number of SEATS reached" What is this? I have Voodoo on just one PC.
[the redundancy part follows :) ]
Dan, I sent you an email about it.
Title: Re: VoodooShield v4 Beta Discussion
Post by: djg05 on December 29, 2017, 11:45:34 am

We have had this discussion before Dan and the logic seems wrong to me. The natural understanding from me it that when you turn a switch on it goes to RED, however I realise that the argument can go both ways and you are probably too far down the line now to reverse it. Maybe you could think in terms of traffic lights where green would mean (VS on) safe to go, and amber (VS off) proceed with caution.

Regards

David
Hey David, how are you?  Great to see you here!  I totally agree, the argument can go both ways.

What if we did something like this... instead of having the shield display "ON" or "OFF" in big letters, it would look something like this, in smaller letters... (we have to pretend there is a shield around these).


Lock
 ON


Lock
 OFF


Or, as someone suggested in the past, have a padlock, either locked or not.

These are just some ideas... I would love to hear other people's ideas as well.

Hi Dan, thanks -just getting crumblier.

I think that whatever you do you must ditch the current colours to avoid confusion. I like the padlock idea. It ties in with the https secure padlock. I don't think you need any script on the icon to avoid language problems. So suggest the following

Green with closed padlock

Amber with open padlock

Any more options will tend to confuse. The padlock should cope with those who are colour blind

I would also suggest that for those that rely on the task bar icon that when you hover over it, it confirms the current mode it is in.

Hope this helps

Regards

David
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 29, 2017, 12:45:23 pm

Hi Dan, thanks -just getting crumblier.

I think that whatever you do you must ditch the current colours to avoid confusion. I like the padlock idea. It ties in with the https secure padlock. I don't think you need any script on the icon to avoid language problems. So suggest the following

Green with closed padlock

Amber with open padlock

Any more options will tend to confuse. The padlock should cope with those who are colour blind

I would also suggest that for those that rely on the task bar icon that when you hover over it, it confirms the current mode it is in.

Hope this helps

Regards

David
Sounds good!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 29, 2017, 01:22:49 pm
Ditto!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 29, 2017, 02:40:17 pm
I found couple nice samples...  :D




Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 29, 2017, 02:49:27 pm
Thank you guys for the suggestions... I will look at them closer today and we can figure out what to do.

I wanted to mention that we are still having issues with the web server / database, but Alex is working on it as we speak.  Thank you!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 29, 2017, 03:29:05 pm
Whatever model you pick ( or not ), in my opinion it will be best that you have only two colors ( green and red )
1.GREEN with two states ( on and lock ), green shield with letter ON and green shield with padlock for LOCK so that users known that they are protected.
2.RED with letter OFF ( for Voodoo is disabled/install state )

RED icon never should be for anything than disabled/unprotected state!

That is my opinion  ;)

Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 29, 2017, 10:16:07 pm

Hi Dan, thanks -just getting crumblier.

I think that whatever you do you must ditch the current colours to avoid confusion. I like the padlock idea. It ties in with the https secure padlock. I don't think you need any script on the icon to avoid language problems. So suggest the following

Green with closed padlock

Amber with open padlock

Any more options will tend to confuse. The padlock should cope with those who are colour blind

I would also suggest that for those that rely on the task bar icon that when you hover over it, it confirms the current mode it is in.

Hope this helps

Regards

David
Sounds good!

Ditto here too and I like Andi's second icon.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Unauthorized on December 30, 2017, 02:54:04 am
BTW, I do not want to give anyone the impression that VS is insufficient in anyway in OFF or AutoPilot Mode...  these modes have stood the test of time and from my testing, have truly unmatched blocking efficiencies for a allow-by-default mode, so if you only want to run VS, you should be more than protected.

I just like to run the two together because it is interesting for me to test and compare the differences in the rules / policies, and it is interesting for me to see how they handle different things in different ways.

Having said that, I encourage everyone to give OSArmor a try, I think you will like it.

I would like the try OSArmor and Voodooshield together but will OSArmor be compatible with malware bytes pro and i have kaspersky Internet Security 2018. I don't want to create problems because of software conflicts
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 30, 2017, 09:20:50 am
BTW, I do not want to give anyone the impression that VS is insufficient in anyway in OFF or AutoPilot Mode...  these modes have stood the test of time and from my testing, have truly unmatched blocking efficiencies for a allow-by-default mode, so if you only want to run VS, you should be more than protected.

I just like to run the two together because it is interesting for me to test and compare the differences in the rules / policies, and it is interesting for me to see how they handle different things in different ways.

Having said that, I encourage everyone to give OSArmor a try, I think you will like it.

I would like the try OSArmor and Voodooshield together but will OSArmor be compatible with malware bytes pro and i have kaspersky Internet Security 2018. I don't want to create problems because of software conflicts

Wait...you want to say that you have on you sistem KIS,MBAM Premium, Voodoo and you wish to add OSA too???
This is overkill to the sistem!!!

I suggest that you at least remove MBAM from the equation!
Title: Re: VoodooShield v4 Beta Discussion
Post by: djg05 on December 30, 2017, 11:18:40 am
Whatever model you pick ( or not ), in my opinion it will be best that you have only two colors ( green and red )
1.GREEN with two states ( on and lock ), green shield with letter ON and green shield with padlock for LOCK so that users known that they are protected.
2.RED with letter OFF ( for Voodoo is disabled/install state )

RED icon never should be for anything than disabled/unprotected state!

That is my opinion  ;)

Don't think you can use red since it will confuse with the current system.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 30, 2017, 12:17:43 pm
Whatever model you pick ( or not ), in my opinion it will be best that you have only two colors ( green and red )
1.GREEN with two states ( on and lock ), green shield with letter ON and green shield with padlock for LOCK so that users known that they are protected.
2.RED with letter OFF ( for Voodoo is disabled/install state )

RED icon never should be for anything than disabled/unprotected state!

That is my opinion  ;)

Don't think you can use red since it will confuse with the current system.

Well...we will have to adapt to new (logical, less confusing) color notification sistem, if Dan decide to change that at all  :D
Title: Re: VoodooShield v4 Beta Discussion
Post by: pavo on December 30, 2017, 02:02:58 pm
I don't understand the whole changing colors hype as the current scheme is logical - when there is no web app running VS icon is red - VS is not locking your system and when web app has been started VS icon is going blue and the system is locked. There is nothing confusing for me.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Antarctica on December 30, 2017, 02:14:25 pm
I tend to agree with you. Four five years ago when I first install VS, I was also a little bit confused but now I am use to it, but Dan will make the final decision and if he decide to change, we will all getting use to it again. ;) beta
Title: Re: VoodooShield v4 Beta Discussion
Post by: pavo on December 30, 2017, 03:28:39 pm
I tend to agree with you. Four five years ago when I first install VS, I was also a little bit confused but now I am use to it, but Dan will make the final decision and if he decide to change, we will all getting use to it again. ;) beta
Amen to that!  ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 30, 2017, 04:08:10 pm
BTW, I do not want to give anyone the impression that VS is insufficient in anyway in OFF or AutoPilot Mode...  these modes have stood the test of time and from my testing, have truly unmatched blocking efficiencies for a allow-by-default mode, so if you only want to run VS, you should be more than protected.

I just like to run the two together because it is interesting for me to test and compare the differences in the rules / policies, and it is interesting for me to see how they handle different things in different ways.

Having said that, I encourage everyone to give OSArmor a try, I think you will like it.

I would like the try OSArmor and Voodooshield together but will OSArmor be compatible with malware bytes pro and i have kaspersky Internet Security 2018. I don't want to create problems because of software conflicts

Wait...you want to say that you have on you sistem KIS,MBAM Premium, Voodoo and you wish to add OSA too???
This is overkill to the sistem!!!

I suggest that you at least remove MBAM from the equation!

Interesting, I run MBam with AIS and OSArmor and VS with absolutely no conflict at all. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Unauthorized on December 30, 2017, 04:35:44 pm
BTW, I do not want to give anyone the impression that VS is insufficient in anyway in OFF or AutoPilot Mode...  these modes have stood the test of time and from my testing, have truly unmatched blocking efficiencies for a allow-by-default mode, so if you only want to run VS, you should be more than protected.

I just like to run the two together because it is interesting for me to test and compare the differences in the rules / policies, and it is interesting for me to see how they handle different things in different ways.

Having said that, I encourage everyone to give OSArmor a try, I think you will like it.

I would like the try OSArmor and Voodooshield together but will OSArmor be compatible with malware bytes pro and i have kaspersky Internet Security 2018. I don't want to create problems because of software conflicts

Wait...you want to say that you have on you sistem KIS,MBAM Premium, Voodoo and you wish to add OSA too???
This is overkill to the sistem!!!

I suggest that you at least remove MBAM from the equation!

So why do you think it's overkill for my system?
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 30, 2017, 04:45:18 pm
Both OSA and VS uses very limited resources and in this day and age with 4-8 GB on RAM minimum, there is no drop in resources so 'over kill' is not a term I'd use in this situation.
A solid "layered security profile" is never overkill..... imho :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 30, 2017, 05:20:01 pm
In my opinion this is too many security product and there is a great risk that sooner or later some problems will occur!
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 30, 2017, 05:42:48 pm
In my opinion this is too many security aplications and there is a great risk that sooner or later some problems will occur!

Fair enough, however I've run the same strategy for over 15 years, no incidents, no conflict.
We only have our experience to support our beliefs. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on December 30, 2017, 06:27:24 pm
Ok, I'm glad you did not have a problems, obviously you chose wisely what to install  ;)

My thinking is...

Would the soldier be effective with a double helmet or with double boots or to carry two machine guns or two or three panties...hey,better double everything you say...I think not!

You don't need two or tree protection modules with the same purpose, that is not "layered protection"!
Only thing you can get with that is problems with pc,conflicts with security applications and slowdowns of pc or internet if you don't think wisely  ;)

If I have KIS ( with a bunch of protection modules ), I do not need much more, maybe just Voodoo or OSA and good ad-block extension in browser, that's it!

If I remove KIS, then I have "room" for several security application which I could installed to fulfill security gaps.

That's my opinion ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Shmu26 on December 30, 2017, 08:17:56 pm
When you combine a lot of overlapping security softs, there can be conflicts that are not immediately apparent to the eye. Everything looks fine. But when malware actually strikes, and two or three behavior-blocking or anti-exploit systems are trying to stop it, they might just conflict with each other, and the malware will not be stopped. It's hard to test these things, and the results can change if you repeat the test.
Title: Re: VoodooShield v4 Beta Discussion
Post by: dotnetnightmare on December 30, 2017, 10:06:39 pm
 I see so many users buy a fast cpu and ssd drive, then throttle it with many security programs. Every file read/write  is scanned.  VoodooShield, AppGuard, OSarmor, all offer solid protection that surpass all current active scanners, in resource use, file access, and have the lowest failure rate. Mbam is a resource hog and has been known to conflict with itself, let alone other security solutions. This is my opinion, and a quick google/bing search of "mbam resource hog" will give you a good amount of users that agree.
Title: Re: VoodooShield v4 Beta Discussion
Post by: BryanB on December 31, 2017, 02:42:33 am
Well said dotnetnightmare, your input is appreciated here. Look forword to your further insight.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Rainwalker on December 31, 2017, 03:01:17 pm
Yesterday I went back to 3.59b as the latest beta became too much. When I first installed it all was well for about an hour, after which the problems began. I could not get it to work in another account unless I opened it as administrator. Next it would occasionally close and there was one instance wherein it suddenly went to DISABLED for about10 or 15 seconds. I went back to 3.59b. When I turned on the computer this morning there was a notice informing me that good ol' 3.59 was no longer supported and VS would not work unless I upgraded. I clicked the option to upgrade and it seemed to upgrade. Then I received the same need to upgrade message. OK, I did and then received it two more times after the upgrade so came over here. What is going on? 3.59 is all that works for me.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Silver0066 on December 31, 2017, 05:29:50 pm
Yesterday I went back to 3.59b as the latest beta became too much. When I first installed it all was well for about an hour, after which the problems began. I could not get it to work in another account unless I opened it as administrator. Next it would occasionally close and there was one instance wherein it suddenly went to DISABLED for about10 or 15 seconds. I went back to 3.59b. When I turned on the computer this morning there was a notice informing me that good ol' 3.59 was no longer supported and VS would not work unless I upgraded. I clicked the option to upgrade and it seemed to upgrade. Then I received the same need to upgrade message. OK, I did and then received it two more times after the upgrade so came over here. What is going on? 3.59 is all that works for me.
The same thing happened to me this morning.  I did a Restore with Macrium Reflect and Voodoo 3.59 popped up stating that it needed an update.  I updated and it keeps happening.  I can't get 3.59 to start.  I did install 4.15b and it seems to be working OK.  Any suggestions on how to get 3.59 working?
Title: Re: VoodooShield v4 Beta Discussion
Post by: giladfrid009 on December 31, 2017, 05:30:39 pm
"VS insisted I do the upgrade, so after upgrading I keep getting the VS needs updating screen.... I'm just round and around in circles! should I delete VS and download 3.59 from the site and re install? What gives?"

same with me (quote from wilders)
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on December 31, 2017, 05:57:21 pm
I knew I had a VM with 3.59 installed so I cranked that up and sure enough got the update screen. AS mentioned it get's stuck in an upgrade loop.
Will try removing VS and manually install the 4.15 later.
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on December 31, 2017, 05:58:23 pm
Sorry for the inconvenience… I did not realize that it was already New Years in certain time zones ;).

The automatic update should work fine now, but if it does not, you can download VoodooShield 4.15 below.

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

There were a lot of changes in VoodooShield and the database in version 4.0, so please check your account to make sure everything is accurate, and if it is not, please let me know.

If there is anything odd with your account, you might try to exit out of VoodooShield, then delete the following file, then start VoodooShield again.

C:\ProgramData\VoodooShield\voodooshield-token.json


Happy New Years!



Thank you,

Dan
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on December 31, 2017, 06:06:49 pm
Sorry for the inconvenience… I did not realize that it was already New Years in certain time zones ;).

The automatic update should work fine now, but if it does not, you can download VoodooShield 4.15 below.

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

There were a lot of changes in VoodooShield and the database in version 4.0, so please check your account to make sure everything is accurate, and if it is not, please let me know.

If there is anything odd with your account, you might try to exit out of VoodooShield, then delete the following file, then start VoodooShield again.

C:\ProgramData\VoodooShield\voodooshield-token.json


Happy New Years!



Thank you,

Dan

Dan is VS v3.59 still supported?
Title: Re: VoodooShield v4 Beta Discussion
Post by: schmidthouse on December 31, 2017, 06:20:14 pm
@ Dan

I followed the direction and deleted:     C:\ProgramData\VoodooShield\voodooshield-token.json

Voila, all is just as it should be now with account and Console running v.4.15

Please disregard my email, except for the Happy New Year part. ;)

Thanks
Title: Re: VoodooShield v4 Beta Discussion
Post by: ssherjj on December 31, 2017, 06:45:31 pm
Sorry for the inconvenience… I did not realize that it was already New Years in certain time zones ;).

The automatic update should work fine now, but if it does not, you can download VoodooShield 4.15 below.

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

There were a lot of changes in VoodooShield and the database in version 4.0, so please check your account to make sure everything is accurate, and if it is not, please let me know.

If there is anything odd with your account, you might try to exit out of VoodooShield, then delete the following file, then start VoodooShield again.

C:\ProgramData\VoodooShield\voodooshield-token.json


Happy New Years!



Thank you,

Dan

Thank you Dan for all you have done to make VS a great product. I noticed my registration was up-dated..all is good to go now!

Happy New Years!
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on January 01, 2018, 01:07:03 am
Sorry for the inconvenience… I did not realize that it was already New Years in certain time zones ;).

Happy New Years!

Errr...  London should be an hour into 2018 as I write, we've had it for 8 hours and 57 minutes  ;D

I've attached the relevant images.  It seems I have nearly a year left on my registration  :D but I'll put 4.15 in and see what happens.  The trouble with New Year is all the lines in the world are congested: I could only get 120KBps on that download  >:(

Anyway, a Merry New Year to all, and remember we have at least 5 more New Years this year  8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: jerzy6012.50 on January 01, 2018, 09:46:37 am
just today it is 1.01 2018 I received a notification of upgrade to version 4.15, and I had versions 3.59.
I've updated and it's all good with rejstracy too.
so far everything works well and hopes everything will be ok I have set for a car.
Anyway, from the beginning I was set for a car.
thanks to Dan and all the best this new year.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on January 01, 2018, 04:10:44 pm
I have a VS license that is valid until December 2020. I don't need it any more. No, I don't want a refund. I would like to give it away to someone who may need it (e.g. to some friendly guy who is also a member here). Is this possible?

Update: I'm still trying to transfer my three-year license to a CoU member. Unfortunately, I don't know whether or not this license transfer has meanwhile been successful because the developer does not send me any replies to my personal messages. Maybe he hasn't even read them, I really don't know. :(

If my license transfer has been successful, fine; if not, well, I don't care any more and I will just let my license run out. I'm just not willing to wait for replies any more that will probably never arrive here. Great support. :(
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on January 01, 2018, 10:32:13 pm
I have a VS license that is valid until December 2020. I don't need it any more. No, I don't want a refund. I would like to give it away to someone who may need it (e.g. to some friendly guy who is also a member here). Is this possible?

Update: I'm still trying to transfer my three-year license to a CoU member. Unfortunately, I don't know whether or not this license transfer has meanwhile been successful because the developer does not send me any replies to my personal messages. Maybe he hasn't even read them, I really don't know. :(

If my license transfer has been successful, fine; if not, well, I don't care any more and I will just let my license run out. I'm just not willing to wait for replies any more that will probably never arrive here. Great support. :(

I wouldn't worry about it as Dan gave most of us a free license for Beta Testing all these years so if your not going to use VS just don't use it. And if any new users want to Beta Test VS just send Dan a PM and I'm sure he will look after you! Unless you hear different from VoodooShield Dan as things can change without notice.

Thanks,

Daniel
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on January 01, 2018, 10:46:32 pm
Quote
I wouldn't worry about it as Dan gave most of us a free license for Beta Testing all these years ...
I'm not talking about b e t a testing. I have a "general" three-year license that I would like to give away to a CoU member. And yes, I have received a couple of PMs recently, asking me for this license. I would love to give it to one of them, but it seems to me that the VS developer doesn't care, so that this license transfer has probably not taken place yet.

Quote
And if any new users want to Beta Test VS just send Dan a PM and I'm sure he will look after you!
I have sent him quite a lot of PMs recently -- I have never received a reply. So sending him another PM would be pointless. I will just let my license run out instead.
Title: Re: VoodooShield v4 Beta Discussion
Post by: khanyash on January 01, 2018, 10:58:27 pm
Congratulations Dan on VoodooShield 4 Stable and Major release!

I will play a little and post my experience and suggestions later.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on January 01, 2018, 11:27:28 pm
Quote
I wouldn't worry about it as Dan gave most of us a free license for Beta Testing all these years ...
I'm not talking about b e t a testing. I have a "general" three-year license that I would like to give away to a CoU member. And yes, I have received a couple of PMs recently, asking me for this license. I would love to give it to one of them, but it seems to me that the VS developer doesn't care, so that this license transfer has probably not taken place yet.

Quote
And if any new users want to Beta Test VS just send Dan a PM and I'm sure he will look after you!
I have sent him quite a lot of PMs recently -- I have never received a reply. So sending him another PM would be pointless. I will just let my license run out instead.

It's holiday time so give him a break. Like I said don't worry yourself about it, it's not a big deal. I know mine is setup up via my email address and password and from the online VS account so is yours different? I was wondering how you could give it away unless it's not tied to your email address?
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on January 01, 2018, 11:37:12 pm
I was wondering how you could give it away unless it's not tied to your email address?
This is the point. I cannot give away the license myself, of course. The developer, who has so far not replied to my PMs, needs to transfer this license for me. Well, maybe he will do it, maybe he will not. I don't care any more. I can well do without this sort of "support".
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on January 01, 2018, 11:43:52 pm
I was wondering how you could give it away unless it's not tied to your email address?
This is the point. I cannot give away the license myself, of course. The developer, who has so far not replied to my PMs, needs to transfer this license for me. Well, maybe he will do it, maybe he will not. I don't care any more. I can well do without this sort of "support".

VS is mostly developed by one man so you should give him a break, also he has a full time day job so he needs a break like the rest of us. If you don't want to use your license just don't use it. I have been using and Beta testing all new versions of VS since it came out about 7 years ago.......
Title: Re: VoodooShield v4 Beta Discussion
Post by: Buddel on January 01, 2018, 11:52:21 pm
If you don't want to use your license just don't use it.
This is what I will have to do. But it would definitely have been more useful to give it to someone who needs it, which, however, is probably not possible due to the unresponsiveness of the developer.

OK, this was my last post in this "support" forum. I'm now going to ask the admins to remove my account. Bye and Happy New Year.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on January 02, 2018, 12:01:36 am
If you don't want to use your license just don't use it.
This is what I will have to do. But it would definitely have been more useful to give it to someone who needs it, which, however, is probably not possible due to the unresponsiveness of the developer.

OK, this was my last post in this "support" forum. I'm now going to ask the admins to remove my account. Bye and Happy New Year.

Why do you want your COU account deleted?
Title: Re: VoodooShield v4 Beta Discussion
Post by: khanyash on January 02, 2018, 12:22:58 am
Buddel, Dan was busy with VS 4 Beta and its holiday period. Give him a few days and you will get a reply.
Title: Re: VoodooShield v4 Beta Discussion
Post by: ProTruckDriver on January 02, 2018, 12:36:52 am
Buddel, Dan was busy with VS 4 Beta and its holiday period. Give him a few days and you will get a reply.
I believe Buddel deleted his account. I don't see his name listed on the Member List anymore.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Triple Helix on January 02, 2018, 12:39:30 am
He asked to be removed via his COU account so I approved it.
Title: Re: VoodooShield v4 Beta Discussion
Post by: khanyash on January 02, 2018, 01:48:51 am
Wouldn't it be better to start a VS 4 Stable thread?

Official website is voodooshield.com or voodooshield.co? voodooshield.com provide latest stable 4.15 and voodooshield.co provide previous stable 3.59
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on January 02, 2018, 01:19:22 pm
Wouldn't it be better to start a VS 4 Stable thread?

Official website is voodooshield.com or voodooshield.co? voodooshield.com provide latest stable 4.15 and voodooshield.co provide previous stable 3.59

1. Done, just to Admin make it "Sticky"  ;)

2.Official is https://voodooshield.com

Dan should remove that ".co" so that visitors and users would not be confused.
Also, it should change the User Guide because it's outdated and put a link to this forum too!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Tarnak on January 03, 2018, 11:54:08 pm
Ok, I think the database and web server is completely squared away.

You might have to click the Confirm Registration button or exit out of VS for it to act normal.  After you click the button and restart VS, please check to make sure your expiration date and endpoint quantity is correct.  Anyone with a license from any of the security forums should have an endpoint quantity of 10... but if something is not correct, just email me at support @ voodooshield.com and I will fix it asap.

I deleted all of the endpoints and whitelists from the database for a couple of different reasons, so basically we are starting with a clean slate.  Thank you guys!

Like this? ...Hey presto!   Dan, thanks for the extension of licence. :)


I have noticed that my registration has reverted, to expire on 30/7/2018.  I guess the database got a glitch, again.

Not too fussed. ;)
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on January 04, 2018, 12:27:15 pm
The answer to this question is probably so obvious I'm almost ashamed to ask  :-[

My Registration page says 5-01-18.  Now I'm fairly sure this is not US date style, but is it referring to US time (which would be 6-01-18 where I live) or Oz time which would be 4-01-18 in the US...  ??? :-\ :o ?

Does anybody know where to find the Discworld Embassy?  I need an immigration visa :P They don't seem to have date-line problems there  8)
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on January 04, 2018, 12:48:24 pm
An update :)

My bank records say I paid Au$28.28 on 08-Jan-2017... Dan?
Title: Re: VoodooShield v4 Beta Discussion
Post by: VoodooShield on January 04, 2018, 04:58:49 pm
I think almost everyone's accounts are in order, but if not please email me at support at voodooshield.com.

It is much easier and less confusing for me if we fix the account through email.  So if your expiration date is not correct or you need more seats, just let me know, thank you!

I will catch up on the posts I missed asap, thank you guys!
Title: Re: VoodooShield v4 Beta Discussion
Post by: Geri123 on January 04, 2018, 09:56:49 pm
@gorblimey My VS showed expired on 01.01.0001 (today). After closing down VS and restarting it the real time left was show and everything was back as it should be. Maybe it works for you also  :)
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mr.GumP on January 05, 2018, 05:57:31 am
account back to normal
Title: Re: VoodooShield v4 Beta Discussion
Post by: gorblimey on January 05, 2018, 09:34:04 am
@Geri123, It seems the date was indeed Oz time, I got to my box about 30 minutes ago and yes, my licence had expired today, as VS said it would.  Points to Dan there, for using local time, but it would be nice to see an indicator :)

Now to see how to get VS working again...  I'll try the "Reset Registration" button, and redo all my settings. :(

EDIT: No, it seems I must wait for PayPal to extract the money from my bank, then deliver it to Dan.

In these times of Instant Gratification, some things don't necessarily happen immediately!
END EDIT.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on January 05, 2018, 06:44:22 pm
I was just wondering if the registry key needs to be set for VS like all the AV makers are doing because of the Intel thing?
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on January 05, 2018, 06:46:04 pm
This is a site showing ones that have fixed their software. https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on January 05, 2018, 08:24:16 pm
I was just wondering if the registry key needs to be set for VS like all the AV makers are doing because of the Intel thing?
I don't think so because VS is no av. Most people run it next to a traditional av.
If VS sets the key and your av is not ready you will have big problems.
Title: Re: VoodooShield v4 Beta Discussion
Post by: boredog on January 05, 2018, 08:29:23 pm
Was just wondering because Dan mentioned if anyone had issues after the MS update with VS, he thought it would be an easy fix.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Gandalf on January 05, 2018, 08:49:35 pm
Was just wondering because Dan mentioned if anyone had issues after the MS update with VS, he thought it would be an easy fix.
I'm also curious what the issue was that they encountered.
Title: Re: VoodooShield v4 Beta Discussion
Post by: Andi on January 17, 2018, 07:04:27 pm
Was just wondering because Dan mentioned if anyone had issues after the MS update with VS, he thought it would be an easy fix.
I'm also curious what the issue was that they encountered.

Because VoodooShield was not on the Microsoft list of supported AV programs and Dan was just careful and expected the eventual problems afther that MS update patch.
( I think so )
Title: Re: VoodooShield v4 Beta Discussion
Post by: Mr.GumP on January 24, 2018, 03:34:12 am
everything okay in here? has the convo moved?