VoodooShield/Cyberlock

Will do, ty

EDIT: Ok no matter what alerts I get the allow button simply doesn't work

 

I un-installed VS COMPLETELY, re-installed and then google update tried to run (but only had "~" instead of the file name/directory) but VS blocked it so I clicked the balloon and clicked allow but the dang thing don't work period! I can click it all day but it does nothing...the block button works fyi

 

I see, that makes sense now. For some reason VS is not getting the path of the google update executable. Let me see what I can do, thank you for letting me know!

 

Searching for the slow start up of VS

I had some spare time today to research this. I have some old images that I restored to a spare HD.

On one of them VS lit up in about 5 secs once the Desktop (Win appeared. The next one in the series took me back to 100 secs +. Looking through the list of installed programs was that I have installed VMLite with XP mode. Also Windows had been updated but probably more would have found troubles is this was the source.

Does that make any sense to you? Did try uninstalling VM but could not do so.

Anyone else running VMLite?

On another point on the latest version. If I have a USB already connected then VS does not see it. If I connect a second one then that is seen.

 

Thank you for trying to isolate the cause, that will be a big help when you figure it out! I have not tried VMLite, but I am sure a lot of people have.

Yes, there is a bug in the USB label, I will fix it soon, it should be pretty simple! Thank you!

 

I have run into the exact opposite situation as I did last time when exiting Shadow Mode, and rebooting while VS was in Smart Mode. The last time I exit Shadow Mode, and reboot VS's protection was stuck in always on mode even though VS was in Smart Mode. In other words the protection was always enabled even when it should have been disabled due to no risky activity being performed.

After exiting Shadow Mode, and rebooting this time VS no longer recognized my Western Digital External Drive while in Smart Mode. I was not given any prompt when the desktop appeared asking if I wanted to enable protection for USB devices. VS's protection was disabled even though I still had my Western Digital External drive connected during, and after boot. Smart Mode did activate VS's protection when opening my web browser so it seems it just did not recognize that I have a USB device plugged in. It has recognized this same Western Digital External drive, and enabled VS's protection in smart mode for this device until now. I still wonder if it's related to Shadow Defender. I really don't see how SD could cause this without having one of VS's directories excluded in SD. I don't have any exclusions in SD where VS has files or folders. The only exclusions I have is users/user/downloads, and Firefoxes file places.sqlite for saving my bookmarks while in Shadow Mode.

I'm not sure it would be helpful to make a screenshot of my running processes in task manager since VS's protection was disabled when it should have been enabled due to a USB device plugged in. If it was enabled when it should have been disabled then I could see the value of posting screen shots of my running processes because something could be running in the background causing VS to enable it's protection. Unfortunately i'm experiencing the opposite this time. What do you think?

 

You should really add logging for all events that cause VS to enable it's protection while in Smart Mode. You can make this logging optional that can be turned on when needed for trouble shooting. I would suggest having this logging enabled with default settings since it would not have any effect on system performance. Last night when my protection was stuck in always on mode even though VS was in Smart Mode the logs would have been very helpful to see if an application running in the background was causing VS's protection to stay enabled.

 

It does recognized the Western Digital External Drive if I unplug it, and plug it back in again. Maybe coming out of Shadow Mode confused it somehow I'm going to not use Shadow Defender for a while to see if VS continues to have problems. If not then it's probably a conflict with VS, and SD.

 

Why won't the allow button work? ty

 

Ok, sounds good. When I get a chance, I will try VS with SD and see what I find. Thank you!

 

It depends... if it is a cmd or msi issue, that will be fixed very soon. If it is another issue, that will be fixed when we run the engine as a service.

What is the path of the file that is blocked? Thank you!

 

C:\Program Files\Google\Update\1.3.21.153

 

Maybe it's like the issue when I do Disk Cleanup and it runs child process in the %Temp% Folder?

Daniel

 

Thanks.

I don't know the best color but i suggest the white or the yellow.



I use VS in "Always On" mode.
When i chose "Disable Protection", after some minutes (I define 5m), VS shows a popup to enable it if i want.

In this case, when i chose "Activate", it put VS in "Smart" mode.

Is it possible to put it in the mode VS was, when i disabled protection (In my case, "Always On") ?

 

Well, this one is a little odd because really it should not be blocked in the first place if Automatically Allow Program Files folder is enabled... is this enabled in your settings?

But what is really odd is that if you try to manually run this executable, it will not run. But that does explain why it is not running when you click allow. However, when you click allow, it should add it to your whitelist so the next time it will not block it when it tries to run.

There are around 10 or so processes that are just plain odd for one reason or another, and so typically we just put them on the Default Process List. But since this should be allowed since it is the Program Files folder, it shouldn't be necessary to add it to the Default Process List, since I need to clean that up anyway.

So please let me know if that option is enabled in settings, thank you!

 

Oh yeah, I still need to figure out a fix for that! It is similar, but since this is not a protected folder, we have to do something else.

I am getting really close on the cmd / msi fix, hopefully by tomorrow that will be fixed. Then I can finish fixing these other small bugs! Almost there!

 

Yeah, I think white would be cool too! Yes, we could do that, but there was a reason I just put it into smart mode, I just do not remember what the reason was. I will look at it and see, it will be easy to put it into the previous mode, as long as there is not a reason we cannot do that. Thank you!

 

Yes it is enabled

 

I un-installed VS until the next version is released, it is running like crap so I was wondering if these registry entries are safe to delete?

http://i.imgur.com/vJFf9Bm.png

 

hey whatch your language kids

 

I went back to the image that had VS loading reasonably and installed VML. On reboot the loading of VS had slowed down again. So it seems, at least on this machine, that VM interferes with VS. That's as far as my expertise goes, so will have to leave the rest to you.

 

VS keeps forgetting the path of an application I have in my whitelist. It's installed to an external hardrive assigned G:\ . It flagged it today asking whether I wanted to deny or allow it to run. I clicked allow then VS locked up, and the VS prompt said not responding. I waited for about 5 minutes, and it never recovered. Windows began to freeze up so I had to kill VS from the task manager. I'm going to reset my whitelist tonight. It's been a long time since I have done so.

 

Overkill, you are not the only one. The VS allow button will not work for me either. If I try to use it VS locks up, and I have to kill VS from the task monitor. It will not even allow me to shut VS down. This is a pretty big bug! Thanks for posting about it! I thought I was the only one having this problem.

 

VS actually adds the application to the whitelist, but is unable to allow it. Instead VS locks up. After I turned VS back on, and tried to run the same executable that caused it to lock up it allowed it to run without prompting me. I remember when trying to allow the executable that VS showed the path to begin with ~C:\ What does this symbol mean "~". Does it mean allow or deny from anywhere? The actual path of the executable was C:\users\user\downloads

 

That is odd that VS is not automatically allowing this process, since it is in the program files folder.

I assume it is safe to delete those keys, VS does not create them, Windows does automatically.

Edit: So what version works best for you? Are you running the release version from our website? I know you were saying that it wasn't running right, but what were the specific problems? Thank you!