VoodooShield/Cyberlock

Yes, correct.

 

The issue was I clicked on the balloon and it opened the Alert Window I clicked Allow and nothing happened the only way to close the Alert Window was to click on the red X that I asked you to put in.

I'm just reporting that the Alert Window is still freezing if it wasn't for the Red X then we would of have to open Task Manager and Kill the processes.

Daniel

 

The alert windows started freezing for me again last night, and VS started ignoring the whitelist again. VS ignored the whitelist for the same application 3 times in a roll, and each time I would allow it using the ballon from the tray icon. I was using Shadow Defender, and every single time I've used VS, and SD together i've had problems. I've come to the conclusion that there has to be a conflict with between VS, and SD. Shadow Defender should be compatible with anything, but VS sure does not like it.

 

Cool, thank you for letting me know. Is this only for the firefox update, or for something else?

 

So this only happens when you use SD? I can download SD and see if I can fix the issue. Thank you!

 

I always have the problem of VS ignoring the whitelist reoccur when using VS, and SD together. Then when I try to answer the alert window it freezes. It does not freeze as bad now though because i'm able to use the red X in the upper right corner to kill the alert Window. Before I had to kill VS from Windows process monitor.

 

I just checked my whitelist, and applications I added to the whitelist last night while in Shadow Mode never was added. I tried adding Brosix Messenger 5 times to the whitelist. VS was unable to add it. I went ahead, and deleted my whitelist again by using the remove computer button in the cloud. I rolled back to my test image, and made some updates to that image so I will create a new baseline test image. For years i've operated in Shadow Mode about 95 percent of the time. The only time I do not is when installing new software, or installing updates. Lately I have not been using Shadow Mode very much only because I've had no luck getting VS to work with SD.

 

Yes Process Explorer -http://technet.microsoft.com/en-ca/sysinternals/bb896653.aspx as it runs in the user space c:\users\daniel\appdata\local\temp\procexp64.exe and I put it in Program Files and send a short cut to Desktop and transfer to the Task Bar. I click on the balloon and Alert Window opens and I click allow and it doesn't do anything then I have to click the Red X to close and then put into Training Mode to use it.

Daniel

 

I will try SD asap. I can put it in shadow mode while I am debugging VS and see if it gives me an error. Does SD allow changes to files in the appdata folder while in shadow mode? We can also email SD to see if they have any thoughts. Thanks again!

 

That is really odd about Process Explorer. I just downloaded it to my desktop, extracted the files and ran it, but it did not use the appdata folder at all. I tried it on Windows 7 and 8 and it worked for both. Do you have any idea how I can make it use the appdata directory? Thank you!

 

The problems usually start after rebooting in Shadow Mode, or rebooting after exiting Shadow Mode. Add some applications to the whitelist while in Shadow Mode. Then reboot while in Shadow Mode. Then see if VS continues to allow those applications to run after rebooting once or twice.

Also try adding some applications to the whitelist while in Shadow Mode. Then choose exit Shadow Mode, and reboot. See if VS continues to allow those applications to run after exiting Shadow Mode.

VS usually fails to add the application to the whitelist, or VS ignores the whitelist entry for the application. The applications that cause problems are using installed in the userspace, or on an external drive.

 

Have you tried extracting it to a folder you have created in the Program Files directory, and then creating a shortcut to the desktop & tray taskbar like he did?

 

I will play around with it tomorrow and see, I am curious now. Maybe the issue is that VS is not uploading the whitelist to the server, unless the user right clicks on VS and chooses Exit before rebooting the computer. I am just thinking that VS is not uploaded the whitelist to the server unless the user chooses Exit on VS. Either way, I will check it out soon. Thank you!

 

Actually I just tried that after you mentioned it, and it did recreate the problem that TH was having. So this will help big time to troubleshoot the issue. Thank you Cutting_Edgetech and TH!

Edit: I see what is going on. VS will not let the user click the Allow button because it is trying to whitelist something in the appdata directory. Whenever there is an executable file in the appdata directory, the user will need to put VS in Training Mode to learn the new process (and I will make this work in the next version). Then again, this will not work if the sub folder is randomly named like it is for Disk Cleanup. I will have to figure out the best way to handle this, it should not be that difficult.

 

I just released 1.26.5 to the public. I will start on the other fixes and features tomorrow.

http://voodooshield.com/Download/versions/Install VoodooShield.1.26.exe

 

I've been running VS mainly "Always On" since, if I understand correctly, it gives the program less work to do. I put VS in "Training" when loading software. Are there other actions where VS should be taken out of "Always On"?

Thanks, loading up 1.26.5.

 

I always turn off VS (Training, Disable Protection, or exit) when I am doing any kind of system maintenance, like Windows Updates (not that I always do Windows Updates) or uninstalling software. Also, VS should deactivate if the system is idle so it can do any kind of scheduled maintenance, but you can disable this if you want.

When I install software, I just do what you do and put it in training. But yeah, how you are using VS sound great. And Always ON really does a lot less than Smart Mode, since all it is doing is killing things that are not on the whitelist. Thank you!

 

What changes were made in this build?

 

Here are the change logs for the last 3 versions. I think I forgot to post the previous 2. A lot of times it is hard to describe the refinements, but there are always a lot of small refinements in every new version.


VoodooShield 1.24 ChangeLog

Recoded the logic for each of the four modes



VoodooShield 1.25 ChangeLog

Added USB label on desktop gadget

Optimized the engine

Added Default Settings button to Settings



VoodooShield 1.26 ChangeLog

Fixed errors when an internet connection is not available

Fixed the Allow button in the Prompt - Bug in appdata folder whitelisting will be fixed in next version

VS will now go into the previous mode after being prompted to activate in Disable Protection or Training Mode

Optimized the Scan with VirusTotal feature

 

Thank you!

 

Great Thank you!

Daniel

 

I hadn't thought about automatic scheduled maintenance done by the system, thanks for mentioning that. Maybe it would be a good idea to set VS to "Training" before walking away from the computer for any length of time? Or will VS always know to deactivate itself? Should any settings be modified to help VS deactivate itself smoothly for scheduled maintenance when it's being run "Always On"?

 

Working good here, no problems noted. VS alerted me new version was available.

 

You can just make sure that the Automatically Deactivate option is checked in the Settings / Advanced. You really do not need to switch to training, VS should deactivate itself after 10 minutes, or whatever you have it set to.

 

Good deal, thank you for letting me know!