VoodooShield/Cyberlock

Hi Dan, am mystified since as far as I am concerned I cannot replicate the issue that either Cutting_Edge or djg05 have reported. Any tips on how to reproduce would be welcome so I can help to debug.

Regards, Baldrick

 

Which problem that I reported are you referring to?

 

Hi CE, this one. Did I get the source wrong? If so then apologies...no slur intended.

 

No, you got it right. I'm still experiencing that bug. I check my user log regularly, and I started to notice that after many days of use the user log hardly changed. The log mostly contained Firefox executions with only a handful of other applications showing in the log. I decided to run most of the applications on my machine to see if VS was logging their execution, and only a few of them were being logged. I think Dan was able to reproduce this.

 

I just updated to 2.10, and I think i'm experiencing the same CMD run as admin bug reported. I would say the bug existed in 2.07 as well. I just did not check for it then. If I run CMD as admin there is a brief pause, and then the VS tray icon flashes. I do not get the notification bubble from the tray icon, and VS does not go to the tweaks tab. I'm using Windows 7X64 Ultimate.

 

Phew...cheers...well relieved I am...I thought I might have cast a slur...

 

When I updated from 2.07 to 2.10 it did not retain the command line string added yesterday. There needs to be some way of knowing which strings need to be retained in the command tab during an update because all of them will not be hard coded. Well, got to run. I will be back later this evening.

 

I know what you mean, that is why debugging is so difficult for everyone involved . If we can reproduce a bug then it is typically easy to fix, but if we cannot, it is really hard .

 

Hmmm, this bug was originally for Windows 8.1... I will have to check 7 since I made the changes to fix 8.1 (I probably broke this feature for 7 ). I thought I checked it last night after I made the changes to fix 8.1, but maybe not . I figured out this morning that the same fix that I had to do for cmd also applies to a few other processes in the Settings / Tweaks tab, so I will take care of all of this at one time, most likely tonight... AFTER the Kansas City Royals game .

GO ROYALS .

 

The commands are stored in C:\ProgramData\VoodooShield\Settings.dat, and yeah, we do not want them to disappear after an update. I will look at this tonight as well, thank you for letting me know!

 

Every time, after uninstall, reinstall VS and reboot, I keep getting this popup from WSA. I wish there was away to make "Allow Always" stick. But, no I get to see it twice, always.

Maybe, TH can clue me in, as to how to get the popup to stop recurring.

Spoiler: Screenshot

 

Yeah, TH or Baldrick will probably know off the top of their heads! We need more questions like this .

 

I hope, they will know.

In the meantime, I am still getting these here

 

If you are referring to the user log issue I reported then that should be the easiest thing in the world to reproduce so I have to assume that bug does not affect you. What OS are you using?

 

No problem!

 

check your WSA firewall rules.First, the VS program isnt trusted by WSA so allow it and then check WSA firewall settings. You may have it set to alert on any untrusted program, which VS is.

 

The command line string I reported not showing up in the command tab after updating VS is there now. It showed up after a reboot. Humm... strange.

 

Bug with cmd is fixed.Thanks!

But on my machine VS block all program downloaded from internet without any notifications.I uncheck deny by default and the result is the same. No check files in VT simply block them.No log entries.No user interactions like block, sandbox ,allow...

 

Hi Dan

It happens with a couple of programs that like to start at boot. One in particular is Opera Dev which you can find here

http://www.opera.com/download/get/?...ce=desktop_blog&utm_campaign=desktop_side_bar

The program that starts it is "Launcher.exe" which sets itself to autostart. I could stop it other ways but thought that VS should cope.

 

Hi MrGump

Indeed, I make sure that the VS components are declared as 'Allow' under the 'Block/Allow' tab under PC Security, and then check that under 'Active Processes' the VS components are not marked as 'Block' (they are most usually flagged as 'Monitor' as VS is an unknown item, especially at this time when the beta is underway.

Hope that helps? Baldrick

 

On this one I also get the prompt but only usually after I have clean installed a new version of VS otherwise generally a couple of clicks 'Always Allow' option and I hear no more until the next beta.

 

Yeah, that is odd, hopefully it was just a fluke, but maybe we should keep an eye on it. Please let me know if you notice that again! The command lines are stored in C:\ProgramData\VoodooShield\Settings.dat, so as long as that doesn't disappear, it should read it fine. Thank you!

 

Cool, thank you!

I am not sure what you mean by programs downloaded from the internet. Is there any chance you could make a quick video so I can see? If not, can you please let me know the steps to reproduce this behavior? Thank you!

 

Hey David, I downloaded Opera Developer, but "Launcher.exe" did not set itself to autostart, so I am not sure what is going on here. Is there an option in Opera to enable and disable autostart of Launcher.exe?

Just a thought, what if you put VS in Training and rebooted? Does that make a difference? Thank you!

 

Cool, thank you Baldrick!