VoodooShield ?

Discussion in 'other anti-malware software' started by CloneRanger, Dec 7, 2011.

  1. Cutting_Edgetech

    Cutting_Edgetech Registered Member

    Joined:
    Mar 30, 2006
    Posts:
    5,601
    Location:
    USA
    Vlad, congrats on bringing a little angel into the World!

    I just tested the latest VS beta for two weeks, and I did not experience any issues. VS is working better than ever on my Windows 7X64 Ultimate setup.
     
  2. Brandonn2010

    Brandonn2010 Registered Member

    Joined:
    Jan 10, 2011
    Posts:
    1,850
    Hey everyone, not sure if this is because of VoodooShield or something else, but I think it may be VoodooShield:

    When I try to launch Chrome, sometimes it will launch normally, but many others it will either do nothing and I have to click its icon again to get it to launch, or it will fail and say "Windows does not have permission to access..." and I will have to click its icon again to get it to launch as well.
     
  3. Gillor

    Gillor Registered Member

    Joined:
    Jul 12, 2013
    Posts:
    83
    Location:
    UK
    I am having the same problem - well hardly a problem, more a minor inconvenience.

    Launched Chrome ten times in succession with VS set to Scan and Allow and it failed to launch first time on five occasions. With VS disabled Chrome launched correctly every time.
     
  4. VladimirM

    VladimirM Developer

    Joined:
    Sep 16, 2015
    Posts:
    153
    Location:
    Jerusalem, Israel
    Hello,
    Please send DeveloperLog.log from C:\Program Data\VoodooShield to email vlad@voodooshield.com so I could see what is blocked. The reason might be that sometimes chrome starts some subprocess that accidentally blocked by VS, but I need to see the log.

    Thanks in advance,
    Vladimir
     
  5. VladimirM

    VladimirM Developer

    Joined:
    Sep 16, 2015
    Posts:
    153
    Location:
    Jerusalem, Israel
    Due to technical reasons, the planned release is delayer for a day or two.

    Thanks
     
  6. ProTruckDriver

    ProTruckDriver Registered Member

    Joined:
    Sep 18, 2008
    Posts:
    1,221
    Location:
    Stand Up For Your Country
    Thank you Vlad for the heads up on the delay of the new release. :)
     
  7. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Thanks Vlad.

    I'll hurry up and wait. ;)
     
  8. ProTruckDriver

    ProTruckDriver Registered Member

    Joined:
    Sep 18, 2008
    Posts:
    1,221
    Location:
    Stand Up For Your Country
    Now that sounds like when I was in the Navy! :argh:
     
  9. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Vlad,

    I could be mistaken but I reinstalled VS 3.07 beta yesterday and it looks like dismhost.exe ran this morning on one machine and was allowed and automatically white-listed. o_O

    Thanks,
    Dave
     
  10. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Vlad, I've sent you an email with my log as well.

    Cheers!
     
  11. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    I've even had this popup a couple of times when trying to open Chrome from the Task Bar icon now.
    Chrome.PNG
     
  12. Gillor

    Gillor Registered Member

    Joined:
    Jul 12, 2013
    Posts:
    83
    Location:
    UK
    Any connection between this and my post #8397?
     
  13. Gillor

    Gillor Registered Member

    Joined:
    Jul 12, 2013
    Posts:
    83
    Location:
    UK
    Developer Log Sent to your email address.
     
  14. djg05

    djg05 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    1,563
    Thanks Dan

    Firstly congrats to Vlad on his newborn

    I have tried you suggestion and it does not work.

    On reloading VS after deleting the VS Prog data nothing is selected in the "Choose Mode" settings. Under this condition it works, but select training and it no longer works. Of course under this I am no longer registered and re-registering will not work .Net comes up with the error in Code below.

    At this stage VS has not created anything in PD. Looking in the old file there was nothing listed as being blocked.

    The scanner is a USB driven, make Canon and using their supplied s/w.

    Hope this make some sense to you.

    David



    Code:
    ************ Exception Text **************
    System.TypeInitializationException: The type initializer for 'VoodooShield.VSSettings' threw an exception. ---> System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\ProgramData\VoodooShield\settings.dat'.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.File.Delete(String path)
       at VoodooShield.Storage.﷐(String ﷐, String ﷑)
       at VoodooShield.VSSettings..cctor()
       --- End of inner exception stack trace ---
       at VoodooShield.VSSettings.get_StringItem(String propertyName)
       at VoodooShield.Settings.﷒(Object ﷐, EventArgs ﷑)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    
    
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    ----------------------------------------
    VoodooShield
        Assembly Version: 3.0.1.0
        Win32 Version: 3.0.1.00
        CodeBase: file:///G:/Program%20Files/VoodooShield/VoodooShield.exe
    ----------------------------------------
    Microsoft.VisualBasic
        Assembly Version: 8.0.0.0
        Win32 Version: 8.0.50727.8007 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8015 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8016 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Runtime.Remoting
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8012 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    VoodooShield.Common
        Assembly Version: 3.0.1.0
        Win32 Version: 3.0.1.00
        CodeBase: file:///G:/Program%20Files/VoodooShield/VoodooShield.Common.DLL
    ----------------------------------------
    System.ServiceModel
        Assembly Version: 3.0.0.0
        Win32 Version: 3.0.4506.8002 (FX35W81RTMGDR.030729-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceModel/3.0.0.0__b77a5c561934e089/System.ServiceModel.dll
    ----------------------------------------
    SMDiagnostics
        Assembly Version: 3.0.0.0
        Win32 Version: 3.0.4506.8002 (FX35W81RTMGDR.030729-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/SMDiagnostics/3.0.0.0__b77a5c561934e089/SMDiagnostics.dll
    ----------------------------------------
    System.Transactions
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
    ----------------------------------------
    System.IdentityModel
        Assembly Version: 3.0.0.0
        Win32 Version: 3.0.4506.8002 (FX35W81RTMGDR.030729-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.IdentityModel/3.0.0.0__b77a5c561934e089/System.IdentityModel.dll
    ----------------------------------------
    System.WorkflowServices
        Assembly Version: 3.5.0.0
        Win32 Version: 3.5.594.7903
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.WorkflowServices/3.5.0.0__31bf3856ad364e35/System.WorkflowServices.dll
    ----------------------------------------
    System.ServiceModel.Web
        Assembly Version: 3.5.0.0
        Win32 Version: 3.5.594.7903
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceModel.Web/3.5.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll
    ----------------------------------------
    System.Runtime.Serialization
        Assembly Version: 3.0.0.0
        Win32 Version: 3.0.4506.8002 (FX35W81RTMGDR.030729-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
    ----------------------------------------
    3cdd2812d1e8454fa5864ba3718387e3
        Assembly Version: 3.0.1.0
        Win32 Version: 3.0.1.00
        CodeBase: file:///G:/Program%20Files/VoodooShield/VoodooShield.exe
    ----------------------------------------
    log4net
        Assembly Version: 1.2.13.0
        Win32 Version: 1.2.13.0
        CodeBase: file:///G:/Program%20Files/VoodooShield/log4net.DLL
    ----------------------------------------
    System.ServiceProcess
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
    ----------------------------------------
    System.Data.SQLite
        Assembly Version: 1.0.94.0
        Win32 Version: 1.0.94.0
        CodeBase: file:///G:/Program%20Files/VoodooShield/System.Data.SQLite.DLL
    ----------------------------------------
    System.Data
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
    ----------------------------------------
    
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    
    For example:
    
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    
    
     
  15. VladimirM

    VladimirM Developer

    Joined:
    Sep 16, 2015
    Posts:
    153
    Location:
    Jerusalem, Israel
    Yes
    I think it is connected. I see that software_reporter_tool.exe, that is started by chrome is blocked, because a scanning finds 1 threat. Probably this is a reason.

    I'll check and will find out what may fix it

    Thanks for the log and your help!
     
  16. VladimirM

    VladimirM Developer

    Joined:
    Sep 16, 2015
    Posts:
    153
    Location:
    Jerusalem, Israel
    Thanks for the logs.
    I think I've found what was the problem and the fix is planned to the next release.

    Thanks
     
  17. VladimirM

    VladimirM Developer

    Joined:
    Sep 16, 2015
    Posts:
    153
    Location:
    Jerusalem, Israel
    VoodooShield 3.08 Beta Release
    You can download it from https://voodooshield.com/Download/beta3/InstallVoodooShield.exe

    System requirements:
    • Windows Vista sp1 and above (XP is not supported!)
    • .NET 2.0/3.5 and above
    What's new in VoodooShield 3.08 Beta:

    This release contains the fixes for the following bugs
    • BSOD caused by VS driver under some circumstances.
    • dismhost.exe bug fix
    • Fix non-opening chrome (frequent bug)
    • Better exception handling (to make VS less crashing)
    • Fix installer to not install on XP

    Known issues

    • Sometimes gray user prompt is shown - unable to reproduce, so still trying to find what could be a problem
    Have a good day,
    Vladimir
     
  18. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Awesome Vlad! Installing right now.

    Thanks,
    Dave
     
  19. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Yay! Both of these bugs do indeed appear to be fixed. Guys, this could be the best version of VS yet.

    Great work Vladimir and Dan! :thumb:

    Thanks.
     
  20. Cutting_Edgetech

    Cutting_Edgetech Registered Member

    Joined:
    Mar 30, 2006
    Posts:
    5,601
    Location:
    USA
    Thanks for the new release Vlad! I can't wait to try it!
     
  21. Baldrick

    Baldrick Registered Member

    Joined:
    May 11, 2002
    Posts:
    2,555
    Location:
    South Wales, UK
    Nice one, Vlad

    All installed here (using the built in updater which offered the update) and running very nicely. :thumb: :)

    Regards, Baldrick
     
  22. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Hey Dan,

    I would even go as far as to suggest offering this build to the public as an official release, unless you know something I don't. ;)

    This is one rock-solid, stable release on my machines. Once again, great work guys! :cool:
     
  23. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,236
    Location:
    Under a bushel ...
    Known issues
    • Sometimes gray user prompt is shown - unable to reproduce, so still trying to find what could be a problem
    This is quite a frequent problem (Win 7 Pro 64), so I would suggest Vlad tracks this one down first. :)
     
  24. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    8,354
    Location:
    Among the gum trees
    Ah! Fair enough. ;)
     
  25. Tyrizian

    Tyrizian Registered Member

    Joined:
    Apr 26, 2012
    Posts:
    2,823
    This software is just getting better and better.

    Thank you for the continued development, it is truly an amazing product.

    Keep up the amazing work, guys! (@VoodooShield and @VladimirM).
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.