VoodooShield/Cyberlock

BTW, if anyone is having trouble confirming their registration, please download and install the newest version. We just uploaded a 0.94 with the registration fix. Hopefully it will work! Please let us know!

 

Can I get the MD5 Hash for the new file?

This is what I have! MD5 B7EC3089B337CD891563A1E9EF422D47 and now the new one? MD5 7646EBDD7BDD2C30C3D030B283E8DCC6

Thanks,

TH

 

I keep getting this window on every boot up on Win 7 x64 but not on Win 7 x86 and I removed my personal info!

TH

 

Sure TH, 7646ebdd7bdd2c30c3d030b283e8dcc6

That is odd about VS forgetting the registration info on 64 bit, let me try it on my 64 bit system to see if I can duplicate the problem. That is really odd though, the changes we made should not have created this problem. I will let you know! Thanks again!

 

It has always been that way on Win 7 x64 and I uninstalled VS rebooted and installed the latest version with that MD5 and still the same!

Thanks,

TH

EDIT: And there both Laptops if that matters!

 

You might try this... Can you delete the contents of the following folder?

C:\Users\User Name\AppData\Local\VoodooShield

Mine is working fine, hopefully that will fix it for you. If not, please let me know.

 

I deleted the contents a rebooted twice and still no go I have to click to confirm registration everytime!

TH

 

Hmmm, that is odd, we will have to look into this. Thank you for letting us know!

 

I made sure that my other security is not blocking VS and I have the same on both!

TH

 

I have always had the same problem. The only way I can keep from re registering is to manually start it after connecting to internet. I think it only works if your internet is always on. Gets used less and less around here with as much as our computer gets restarted.

 

On a x64 OS?

TH

 

Ok, now it is starting to make sense. We have a bug on reboot when there is no internet connection since VS cannot talk to the registration server. I believe both of these issues are symptoms of the same problem. We will resolve these issues in the next release, which should be about a week from now. Thanks for the feedback!

 

Great, also I'm still getting this process blocked I have to leave on Train Me? Win 7 x64 again!

TH

 

This is very hard to explain, but I will do my best!

VoodooShield WILL block processes from time to time, especially processes that that require, for example, rundll32 and dllhost. The whole idea of VS is if the user did not ask to run something, it will be blocked. But if the user does ask to run something and it is blocked, then the user should train VS to allow it. VS puts the user in control of their computer, and does not allow unexpected processes to run.

Now, there are exceptions, for example, scheduled tasks. VS will deactivate after 5 minutes to allow scheduled tasks to be learned and run as expected.

Over time, VS will learn the processes you want to run and allow them, while keeping the viruses and malware out. We did not want to prompt the user to allow processes, since this is annoying and dangerous.

 

Triple Helix
Sorry I took so long getting back, Win 7, 32.

VoodooSield

After clearing whitelist and running on training mode for a day when not connected then left set in training mode overnight not connected, I have gone to Alway On and it is laying very quiet. I tried installing a desktop gadgit and it intercepted. I do like the idea it stops processes coming from sources it doesn't recognize . In theory you could train it to allow svhost from a number of sources. Fix the start up license issue and make the whitelist user edit and put a price on it lets go!

 

Well I think you need a Expert Mode where a user can add processes to the White List! Because getting the same processes blocked all the time even though I had in training mode for 6 hours open all my programs then set it to smart mode then I open FF then the file gets blocked again so something is not working correctly ATM! Maybe it's a 64bit issue?

TH

 

Triple Helix
Have you tried running a internet session in training mode? I did that last night before going to bed beings I am still using all my other security software along side VoodooShield it didn't concern me just as you are I'm sure. Then I left it in train me mode unconnected overnight and went to always on this morning and have not had a blocking in error at all today. My guess is process in F.F. is firing svhost and the source hasn't been allowed yet. Good Luck

 

I have it on for 7 hours now in training mode and still get a pop up when I switch to Smart Mode when I open FF?

TH

EDIT: I just did a clean reinstall and will leave in training mode for the day!

 

Yes, this is what I meant, thank you!!! It just takes a little while for VS to learn everything, especially when certain processes fire other processes. We have an idea that will help alleviate this issue in the next release. It might still have a couple of UNNECESSARY balloon notifications, but we should be able to reduce it by 90% or so.

We are also going to fix the registration problem with no internet connect, and add some expert features, like the white list manager. We just have so many things to do!!! But we are very, very close! It has taken us 9 months to get to this point, and we think we will be completely finished within another month.

I remember when we first started, we had some serious road blocks to overcome, but we are past all of those now. We just have to tighten up the code and add some features so that the user experience is the best we can possibly make it.

Thanks again for everyone's help!

 

So for so good after a clean reinstall it's working as it should without the pop-ups opening FF!

TH

 

Good to hear!

 

I just noticed the setting in options to deactivate after 5 minutes of inactivity.Actually the icon was red on the Always On mode when I came back to the machine. I unticked it, I'm just glad there was a good reason and my mistake for missing the setting in the first place.

 

Sounds great! Thanks for letting us know!

 

Yes, we could always disable deactivation while in Always ON mode, but some users might want it to deactivate even in this mode.

 

It has behaved perfectly here all day on Always On mode. I think the option to reset the whitelist is a lifesaver at this point. A log file would be nice for trouble shooting. When it shows the full path of what it is blocking is a good thing also.