VoodooShield/Cyberlock

Hi C_E

Many thanks for the heads up...that would most likely explain it... I will therefore wait patiently for the beta to settle down so that Dan can launch it a a release and start raking in the money (hopefully...as this app deserves nothing less).

Now...just need an answer re. the time a manual snapshot should take...unless that is also not yet ready...which again might explain what I am seeing...

Regards, Baldrick

 

I am still finding that VS is still silently blocking programs. It is only when you kill VS that everything springs back into action again.

One example - looking at at a folder in explorer VS slowed the machine to a crawl and in the end did not show the thumbnails.

One other point is automatically submitting files to Virus Total does not work on a slow connection. I have turned the option off. Maybe there should be a limit set on the file size, or a warning that it might take a long time.

 

The only file I get blocked and no notifications and I'm not sure if I should be notified?

Daniel

 

Hey, sorry everyone, it was a rough weekend... a lot of onsite work. I think I am getting close to figuring out the last big issue with VS silently blocking everything. I will read and respond to the posts tonight, sorry for the delay!

 

No problem, Dan

Everything is looking good it appears apart from that...so kudos at this point. We will be patient whilst you figure it.

 

Thank you Baldrick! As I was saying, I will read the other posts later, but I wanted to mention something real quick...

If anyone is having ANY issues with VS after installing and rebooting the first time, please try this...

1. Make sure all versions of VS are uninstalled, and reboot if you need to uninstall an old version.

2. Install VS 2.11, but do not reboot yet. Run MSCONFIG and uncheck Voodooshield for now, then reboot.

3. Reboot and wait until you computer comes up completely, then wait about 30 more seconds, just to be safe. You can double check the task manager and make sure that under Services, VoodooShieldService is running, and has a PID. Even then I would wait 30 seconds or so, just to be safe.

4. Then start VS from the desktop icon. It should work from then on, so you can check the MSCONFIG box again if you want.

Please let me know if anyone tries this and if it fixes the various issues that occur after first installing VS.

I think what is happening is that the service is not finishing doing its thing before the GUI launches, and it is creating multiple issues. Since it is only First Run where both the service and the GUI does a lot of stuff on startup, it should be fine after the first run. I had not experienced this issue until this morning, but once it happened to my computer, it was a lot easier to figure out what was going on. At least I think this is what is causing several different issues after first installing VS. We will see, right? .

If this is the case, it is an extremely easy fix and will be included in the next release. Then we just have to track down the bug where VS is silently blocking everything, then we should be good to go! Thank you!

 

Hi Dan

The above suggestion...just to see if it does make any difference and I will let you know if I spot anything having changed. Had not noticed any major issue but you never know...I might notice something working better.

Regards


Baldrick

 

It seems to be working well, other than my already noted XP issues.

 

Quick update - Ok, I THINK ALL of the boot issues are resolved, and believe it or not, the VS blocking everything silently is almost fixed. Well, I know what is causing it, and I think I know what I need to do to fix it . So after I try this fix and test it for 8 hours or so, if it tests ok, I will post it soon. I also have to reply to quite a few post, sorry, I will do that asap. Thank you!

 

Hi Dan

Does seem to have made a difference...processing seems a little smoother than before which suggests that the beta may have been introducing a very slight lag to processing prior to trying your 'workaround'...may be imaging it but I suspect not. Kudos for the suggestion. All else running well here with .11 beta.

Regards


Baldrick

 

Quick update... I should be finished very soon, sorry for the delay!

 

No worries we're all waiting patiently.

Regards
Gordon

 

+1

 

I really will go back through all of the posts asap... I have just been working on this last big issue of VS silently blocking everything after a couple of hours. I spent somewhere around 100+ hours on this issue, but I THINK it is finally resolved.

But I just wanted to leave myself a quick note .

Note to self:

32bit dll's belong in the 64 bit folder
64bit dll's belong in the 32 bit folder

If you are using Microsoft WMI, make sure you do not look for 64bit processes, especially if you tell it to look for 32 bit processes .

Oh, and also, make sure you do not have a typo that Cutting_EdgeTech discovered that blocked trustedinstaller.exe on first run .

Hehehe

Anyway, we are almost bug free, sorry for the issues. I guess that is all part of the fun, right? . We will all laugh about this very soon . Thanks again!

 

http://www.youtube.com/watch?v=hfuERD3UOS4

 

hehehe, I am not sure we will laugh quite that hard, but yeah, something like that .

It is funny how this whole thing has developed the last 3 years. I just had a silly idea that if your computer is on the internet it should be locked, and that it would toggle, depending if you were are risk or not.

That is (not that I have to tell you guys), VS would take a snapshot of your computer before it was on the internet, and once it was on the internet, it would only allow what was previously allowed.

But really, if a computer or device is on the internet, shouldn't it be locked .

BTW, so far so good on the final fix for the silent blocking issue. If it holds up, I will release it very soon.


Thank you guys!

 

I can't wait!

 

...but I have to, because I am not in the snapshot that VS installed.

 

Quick update... I am getting very close to working out all of the bugs, it should be ready and pretty much bug free by the end of the weekend!

 

I haven't been keeping up with this thread lately so forgive me if this has been discussed already... I was testing VS against some malware and anytime I click quarantine nothing happens? How does VS quarantine files and where are they stored?

 

Hi Overkill

It does not quarantine files or apps...it prevents/blocks them from executing unless they are whitelisted.

 

Then why does it say quarantine? it's misleading

 

It seems to be working well other than the quarantine button, the only problem is that it takes too long to load at startup