VoodooShield discussion

[shmu26]

To voodooshield.exe or to voodooshieldservice.exe?

voodooshield.exe

 

[shmu26]

A general question/s:
Besides flipping VS to "on" mode, do web apps have any special mitigations/restrictions that apply to them?
And why aren't office apps, like MS Word, considered web apps, seeing as PDF readers are so considered?

 

[paulderdash]

voodooshield.exe

Tried that but for some reason

it didn't work for me ... switched back to 'automatic, delayed start' method.

A general question/s:
Besides flipping VS to "on" mode, do web apps have any special mitigations/restrictions that apply to them?
And why aren't office apps, like MS Word, considered web apps, seeing as PDF readers are so considered?

+1, would also like to know e.g. whether to add Office apps (LibreOffice).

 

[blueblackwow65]

For some reason Voodoo started on its own on startup this morning ..

 

[shmu26]

For some reason Voodoo started on its own on startup this morning ..

I think the whole thing is a matter of timing. Certain other processes are interfering when they autostart simultaneously. If they finish quick enough, and/or VS gets delayed enough, things will work right.

 

[Brodyaga]

@danb, is it possible for you to get the key to the Pro version, with beta testing, thanks.

 

[Wolfsbane]

A more elegant solution would be to use the inbuilt Windows task scheduler so VoodooShield can run with predefined parameters and more stable switches, while the service can still be used for self protection /integrity checks or telemetry and making sure only allowed modules are loaded, imo. Redstone update should be interesting. I'm wondering if WD EMET will play nice with VS

 

[boredog]

Had the startup issue right after install. It then stopped for a while but came back today.
UAC MAX
ADMIN
Appguard, Winpatrol RAR, Tinywall

 

[Antarctica]

Had the startup issue right after install. It then stopped for a while but came back today.
UAC MAX
ADMIN
Appguard, Winpatrol RAR, Tinywall

I had the same problem today. Going back to V3.59 until it is solved.

 

[boredog]

I had the same problem today. Going back to V3.59 until it is solved.

It is not a Biggy for me. I just open task manager and start it.

 

[VecchioScarpone]

Dan

All worked fine yesterday. This morning at startup VS requested for registration.


I registered then after making sure all worked fine I turned the computer off.
When restarted VS did not startup, I had to do that manually. Note that VS is set to logon at startup.
Turned the machine off and restarted once more and all is fine, for now...

VS Smart Mode
UAC default level
WD
HTMP set to run a scan at startup.
MBAE

 

[Mr.Gump]

4.0B isnt starting with my PC but I am not too worried about it, i just start it up manually. Everything else working great! Windows 10 64bit

 

[plat1098]

VS is in the systray first but doesn't show up in Startup programs/task manager--just an observation. Still get a "Program Manager is still in use" message at shutdown but it just proceeds and there are no errors or warnings in event viewer. Machine has been running for a few hours with 4.0 beta and no CPU issues, no registration boxes after startup either. Nice.

 

[_CyberGhosT_]

This start up and registration issue seems strange in that after it asks for you to re-register, after you enter your info
have you noticed that it resets the whitelist. It cant keep the startup info, it cant retain the license info, or the Whitelist
it created. sounds "to me" like code changes or write permissions could be part of this.
Either way I put VoodooShield to sleep for now and will update when Dan posts beta updates.

 

[VecchioScarpone]

This start up and registration issue seems strange in that after it asks for you to re-register, after you enter your info
have you noticed that it resets the whitelist. It cant keep the startup info, it cant retain the license info, or the Whitelist
it created. sounds "to me" like code changes or write permissions could be part of this.
Either way I put VoodooShield to sleep for now and will update when Dan posts beta updates.

Same experience. Strange though that it keep changes to WebbApps

 

[DotNet]

I am amazed at how much better this is versus 3.59. Dan you are truly gifted! This is the first beta of any security software where users don't hesitate to install it. A few bugs put you 4 or 5 releases ahead of other so called stable builds, (malwarebytes), (bitdefender), etc. After restart registration is working after the 2nd try. 1st time it acts like it worked and even takes an advanced snapshot, but it still show free version. Completely exit the application & restart it. Now enter registration again. Registered! Tested several times, same results. Disabled UAC, No active antivirus running, Windows 10 x64 LTSB.

 

[danb]

I am amazed at how much better this is versus 3.59. Dan you are truly gifted! This is the first beta of any security software where users don't hesitate to install it. A few bugs put you 4 or 5 releases ahead of other so called stable builds, (malwarebytes), (bitdefender), etc. After restart registration is working after the 2nd try. 1st time it acts like it worked and even takes an advanced snapshot, but it still show free version. Completely exit the application & restart it. Now enter registration again. Registered! Tested several times, same results. Disabled UAC, No active antivirus running, Windows 10 x64 LTSB.

Thank you, I appreciate that very much... even though I do not deserve such a compliment .


Here is the 4.01 beta, hopefully the registration issue is fixed… if not, I will see if Alex can take a look at it asap.

The token issue (VoodooShield starting on startup with the service) may or may not be fixed, but if it is not, I added some logging that will provide a specific error code that will help us narrow it down.

I was not able to duplicate the high CPU utilization that is a result of the scan child processes feature… so if someone can send me a link to a file that causes this issue, please do. It will be a very, very easy fix once I can reproduce the error… high CPU utilization errors are always easy to fix once you can reproduce them.

Other than that, there are around 10 or so other bug fixes included in this version.

There were a few bugs in the new rules feature, and the custom folders feature, but I believe they are resolved now. If either of these features do not behave as expected, please let me know. If you can provide a way for me to produce the unexpected behavior, that will be even better.

Everything seems to be going extremely well, and are getting very, very close to a stable VS 4.0… I would not be surprised if we can wrap this up in less than a week. Thank you guys for your help, I will catch up asap!

You should be able to install over the top of the old versions of VS… but if you run into trouble, please uninstall the old version, reboot, and reinstall (and please let me know if you had an issue with installing over the top).

www.voodooshield.com/Download/beta4/InstallVoodooShield401beta.exe

 

[codswollip]

4.01b... No autostart (reboot login)

From Event Viewer:
Service cannot be started. System.InvalidCastException: Conversion from string "StartProcessAsCurrentUser: GetSe" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
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)

 

[faircot]

4.01b
Dan, Installed fine over the top of previous beta, rebooted and VS had reverted to free edition.

Registration issue not resolved, I'm afraid.

 

[codswollip]

Registration issue not resolved, I'm afraid.

FWIW, my registration continued w/o issue (/knocks wood).