VoodooShield 5.50

Forums VoodooShield Support Forum VoodooShield Releases VoodooShield 5.50

  • Post
    Dan
    Keymaster
    US
    Hey guys, we are getting very close!  Here is the latest version… there are just a few things that I need to finish up, like the new artwork on the How It Works form, and I also need to finish the Windows Firewall feature.  It is all ready to go, but I don’t want to actually automatically add rules until we are sure all of the bugs are fixed, because believe me, as many changes as there were in this version, there are most likely be a few small bugs.

    There are way too many changes under the hood and with the WLC implementation for me to describe, that it is probably best for you guys to just try it and see.  A few small things though, I removed the Advanced Snapshot feature for a lot of reasons.  First, we really need to get back to our roots and focus on VS’s proprietary tiny, customized whitelist… that really is what VS is all about.  The whole goal is to offer the smallest attack surface in the industry.  Also, there is no reason to analyze thousands of files with WLC.

    Also, brand new whitelists will be automatically generated and scanned with WLC.  Again, the whole goal is to keep the whitelist as small as possible.  Then again, with WLC and the other features we have implemented the last year or so, unwanted blocks should be pretty much non-existent.

    I hope to catch up on the posts here soon… it is great to see you “old guys” 😉.

    And yes, I would uninstall the standalone version of WLC now 😉.

    Thank you guys, have a great weekend!

     

    VS 5.50 beta
    https://voodooshield.com/Download/InstallVoodooShield550beta.exe
    SHA-256: bd85bc201c7f70c9677edb89cad73a85d0e3ed55e1f92507e9f4178dee53bdd0

    VS 5.51 beta
    https://voodooshield.com/Download/InstallVoodooShield551beta.exe
    SHA-256: e05cb8ac0a89edaade7c3543c4717955c451efb2f953be3874f2bbad8e1cecdb

    VS 5.52 beta
    https://voodooshield.com/Download/InstallVoodooShield552beta.exe
    SHA-256: dba4fd21024a2bc2686f5ed4e70f1242b5fd24bf66c5ad0987b4cd4ed56abc48

    VS 5.53e beta
    https://voodooshield.com/Download/InstallVoodooShield553ebeta.exe
    SHA-256: 73770b6a1e9d9de5d506e0814fb8c2658b5d9f04c1d6fb572a62bcd046b9d410

    VS 5.54F beta
    https://voodooshield.com/Download/InstallVoodooShield554Fbeta.exe
    SHA-256: 68441b9c1cdb871cd0181ead2b6fecd441582fccb6bbd4b3d144e72ec746186d

    VS 5.54G beta
    https://voodooshield.com/Download/InstallVoodooShield554Gbeta.exe
    SHA-256: 60efd004a377393d69583abbfefdc7f6c7deef28893df832e9dedbf50e6baba7

    VS 5.54H beta
    https://voodooshield.com/Download/InstallVoodooShield554Hbeta.exe
    SHA-256: 9391f87595681e03f37b23f20692b049d303f6e6a11cc2d36291daac6d1d43d5

    VS 5.54I beta
    https://voodooshield.com/Download/InstallVoodooShield554Ibeta.exe
    SHA-256: 03c1f22ba2e9d73b96cf6133b4bf9da711bddd73063b7d2ab4859e304ad2c615

    VS 5.54K beta
    https://voodooshield.com/Download/InstallVoodooShield554KBeta.exe
    SHA-256: b8c87fae09ebc75ea96c65fa6537643b6e2dad43f41df206ed127edc7a976051

    VS 5.55
    https://voodooshield.com/Download/InstallVoodooShield.exe
    SHA-256: 40e42b086f7cc587fd5c31d92fcae22272838dbe285a0f187bb5bd26d417ac2a

    VS 5.56 beta
    https://voodooshield.com/Download/InstallVoodooShield556beta.exe
    SHA-256: 7aba5acd48efb2c9343fe5b3c3c43314f3855f623e6969d7d6a617a8766c16c0

    VS 5.58 beta
    https://voodooshield.com/Download/InstallVoodooShield558beta.exe
    SHA-256: 38c96247d45a094cf071be91a747ec38e20683707cbd84ccbb962e28a457dd48

    VS 5.59c
    https://voodooshield.com/Download/InstallVoodooShield559c.exe
    SHA-256: a2ddd543bbf1dc5226c4e9e224672e2021e8325e3461c11e3c3871b744df0e13

    VS 5.60 Public Release
    https://voodooshield.com/Download/InstallVoodooShield.exe
    SHA-256: a08d9ae8c78c9ce9c51bee96ed7ab369eab668e053d80af7f01f86d76792d3cd

     

    • This topic was modified 1 month, 4 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 2 weeks ago by Dan.
    • This topic was modified 1 month, 1 week ago by Dan.
    • This topic was modified 1 month, 1 week ago by Dan.
    • This topic was modified 1 month, 1 week ago by Dan.
    • This topic was modified 1 month, 1 week ago by Dan.
    • This topic was modified 1 month, 1 week ago by Dan.
    • This topic was modified 1 month ago by Triple Helix.
    • This topic was modified 1 month ago by Dan.
    • This topic was modified 3 weeks, 4 days ago by Dan.
    • This topic was modified 3 weeks, 3 days ago by Dan.
    • This topic was modified 3 weeks, 1 day ago by Dan.
    • This topic was modified 3 weeks, 1 day ago by Dan.
    • This topic was modified 3 weeks ago by Dan.
    • This topic was modified 2 weeks, 1 day ago by Dan.
    • This topic was modified 1 week, 5 days ago by Dan.
    • This topic was modified 1 week, 5 days ago by Dan.
    • This topic was modified 1 week, 4 days ago by Dan.
    6
    0
Viewing 15 replies - 16 through 30 (of 735 total)
  • Replies
    Dan
    Keymaster
    US
    Hey guys, please keep in mind that it is a work in progress.  Once it is finished, it will all make sense.  I just wanted you guys to see what I had so far, so that you could make suggestions and help me with some of the decisions.  That, and also, since SOOOOOO many changes were made under the hood in this version, I wanted you guys to try it so we can see what bugs remain.

    BTW, the internet connection on the server was down for the last hour or so, so you might have had some issues because of this.  Thank you guys!

    0
    0
    Krusty
    Moderator
    AU
    I used 5.50 yesterday and it was running great but I started this machine this morning and left it idle for half an hour or more and WC was still scanning when I resturned.  I disabled WC, right clicked the Tray icon and exited VS, then opened REVO Uninstaller to uninstall VS but only to receive a message that VS was still running.  I could not end VS process in Task Manager, so I restarted the machine.  This time I could exit VS and kill the VS process.  I finally managed to uninstall VS.

    I see what you’re doing Dan, and I think it will be OK when you get the bugs sorted.  For now I’ll wait for the next version or so.

    Cheers!

    _______________________________________
    • Windows 10 x64 1909
    • Linux Mint Mate 19.3
    0
    0
    HempOil
    Participant
    CA
    Hi Dan,

    I upgraded and now every time I enable or disable WC (in VS) I get an unhandled exception. I can’t seem to find a way to attach a screen cap of it, but I can copy and paste the gory details:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

    Server stack trace:
    at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
    at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at VoodooShield.VoodooShieldService.IVoodooShield.UpdateSettings(String SettingString)
    at VoodooShield.Settings.﷐﷘(Object ﷐, EventArgs ﷑)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.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.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    • This reply was modified 1 month, 4 weeks ago by HempOil.
    • This reply was modified 1 month, 3 weeks ago by Dan.
    Windows 10 Home 64-bit, version 1909, build 18363.592 (hyper-threading disabled). Comodo Internet Security Premium 12.0.0.6882. HMP.A 3.8.0 Build 861 beta & HMP 3.8.16 b310 (64-bit). VoodooShield 5.60 Public Release. Google Chrome 79.0.3945.130 (Official Build) (64-bit) run in Comodo sandbox.
    0
    0
    Ssherjj
    Participant
    US
    Thanks Dan for the updated VS Beta.

    I am not having any issues so far that I am aware of. I uninstalled WhiteCloud since it is integrated with VS. I did reinstall WC the other day to see if there was a difference between the integration of VS and running WC separate. There were a few games that I needed to Whitelist in WC.  But it gets to confusing for me running the two separately so I uninstalled WC again. …relying on VS is better..

    All is good! No errors! I haven’t had any performance issues so far. 🙂

    Webroot® SecureAnywhere® Complete Beta Tester, VoodooShield Beta v5.5.4C- Glasswire Firewall Elite - Windows 10 Pro Workstation v1909, Alienware 17R4 Webroot SAC Beta on Mac El Capitan, 10.11.6 -Microsoft® Windows Insider MVP - Windows Security
    1
    0
    VecchioScarpone
    Participant
    AU
    I uninstalled WhiteCloudC after its integration with VS. The only thing I noticed so far is, the average memory reading went from 20% now to 28%.

    Would it be considered high?

     

    ______________________________________________________

    "Today is yesterday's future"

    0
    0
    Mr.GumP
    Participant
    none
    5.50 working great, so fetch!
    • This reply was modified 1 month, 4 weeks ago by Mr.GumP.
    0
    0
    Dan
    Keymaster
    US
    Thank you guys… the main issue was the internet connection on the server was down, that really messed a lot of stuff up.  But it is giving me a chance to debug the code for when it goes down later.  Anyway, most of the bugs that you guys have found are fixed (I think), and in a day or two I will be able to release a much more refined version.  This happens every time I make significant changes to VS… and actually, if the connection had not gone down, it would have been pretty smooth.  Which is why it seemed to work really well for some people, then all of a sudden it did not… well, its because the connection went down ;).  Thank you guys, talk to you soon!
    0
    0
    Gandalf
    Participant
    NL
    Still the WLC scan of VS is not very fast, but now all files are safe. Seems that the (server) issues are indeed resolved.
    0
    0
    Triple Helix
    Moderator
    CA
    Thanks Danno! Running well here!
    • This reply was modified 1 month, 4 weeks ago by Triple Helix.
    Microsoft® Windows Insider MVP - Windows Security - VoodooShield Pro - Webroot SecureAnywhere Complete - Glasswire Elite
    0
    0
    ProTruckDriver
    Participant
    US
    Thanks Dan. Up and running. No problems so far.

    Win 10 Pro ~ VoodooShield ~ Malwarebytes Premium ~ GlassWire.

    macOS Catalina 10.15.2 ~ Malwarebytes Premium ~ Malwarebytes Browser Guard & Adguard on Firefox & Chrome.

    0
    0
    Jasper The Rasper
    Participant
    none
    Thank you Dan. No problems here at all, it is all running just as it should be.
    Webroot® SecureAnywhere® Complete Beta Tester v9.0.27.55 - VoodooShield v5.60 Beta - Glasswire Firewall Elite  - Microsoft Windows Insider MVP
    0
    0
    Jasper The Rasper
    Participant
    none
    Correction to my last post. The Whitelist element of this VS build is continuously scanning now and has been for over an hour now.

     

    I have just realised that even after a restart, without browser or Outlook running, Voodooshield is still running whereas it would always turn off.

    Webroot® SecureAnywhere® Complete Beta Tester v9.0.27.55 - VoodooShield v5.60 Beta - Glasswire Firewall Elite  - Microsoft Windows Insider MVP
    0
    0
    Gandalf
    Participant
    NL
    Dan, I’m seeing dimhost.exe four times being Auto Blocked in the user log. A false positive?
    0
    0
    Mr.GumP
    Participant
    none
    Whitelist Cloud found 13 items. I am pretty sure they are all safe. Is there any disadvantage however, to leaving them all on the not safe list? As it pertains to performance or any possible complications…

     

    Thanks!

    0
    0
    gorblimey
    Participant
    none
    @Gandalf – Do the dimhost.exe entries all have the same qualified path?  And on a similar theme, are they all called in the same way?  This is important, as VS doesn’t just rely on the exe name.

     

    @Mr.GumP – How long have you had those 13 items?  If they haven’t been pinged for antisocial behaviour before, they’re probably safe.

    However, I strenuously suggest the use of a reputable firewall set to default deny all outbound, so you can make sure your softs are only talking to permitted people.  I use and recommend Windows Firewall, and Windows Firewall Control by https://www.binisoft.org/wfc which will automatically rework Microsoft’s Stupidity Settings plus it’s FREE from MalwareBytes.

    Windows Firewall is shipped as part of Windows…

    _________________________________

    Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall"]
    0
    0
Viewing 15 replies - 16 through 30 (of 735 total)
  • You must be logged in to reply to this topic.