VoodooShield/Cyberlock

Hi Dan

Am just installing and hopefully I will be able to confirm that the DISM issue is resolved as mentioned by Antarctica.

Will of course feedback if I spot anything.

Regards, Baldrick

 

I had the occasional DISM issue after installing Windows 10 AU, will report back if it continues with this new version.

 

fixed , thanks.

 

Does VS not work with Secureboot at the moment? I tried installing this latest beta version that Dan posted and it's telling me that the program can't be initialized, and that the driver files are not signed.

 

Dan - FYI I have the cloud option disabled on mine and yet have experienced freeze issues.

 

I really will catch up on the other posts soon, but real quick...

Please try again, it should work now... our digital signature was overwriting the Microsoft one . So it should be fixed now, but I do not have Secureboot (my computer is like 6 years old), so please let me know how it goes, thank you!

 

Dan,

Have you had a chance to look at the files I sent you? The block is now occurring every morning when I wake up from sleep.

 

Latest version here (clean install), VS recommends blocking system safe calls (likely windows store background updates). Already reported sometime ago by other users https://www.wilderssecurity.com/threads/voodooshield.313706/page-469#post-2606210

Cheers,
Fax

Code:

[08-17-2016 18:45:29] [DEBUG] - SRD::HP: ctx=60, proccess: id = 6076, name=rundll32.exe, path=C:\WINDOWS\system32\rundll32.exe, cmd=rundll32.exe AppXDeploymentExtensions.OneCore.dll,ShellRefresh, parent pid=10728, parent process=svchost.exe
[08-17-2016 18:45:29] [INFO ] - Parent Process Empty for: c:\windows\system32\rundll32.exe
[08-17-2016 18:45:31] [INFO ] - Blocked: c:\windows\system32\rundll32.exe

 

Running 332 here with no issues. I have changed from Auto Pilot to Always On mode for a change.

One thing that slightly surprised me was that "Always On" goes Off when the computer is left unattended for a while. Understandable I suppose but seeing the shield say OFF rather belies the label. Is there any need for the shield to read OFF when in this mode as it would probably be more reassuring if it always read ON?

 

@VoodooShield

What's going on with VS? Vlad isn't working it, and the development looks slow. Have you figured out how to ensure the future of VS?

 

Your last beta is working fine for me now with secureboot enabled.

 

@guest

Dan is one man band with part-time help from Vlad (last monday Dan posted that Vlad was working on the freeze issue). Dan managed to push out a new driver which for instance Surfright with a larger team and 30 million dollar investment of Sophos was not able to do.

Dan also runs a local computer support company. He once posted that at least 500 of his clients ran VoodooShield. Assuming that Windows 10 market share also is around 20-25% at his clients, my guess is that he has at least 100-150 clients with possible upgrade problems. So he might be busy with a lot of on-site support caused by W10AU.

Regards Kees

 

Well said Kees. I think Dan does a remarkable job with VS considering his limited resources.

 

I agree, the fact that he is able to do all this with VS (Troubleshooting, Listening, Answering to everyone, and fixing), is beyond impressive for just one man to do.

I tip my hat for what Dan is doing, I honestly don't see how he does it.

Because of his immense drive, passion and work ethic...I respect the man for what he has accomplished.

 

Dan is one of the most personable developers and members here at wilders....I think the future of voodoo shield is assured.

 

yup the future is bright for voodoo shield. It is very user friendly and all the alerts it gives is almost self explanatory. I have installed voodoo shield on at least 15 or so systems and I have never received any SOS calls from my friends. ( I was afraid to give Comodo to them for obvious reasons)

 

I think I finally figured out the root cause of the freeze issue! The driver was reporting to the GUI the following path for certain processes: \SystemRoot\System32\Conhost.exe.

Since it was not an absolute path, VS became confused and did not know what to do, so froze like a deer in headlights . I am not sure why I did not discover this before, but I always found it odd that almost every time in the DeverloperLog, the conhost entry was listed right before the taskmanger entry.

I am still tweaking it a little, but I really think this will fix the freeze issue once and for all. The only good thing came out of this whole freeze fiasco is that it uncovered a few bugs that would probably had not been discovered otherwise, and VS should be rock solid.

Earlier today I worked on the installer so that all of the signatures are just right, and so that VS will ask you if you want to delete the settings and logs during the uninstall (among other things).

Assuming that the freeze issue will be behind us soon, hopefully things will go back to normal, and I will be able to respond a little quicker to everyone… sorry if it seems like I have blown anyone off lately, that was certainly not my intention.

I have also fixed most of the issues from the last couple of months, and will go through my to do list soon and post it so we can work on these last few issues together.

Other than that, we should be good to go… I have a several small usability tweaks that will be easy to implement, and will do that soon.

I hope to post a new version tomorrow and catch up soon!

Thank you for all of your help, we are getting there!!!

 

BTW, I want to create a poll… this is just off the top of my head, but if you guys want to look at it and make suggestions, that would be really cool! Once we are finished with it, we can post it!

When it comes to cyber security, everyone seems to be passing the buck. I really, really, really am tired of receiving notices every month or 2 that my personal information was compromised. The last one was from just the other day, from my health care provider.

The question is… who is most responsible when a company that you deal with is hacked and your personal information or identity is stolen?

A. The company you deal with who was hacked, who did not properly secure their computers.

B. The operating system provider.

C. The company who wrote the application that was exploited (assuming it was an exploit).

D. The antivirus / security provider who actually believes that they can outsmart all of the hackers / malware authors without locking down the systems.

 

BTW, I am not concerned about my privacy at all... I could care less who knows my web search history (or whatever). But what I am concerned about is having my identity stolen, because some company was careless, or or because some company thought that they could outsmart the hackers with a filter. I have heard horror stories about how people spend 5-7 years and tens of thousands of dollars to restore their identity.

 

hello Dan,

Nice to hear that u hv sorted out the freezeeee issue in VS, in my view VS can be a rock solid security product, keep up with ur good works.

In response to ur question --

I think it should be 1. D -- because they promised that with their Security product, they shall take care of everything, but still the security product failed.

 

to answer the question: all of them.

 

@Windows_Security
@Cache
@Tyrizian
@clubhouse1

I'm just asking about the progress about finding financial support for the project, as far as I understood Dan is working on this as well.

 

Excellent news, Dan. FYI, the SBS version continues to run like clockwork here with no freezes or other issues at all since I installed it.

 

The SBS version did crash Wednesday on my laptop, I've sent the logs to Dan. I hope they confirm that it has to do with Comhost.exe and that it will be fixed in the next version.

 

Both 3.31 / 3.32 have been issue free here, no freezes.

Have to agree with guest, and answer your question with "All of them".

Thank you for all your hard work and dedication Dan!