VoodooShield/Cyberlock

Very cool, thank you for letting me know! It really should be fine from here on out... I was concerned about one line of code, but it worked well for me, so I left it in. But it should be fixed either way now .

 

3 Win10 x64 machines are all happy with 3.54.1.

 

3.54beta- Working well here also Dan along with Sandboxie. Windows 7 64 bit.

 

3.54 working fine here Dan.

Is it 3.54 or 3.54.1?

 

I installed the updated version and all is fine

 

It's 3.54. I just added the ".1".

 

InstallVoodooShield354beta.exe is what I installed.

 

Got it, thanks.

 

Yep.

 

All,

I'm sorry for the confusion. My adding the ".1" was an attempt at humour since Dan has been known to release a few versions with the same version number. I never meant to cause confusion.

Cheers.

 

Installed fine on top. No issues to report.

 

One of my other machines is taking an extraordinarily long time to restart. It is sitting saying restarting and I've got the Win10 spinning dots but it isn't restarting. This machine always shuts down very quickly.

 

I eventually had to press the power button to shut that machine down. I'm going back to 3.53 on that machine for the time being.

 

Well, another machine refusing to restart.

VS 3.54, strike three. You're out!

 

I have two PCs with 54.1 betas working OK. 54.0 was OK as well. Running it alongside 360TS (Qihoo cloud only) and Process Lasso V9 beta (free version for now until I receive the Gen2 serial from Jeremy).

 

Hmmm, sorry about that. If you get a chance, or if anyone else if having a similar issue, can you please try this version? I added some logging to tell us what is being blocked or killed, that is interrupting the reboot.

The DeveloperServiceLog.log will say something like... "Krusy, this process is being blocked:"

www.voodooshield.com/Download/beta3/InstallVoodooShield354Krusty.exe

Please email me the DeveloperServiceLog.log (the service one), right after this happens, thank you!

 

Dan, will it be logged if I press the power button to shut down? I mean it hasn't shut down without doing that.

Thanks.

 

It is hard to say for sure... but I think VS is blocking a process because of the new self-protection feature, and that is why it is not shutting down. While implementing the self-protection feature, it happened to me 10-20 times, and each time it logged the items I was interested in... so I think it will log just fine for you. It is probably only one processes that is causing the hang, and once I make an exception for it, it will work great. I really thought I had all the exemptions that I needed to add... in the end, there were only a few. I could just add the entire Windows directory, but I am trying to create the tightest lock possible.

Thank you for your help, I am off to bed .

 

Okey Doke. I'll give it a shot in the 'morrow and will email you the log.

Time for Krusty to have a beer before his bedtime.

Pleasant dreams, Mate.

 

3.54beta so far so good here on my win7x64, during install and after rebooting, no issues seen so far.

 

The previous mode will be toggled 10 second after what? I think it would be good to toggle it 10 seconds after the user login.
But, if a non-whitelisted app wanna start on boot, VS should stay in Always ON and notify the user of this issue

This looks very clever

 

3.54 running nicely here on Win 10 Pro x64.
Nice work Dan

 

Hi @VoodooShield

Would it be possible to change the behaviour of the program if the end user is to manually select"VoodooShield Scan". It appears that if a user right clicks a file and select this option, post VS check, the file would launch. Can this be changed? If I right click scan a file , I just want to see if it is safe to run but I do not actually want to run it

 

It will be toggled after a user login or after launching VS manually. So every time VS is being started you will see the "10 seconds Always On Mode".

@VoodooShield
with the new version VS is now one of the first programs after a user login
That's an improvement, because in previous versions it was always launched much later.