VoodooShield/Cyberlock

Here is 3.55beta... Please do not install on any mission critical machines for now. I do not think we will have any issues, but you just simply never know... there is a very small chance that you might have some trouble logging in or whatever.

To make a long story short... if the GUI disconnects properly from the service, then there is no problem. But for example, if the computer is shutting down and the GUI does not have the chance to send the service a message to tell it is shutting down, then the service thinks that it needs to lock down the computer. To resolve this issue, I had to add exceptions to the service, based on the process path and the parent process path... so that all critical processes are always allowed, no matter what happens. But we have to be careful to not always allow certain critical items that can be exploited, which is why we check the parent process as well.

To make a long story short, everything should be working correctly, but if anything goes wrong, please send me your DeveloperServiceLog.log.

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

Also, while debugging the new self-protection feature with Vista, I noticed that Vista had a few issues unrelated to the new features, and it is not working properly. So at least for the time being, Vista is not supported, but all other OS's from 7-10 are.

Thank you guys... I hope to respond to the PM's, posts and emails very soon, have a great weekend!

 

Thanks, Dan...downloaded and installed (over the top) and so far working great.

Have lost track of what this is looking to resolve so please let me know (if you have the time) of anything specifically that needs checking for otherwise I will just give it my runof the mill 'ashing'...

 

Thanks Dan! I'm going to do a clean reinstall of this new version!

 

I just rebooted, after upgrading from v3.53 to 3.55 beta a short time ago. It was an over-the-top install. All is fine it seems. This was after I had the usual monthly round of Windows Updates, yesterday.

 

stable here.

 

"Here is 3.55beta... Please do not install on any mission critical machines for now. I do not think we will have any issues, but you just simply never know... there is a very small chance that you might have some trouble logging in or whatever."

 

"Here is 3.55beta... Please do not install on any mission critical machines for now. I do not think we will have any issues, but you just simply never know... there is a very small chance that you might have some trouble logging in or whatever."


I would not worry about for those that that have image backups

 

I walk the tightrope at the moment. My Macrium Reflect has gone wackydoodle on me, for the moment.

 

Now I am thinking you must be walking that tight rope Neked

 

Nah!

 

Hi
Installed 3.55beta over 3.53 and all seems to be working ok. I am running Windows 7 32bit OS. The 'logging off' at shutdown seems a little longer than with 3.53.
Question regarding the self protection ....
With 3.55b I can still terminate the two VS processes via the Task Manager without any problem or warning boxes about locking the system appearing. Is this normal?

Thanks Dan for all your hard work.

 

Fantastic, but mission critical stuff here. So, still have 3.53 for the time being. Was there a correlation between VS 3.54 and really slow finish of installing Windows cumulative update, the one needing the reboot? Would really like to know. Thanks!

 

Just updated to 3.55. Installed on top 3.53.
Start up, rebooting and WD disabling issues seems gone.
Fingers crossed...

 

Dan,

I installed 3.55 beta, restarted and found this in the log:

Code:

[03-18-2017 12:09:52] [ERROR] - VoodooShield has entered self-protection mode. | C:\Windows\System32\svchost.exe |  | True | False
[03-18-2017 12:09:52] [ERROR] - Vital INFO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | C:\Windows\System32\svchost.exe |  | True | False

The rest of the log has been sent.

Thanks.

 

Hi Dan,

I've installed the latest beta, I know there's no need to tell you this unless I'm having problems...If I do I'll send you the DeveloperServiceLog.log. as per your request and not waste space here telling you it works

 

Dan

Reverted to 3.53.
Issues: Suddenly could not access explorer, taskbar apps, one instance of WD Killed on reboot.
Dev log and screenshot sent.

Thanks.

 

Turns out this is a false positive and not really an error.

 

This might be a better version...sorry the self-protection feature is being such a pain, but I think we are close!

http://www.voodooshield.com/Download/beta3/InstallVoodooShield355beta2.exe

I am going to bed, but talk to you guys soon!

 

Thanks Dan

 

Dan, Installed this morning on my Laptop Win10 64-bits. So far no problem at all.

 

Windows 10 x64.
So far, so good...

 

All installed over the top...and so far no discernable issues to report, Dan!

 

Latest version is running fine, on Windows 10 Pro x64.

 

likewise 3.55beta2 on my win7x64