VoodooShield/Cyberlock

Thank you, we appreciate that! Hopefully soon VS will be an additional layer of protection for all traditional and non traditional antivirus . I have to admit, it does work especially well with WSA.

 

It's a great Combo you will see many WSA users using VoodooShield as a second layer and it's great.

TH

 

voodooshield is blocking delegate_execute.exe each time i launch chrome even after I allowed it. Is it just me?

 

Where is it the file located?

TH

 

C:\Users\"username"\AppData\Local\Google\Chrome\Application\33.0.1750.146\Delegate_execute.exe

 

When was the last time you uninstalled and reinstalled Chrome as it should not being running in AppData but in Program Files that was a problem about a year ago with Chrome as mine is installed in Program Files.

HTH,

TH

 

I installed with one month.. following ssd upgrading and os upgrading my system to win8.1

 

Thank you TH! Like TH was saying, basically Chrome should be installed in C:\Program Files. When then install it in AppData, it causes a lot of problems for a lot of developers. They started installing to the C:\Program Files folder about a year ago, I am surprised that it installed to the AppData folder... hopefully they are not changing this again.

 

I had downloaded the chrome standalone setup from filehippo. Does that have to do something with this?

 

Probably so, it must be the old version of Chrome. You might just want to download it from google.

 

Download from here: https://www.google.com/intl/en_uk/c...=en&utm_source=en-et-chromeblog&utm_medium=et and do a clean reinstall of Chrome and make sure the path goes to C:\Program Files or if 64bit C:\Program Files (x86)

http://googlechromereleases.blogspot.ca/2014/03/stable-channel-update_11.html

TH

 

I had the same problem so i downloaded the current build of chrome....still had issues until i found out it was also still in users/appdata in addition to program files.....deleting from Appdata fixed it....

 

Hi Dan,

Information about Chrome and delegate_execute.exe file.

Downloaded after clean install (Windows 8.1 Pro 32-bit) Chrome (35.0.1870.2) from Filehippo.

File location (full path): C:\Users\<username>\AppData\Local\Google\Chrome\Application\35.0.1870.2\delegate_execute.exe

Regards,
Kardo

 

Thank you everyone for the help! I downloaded Google Chrome 34.0.1847.60 beta from filehippo because I could not find 35.0.1870.2. I already had Chrome isntalled, so I uninstalled it and installed the filehippo one. For some reason, it installed to Program Files, kind of odd, huh? Is the 35.0.1870.2 a beta version too? Hopefully Google is only installing the beta version to the AppData directory, and not the release version.

 

Dan,

You can get latest Beta and Dev versions from Softpedia and also from Filehippo.
I just downloaded latest Dev version from Filehippo (35.0.1883.0 Dev).

Filehippo:

35.0.1883.0 Dev (latest) - http://filehippo.com/download_google_chrome/57095/
35.0.1870.2 Dev - http://filehippo.com/download_google_chrome/57050/

Softpedia:

Stable, beta and dev - http://www.softpedia.com/progDownload/Google-Chrome-Download-108166.html

Regards,
Kardo

 

I downloaded the latest dev version as mentioned above (Thanks kardokristal!
And it took me from filehippo to Google and started the online installer.
Anyways it istalled chrome to :
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
so that would fix the issue i guess.
I did have difficulty while uninstalling old version as voodoo blocked " c:\users\"username" \appdata\local\google\chrome\application\33.0.1750.146\installer\setup.exe "

--------------------------

Whenever the voodooshield blocks an app, it gives a notification from tray icon and if we click on it, it will give yet another popup to decide whether to allow, deny or scan by VT.
One little difficulty I face is that sometimes I cannot reach the tray icon notification in time and it vanishes before I could click it.
Why cant we skip the tray icon notification and go straight to the popup notification.
Is there a setting for that?

 

Thank you Kardo!

 

There is in option in Settings / Basic "Deny by Default". If you uncheck this, I think it will work the way you want it to. Also, the balloon in VS 2.0 has a longer duration and we might even make it user adjustable. Thank you!

 

I still get some issues with google update even after chrome installed in c://program files(x86)
This time issue is with I guess Google+ autobackup
c:\users\"username"\appdata\local\google\update\install\{0392ddfb-abeb-436e-b362-f3c39a974e15}\gpautobackup_1.0.24.118.exe
Got blocked.

 

There is an option in Settings / Advanced / Do not whitelist items in the AppData Directory. You can temporarily uncheck this, then start the gpautobackup, and VS will whitelist it, then you can check the option again. We might actually have this disabled by default for VS 2.0, since we are now doing path and hash comparison, so this option is not necessary anymore. The main purpose was to stop malware authors from spoofing legitimate software. Sorry for the two issues, but you should be good to go now! Thank you!

 

Mine seem to be unchecked by default. And I havent touched default settings yet.

----------------
What is the difference between "smart" and "always on" ?
And as it has ben mentioned that voodoo takes a snapshot of the syetm each time you enable it. What is this snapshot exactly? A text file logging current apps and executables and their locations? Or an actual copy of the system like a system image? Does it take up any significant space?

 

We want the beta. we want the beta. we want the beta.

 

voodoo still blocked an nvidia process.
c:\users\"user"\appdata\local\nvidia\nvbackend\packages\000058f8\dao.18054780.exe
Even with option in Advanced settings Do Not whitelist items in Appdata directories UNCHECKED

 

Hehehe, I agree, I cannot wait to release it. I am 99% sure it will be ready by Sunday night. After Rajesh and I finish, I have to email it to someone for approval Sunday night, but we should hear back from them quickly. Then I will be able to post it on Wilders. Thanks again!

 

Hmmm, that is odd. I just reset mine to factory defaults and it was checked by default. We could troubleshoot it a little more, but since 2.0 is pretty much ready, we should wait and see how it does. It is completely different under the hood.