VoodooShield/Cyberlock

Hi Baldrick,

No such luxury for me, just my Surface Book laptop, and no VMs. Real live testing on my system!

 

You are a brave one, Tarnak...I hope that you back up/image regulalrly just in case...?

 

I guess Macrium Reflect
But i also install VS on a "real" machine, even beta versions

 

Ditto, suddenly again. But no snapshot, etc. this time. Maybe Dan is working on the back end.

 

Not sure what is happening but have to say that on the same system v3.59 is nicely quiet & appropriate when in SMART mode...but if I install v4.03 on the same system and do the same activities it gets awfully 'chatty' and reports apps/dlls/exes, etc. as as being potential exploits & potentially malicious where as the same are not flagged under v3.59.

Hope that Dan can get to the bottom of this as otherwise I would say that v4 is just not as good as v3.59...at present.

Regards, Baldrick

 

A word from Dan: https://malwaretips.com/threads/voodooshield-discussion.63827/page-39#post-671450

 

Cheers, pablozi

I will give that a try on my test system and hope that the previously mentioned issues are resolved, or at least somewhat mitigated by this new release.

Regards, Baldrick

 

I had an unknown file VS gave a popup on. At the time I blocked it. Later I looked up the file and it belongs to Windows Defender.
Went back to user log and tried to whitelist the file and got error. I clicked quite and VS did shut down.

 

, have just cleam installed v4.04 and it so far seems a lot quieter than v4.0. WIll have to try out osme of the activities that wrating the popups and will post back with the results...most likely tomorrow...but certainly looks promising.

Cheers, Baldrick

 

Similar experience here with clean install, all issues I had seems gone. Fingers crossed...
Enjoy your Sunday.

 

HI VecchioScarpone

Thanks for the confirmation from your side ...whilst all appears OK at present I have noticed that any rules that I create do not appear to be being saved or if they are then they are not displaying when I look in the Rules tab in VS. So there is something not quite right there as I am asure that under previous version of v4 the rules where appearing when one wanted to review them.

So perhaps a final little bugette for Dan to fix if someone can get the message to him.

Regards, Baldrick

 

Consider it done.

 

@Baldrick Message gone by speed post He He.

 

Nice, thanks...I will not frequent the MT Forums...not with what I think about them there, what they do & how they do it (just my personal view) so I was about to send Dan and email...but given what you are saying I will desist.

Regards, Baldrick

 

You are welcome and I respect your decision in regard "the other forum" as it is sometime referred to in here.
On this type of "fora" things should be taken with a great pinch of salt I reckon. Not that in my old age I have learned much as I still get caught more time that I should
Thanks for the insight I shall tread carefully. Shame we lost Dan in here. I wish things could revert back soon.
Regards.
VS

 

I installed VS v4.04b beta over-the-top. The rules wizard popped up for the first time since version 4.01 beta, if I recall correctly. Because, I was not sure about the choices to make for creating a rule, I chose to cancel.



Also, I enclose a section of the DeveloperServicelog which shows an exception, at about the time I updated to v4.04b beta.


[09-17-2017 03:14:13] [INFO ] - VoodooShieldService.OnSessionChange: ConsoleConnect
[09-17-2017 08:54:40] [INFO ] - VoodooShieldService.OnSessionChange: SessionLogon
[09-17-2017 08:54:54] [DEBUG] - DriverCommunicationService::Connect 10 threads
[09-17-2017 08:54:54] [DEBUG] - ->DriverCommunication.ctor
[09-17-2017 08:54:54] [DEBUG] - DriverCommunicationService::Enter main loop
[09-17-2017 09:13:46] [DEBUG] - DriverCommunicationService:isconnect
[09-17-2017 09:13:46] [DEBUG] - DriverCommunicationService::Exit main loop
[09-17-2017 09:13:46] [DEBUG] - DriverCommunicationService:isconnected
[09-17-2017 09:13:46] [DEBUG] - DriverCommunicationService::Client disconnected
[09-17-2017 09:15:27] [INFO ] - User Log Initialized
[09-17-2017 09:15:27] [INFO ] - Snapshot file Initialized
[09-17-2017 09:15:27] [INFO ] - Service started
[09-17-2017 09:15:29] [INFO ] - Driver communication service started
[09-17-2017 09:15:47] [DEBUG] - DriverCommunicationService::Connect 10 threads
[09-17-2017 09:15:47] [DEBUG] - ->DriverCommunication.ctor
[09-17-2017 09:15:47] [DEBUG] - DriverCommunicationService::Enter main loop
[09-17-2017 09:16:00] [ERROR] - Exception in VoodooShieldWCF_CleanupWhitelist: String was not recognized as a valid DateTime.. at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at VoodooShieldService.SnapShotStorage.GetAllProcess()
at VoodooShieldService.VoodooShieldWCF.CleanupWhitelist()

 

So much for being a user-friendly computer lock.

 

@Tarnak

Though the create rules request hasn't show up for me yet, I decline to create rules because my grey matter goes into a spin, what to do...

 

It would be good if Dan could give an example of how to make an appropriate rule.

 

In the end what will make it or break it for me sticking with VS, is that VS is safe without my input in create rules. Though I understand it is my limitation and not VS.
@Tarnak
Yes it would be nice some example how to create rules.

 

It was at one time and it will be that again I'm sure, because betas don't have any problems...right?

 

Yeah, but about these 'rules'?

 

1. Is this the ... "Voodoo Shield" forum ?

2. I have been using VS PRO since Aug-2017... 6 weeks ago.
- running Free Bitdefender with VS v3.59
Q: is there a later full release of VS (non beta) ?
- VS is a breeze to work with, it has already saved my sanity when it stopped ransom wear during a desperate moment of self inflicted stupidity.
- BD has not been a good experience on other PCs where BD-IS PRO had to be clean installed 4 times in 10 months.
- Free BD reacts to new EXEs and quarantines the EXE, at which point my productivity stops dead, while I instruct BD to add the EXE to the "exclusions" list.
- Free BD does not offer any alerts, msgs, or anything.
- When a UI fails to show or an app does not open, then I have to open Free BD to see where the problem might be

I have had it upto here with BD
Any suggestions what to replace Free BD with ?

-----------
SPECS:
Win-7 PRO x64
VS v3.59
Free Bitdefender (auto updated 3x daily)

 

Welcome to Wilders'.

Yes it is a VS thread, no longer maintained by Dan, the dev' of VS.

Not a BitDefender thread though. What Operating System?

Edit: Thanks @stapp