VoodooShield/Cyberlock

Hmmm, that is odd... TH or Baldrick, do you guys typically have issues with WSA updates? Thank you for letting me know Tarnak .

 

You guys might have seen this already, but I figured I would post it just in case... it is pretty freaking dismal if you ask me.

https://www.mrg-effitas.com/wp-content/uploads/2016/08/MRG-Effitas-360-Assessment-Q2-2016.pdf

When are we going to collectively decide that new, non-whitelisted code is not OK to run arbitrarily?

 

BTW, I thought this was pretty cool... Microsoft included VoodooShield / VoodooAi in their latest Azure newsletter.

https://info.microsoft.com/CO-Azure...IMldIbGMyd1dPUG9HMU11WE1xaVI2RmdsMCtBRT0ifQ==

 

Hi Dan

Hope that you are well...yes. indeed...this now appears to be fixed/working well...thanks!

Regards, Baldrick

 

Hi Dan

That is what I see and have always seen with WSA updates...and in a way I quite like it as the WSA updates are so silent that this seems to be the only way of being notified that WSA is being updated...

I will have to check next time as to whether or not it is caught/presented as a false positive (that I do not recall that) and get back to you on that.

Regards, Baldrick

 

Yes - still happening, see screenshot.
Running Win 7/64
VS 3.44

Thanks for all your good work.

 

I have had a mixed bag with WSA updates. I used to run VS in AutoPilot mode and VS would pop up blocking it and I allowed it manually. I then changed to Always On and several WSA updates have since been done smoothly without any intervention by VS. Until yesterday that is when I was informed that there had been a new WSA update, checked my system and found that mine had not updated. On checking the VS User Log I saw that it had blocked the update but never saw a VS prompt. If there was one, I must have been away from my PC. I still have VS in Always On mode and WSA has not yet tried to update again.

 

Well, that is odd as, as far as I know, the updater for WSA, against which the first detection by VS would normally take place, has a different file name with every update, and so missing one should not result in missing future ones as a result of a block. However, if it was the installer itself that was blocked then I believe that what you say is possible...but as to why you did not get a prompt...I cannot say as I get at least 3 VS prompts per update.

 

Thanks for the input Baldrick. It was the wrupdatexxxxxxxx file with the unique number that was blocked. Perhaps it will try again shortly.

However I am somewhat curious as to why it has blocked the update on this occasion whereas I can see in the log previous entries where it was allowed and there were definitely no prompts at the time.

EDIT Here is the blocked entry:

 

Ah, OK...yes, in that case I would try it again (may even be worth deleting the entry in VS...not that this should change things but you lose nothing by doing so) or at least monitor for the next WSA update.

As to why no prompts...that I cannot say as I always see prompts, as previously advised, and most certainly for the wrupdtexxxxx file.

Perhaps Dan can take a look at this as and when he has a moment of quiet time?

Regards, Baldrick

 

hopefully, one day VS will become a complete solution
after you finish implementing all high priority features, please have a look at local sandbox so we won't have to install sandboxie or comodo to run suspicious files

 

cache
do you have your vs set to deny by default-uncheck to show prompt instead of balloon? in advanced set to paranoid? and always on mode?

 

Baldrick

where did you get the VoodooShield v3.58 Beta? the latest in Dan's sig is 3.45. the one I am using.

 

He had me good cause I went checking for VoodooShield v3.58 Beta,to find out 3.45 beta is all I can find.

 

Yes - I leave Deny by Default checked, No it is set to balanced at 100% and Yes I have been running in Always On mode for at least two months now. The first two settings are, I believe the default settings.

My point though is that I was using these same settings when WSA updated without intervention from VS on at least the last four occasions. The only thing that has changed has been the Beta versions of VS. I am currently using the latest 3.45.

 

Cache

there is defiantly some bugs still in 3.45. I lost my desktop icon. still not sure if that was intentional or not but thinking it was not because you then lose the option to see if a usb stick was inserted. seems like with ever new version of beta's to clear one problem another accurses.

 

Hi boredog

My apologies...this was a typo on my part...I updated the version of the wrong app in my signature line ...now corrected...thanks for pointing this out.

Apologies for any confusion caused to you & Nutty Kutchie...and another members.

Regards, Baldrick

 

Is there a way to reset the "Threats Blocked" counter on the top of the UI. I know there is a button disabled on the free version(whicj I'm using" but I'm hoping there
is another way to do it.
Thanks

 

In the licensed version, you can clear the threat blocked from the Utility Settings. In the free version I would imagine that you would have to uninstall VS, including the VS Program Data, and then do a clean reinstall.

 

That's what I was trying to avoid
What features does everyone use on the paid version that made them decide to pay for it(apart from supporting an excellent product)?

 

Most of the VS users who subscribe to this thread are VS Beta testers to help smooth out bugs and glitches in the newer trial versions and are given a free licence in return.
As you have been a Wilders member since 2008, if you ask Dan nicely he will probably give you a free licence as long as you report back with any problems you encounter whilst using VS and help with it's development.

Gordon

 

"if you ask Dan nicely he will probably give you a free licence as long as you report back with any problems you encounter whilst using VS and help with it's development."

Yes and it is for two years too boot

 

+ up to 10 pc's I do believe

 

Correct

 

I put VoodooShield back on seeing that there were positive thoughts on the latest version. Did the PC things that would previously make VS freeze, interfere w/certain exe, etc. So far, putting it thru the paces works. BIG thanks to developer for making VS all right so far, also have to say it was likely partially my machine. Updating BIOS took care of that.

Edit: The only question is the desktop icon. If you click on it, there's a ding-a-ling and the little tray icon is flashing. Can you just eliminate the desktop icon without any ill effects? Sorry if this was asked previously.