VoodooShield discussion

[danb]

ok, I just want to be a part of this beta.
VS is trying to connect sf.symcb.com(23.51.117.163) what is this website? is there any problem if I don't let it reach the address? thnx

Yeah, off the top of my head, I believe that VS is checking the validity of a digital certificate. Either way, I would not let a firewall block any of VS's web requests... they are all legit and necessary, I promise .

 

[danb]

Got some false positive detections too...

Yeah, the conhost and the wmic are the two that I mentioned earlier... I am going to have to figure out a fix for those.

The others are a result of the new option that scans child processes of whitelisted items.. I mean, it is helpful to scan these items (because of packed installers and the like), but we should probably not scan items in Program Files (for example). Basically, we want to make sure that anything that needs to be scanned, is scanned... but nothing else. Either way, it is super, super easy to change in the code.

 

[danb]

Issue for me with the registration, first time it went fine and returned my accurate expiration date, after a restart of the PC however
it needed re-registering and then threw this error:
View attachment 165998
Reinstalled, made sure the FW was not blocking, ect ect. Nothing worked and the way you re-worked this it is useless to have
installed if it cant register, so for the first time in years I am without VS.
Will try again in a few months. PeAcE
PS: the correct email address is not displayed in the SS, but the one I entered was correct. I don't display my real Email acct's anymore in Screen Shots, I used to.

Sorry about that... did you try to click the Reset Registration button? It should fix the issue, if not, please let me know!

 

[danb]

Nope. Did clean install. Service set at Automatic. Does not start.

Event viewer reports...
Service cannot be started. System.Exception: StartProcessAsCurrentUser: GetSessionUserToken failed.
at VoodooShieldService.ProcessExtensions.StartProcessAsCurrentUser(String appPath, String cmdLine, String workDir, Boolean visible)
at VoodooShieldService.VoodooShieldService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Hmmm, that is odd, I will have to look into that, thank you for letting me know!

 

[danb]

Thank you guys for letting me know that the registration is working now (for the most part). I will catch up on the other posts I missed asap... I am totally worn out and need to take a break.

 

[_CyberGhosT_]

Where is the "reset" button ? I can only access this:

 

[scootnod]

It looks like if you uninstall the old version before installing the 4.0 beta version it removes the registry key C:\Program Files\VoodooShield\VoodooShield.exe from HKLM-Software-Microsoft-Windows-CurrentVersion-Run.
You can manually add it back by creating a new String Value called VoodooShield with the vaule C:\Program Files\VoodooShield\VoodooShield.exe in this location.

 

[VecchioScarpone]

Where is the "reset" button ? I can only access this:
View attachment 165999

Is this what you are looking for?

 

[VecchioScarpone]

Dan
At your time and convenience:
Just noticed a significant slow start when I fire my VPN. Also when dealing with Windows Settings.
The user log does not report any issue.

 

[Deleted Member 3a5v73x]

Just noticed a significant slow start when I fire my VPN.

I also encounter strange delay/slowness with VoodooShield detecting stuff and F-Secure Freedome VPN. Same, VPN is allowed and no issues or blocks in logs.

 

[shmu26]

Installed VS 4, it does not start up at boot, even though VS service is set to automatic. I had to add VS manually to startup folder.

 

[Deleted Member 3a5v73x]

Installed VS 4, it does not start up at boot, even though VS service is set to automatic. I had to add VS manually to startup folder.

This was in automatic reply from support at voodooshield com about start issues.

[Also, if VS is not starting on Windows startup, it is probably because the old service was set to (Automatic) Delayed Start. In this case, you can either manually change the VoodooShieldService Startup Type to Automatic, or you can just uninstall VS 4.0, reboot the computer, and reinstall it.

 

[frogboy]

I think I might wait to upgrade till all the bugs are sorted out.

 

[shmu26]

This was in automatic reply from support at voodooshield com about start issues.

thanks. I will try uninstall.

 

[shmu26]

This was in automatic reply from support at voodooshield com about start issues.

[Also, if VS is not starting on Windows startup, it is probably because the old service was set to (Automatic) Delayed Start. In this case, you can either manually change the VoodooShieldService Startup Type to Automatic, or you can just uninstall VS 4.0, reboot the computer, and reinstall it.

@danb , neither of these fixes worked for me.

 

[VecchioScarpone]

The way it worked for me was doing a complete uninstall with Revo.
Download the latest version again. Did a clean install and it worked fine. (Twice just for the record.)

 

[shmu26]

The way it worked for me was doing a complete uninstall with Revo.
Download the latest version again. Did a clean install and it worked fine. (Twice just for the record.)

@danb, the problem is that it starts up in one user account, but not in the other. Weird.

 

[shmu26]

It is a good idea to go into settings and check the command lines, to make sure none are being silently blocked. I found one block. It was an unimportant windows process.

 

[_CyberGhosT_]

I got my issue solved by installing 3.59 (b) and updated from there with the 4.0 installer. I lost my settings, but the registration took and
survived confirmation. Now it just has to survive a reboot. I will do that later and report back.
I post this as a sort of workaround in case anyone else gets that bugged 4.0 registration issue. PeAcE

 

[shmu26]

It looks like if you uninstall the old version before installing the 4.0 beta version it removes the registry key C:\Program Files\VoodooShield\VoodooShield.exe from HKLM-Software-Microsoft-Windows-CurrentVersion-Run.
You can manually add it back by creating a new String Value called VoodooShield with the vaule C:\Program Files\VoodooShield\VoodooShield.exe in this location.

Bingo!
That registry hack fixed it.