VoodooShield/Cyberlock

Thank you for letting me know... we will have to look into this. I think this is because the sandboxed (and other "special" processes), did not start with a drive letter, but now they do. I think the lag is due to the blacklist and VoodooAi scanning... are there any other issues with this besides the lag? Thank you!

 

None noticeable for the moment.

 

Thank you for letting me know... I already know what is wrong, and it will be fixed in the next version. Basically, I forgot about the "Allow by PID" feature... it is an easy fix.

 

UPDATE: With v3.51 I can confirm that Adguard is updating itself automatically without closing VS. Good work, Dan.

 

I made a short video about it on my YT channel (https://youtu.be/2Crkou4Fotw).
Should I removed or leave it?

 

Can anyone facilitate a copy of v3.50 installer to rollback from v3.51 please?

 

Check: Conversation\pm

 

Yes, it's on page 543, post #13558. I'm also getting a lag in app launch that wasn't there with v. 350.

https://www.wilderssecurity.com/threads/voodooshield.313706/page-543

 

Thank you both. Got it.

 

What is more advisable for rollback from 3.51 to 3.50. Overwrite existing installation or full uninstall?

 

I did run JRT and Adwcleaner for a regular maintenance and VS kept blocking the process at every step. On JRT VS warned also that "A program is trying to close VS, do not allow as this may compromise your system (something like that)."
Is this normal?
Should or shouldn't I exit VS before running JRT and Adwcleaner?

 

WAs trying to run a script file in cuckoo and got an error. because I have remote desktop turned off on my computer? I didn't know it had to be turned on to use cuckoo.

 

I'm a little confused - just where do we stand with 3.51?

 

Seriously, with 6 to 8 gb of Ram being the norm now days, that 40 to 60 mb is a drop in the bucket, and what good is it to have that much ram if you do not utilize it.

 

People! Dan asked in the past about memory usage so I was just posting info for him to see so it's nothing more, it's working fine.....

 

I'm "blessed" with memory leaks, so speaking only for myself, I'm interested in the variations people show here and how they develop over time. It's curiosity and interest, that's all. VS is very stable, I know what the culprits are on here.

 

My statement was a generalized one, not directed towards any here trying to narrow down leaks or reporting to the Dev as asked, but to those that still have concerns about applications using 60/80 or even 100 mb of ram, which should be no issue now days unless your still running windows xp with only 1 gb of ram, of which yes, you should monitor these things. No offense was meant.

 

3.51 has been running on my system for over 24 hours now and is as solid as ever. I installed over the existing version as usual. Using a modest 33mb of memory for both processes in Always On mode.

There is a warm and fuzzy feeling knowing that my computer in locked and VS has my back and will stop any nasties at the gate.

 

+1

 

vs3.51 just blocked adobe flashplayer 221 update for firefox. flash update for chrome and ie11 installed no problem. i clicked allow for firefox. win764bit

 

FWIW, with VS 3.51 I am experiencing no extra lags with Sandboxie (but I am using Firefox), or FIDES.

 

VS 3.51
Every thing is perfect ,