VoodooShield/Cyberlock

No, just right-click on the VS tray icon and select Exit. That ends both running VS processes.

 

Sounds great, thank you for letting me know!

 

You should be able to just install over the top of the old version, after right clicking and choosing exit like pegr recommended (thanks pegr for the help!). You do not have to reboot after installation, even though it prompts you to do so. The reboot is only to disable UAC.

You could uninstall the old version first, but it really should not make a difference either way.

It should run great either way, but if there are any strange issues, you can go to Settings / About and click the Default Settings button.

You do not have to worry about the Whitelist Cloud option. We just included that as an option in case people wanted to disable that feature. Thank you!

 

Hmmm, that is really odd. By login window, do you mean the Registration Windows? VS should not be showing the Registration Window unless it is expired. If this is the case, I will have to fix that. Can you please give me a little more details on the scenario? When you say clean install, does that mean that you uninstalled VS first? If you tell me what procedure you followed, I can see if I can reproduce it on my end.

We need to figure out why your computer is creating new entries on the web interface. I think once you tell me the procedure that you follow, I can look at that as well. We do need to do a little refining on this feature. Thank you!

 

By clean install I mean that I restored an image that has never had VS on it. The icon shows expired but I cannot get to the login window to register.

Then when I register I am assuming that it is creating a new whitelist.

Let me know if you need any more info.

 

Ohhhhh, I see, it all makes sense now. Let me figure out a way to test this, it might be kind of tricky. I should be able to fix the Registration window issue without testing. Basically, I will tell VS to not show the How it Works window if it is expired. As far as the web interface goes... that might be a little tricky, I will have to think about how we can get around that. Thanks again!

 

I just uploaded a version that should fix the issue with the Registration Window, I kept the version 1.26.10 because it was such a small change. This should work for you, if not, please let me know because it is a little hard to test this since I am not actually doing a clean install.

As far as the issue with multiple computer entries in the web interface, I will have to think about how we can get around that.

https://voodooshield.com/freeoffer/Install VoodooShield.1.26.10.exe

 

Thanks Dan

That has fixed the start window but the login window freezes with all the boxes blanked out. Has to be manually shut down and then it will restart normally. This still produced another white list.

 

Sure, thank you for letting me know. I wonder why the Login / Registration Window is freezing. Let me think about what we can do to fix that. I might just have to get the name of your imaging software so I can test it to see what the issues are.

 

I am using AX Time Machine - similar in use to Rollback but a very different architecture - well worth trying. The thread is in Wilders under backup/imaging or here

http://ax64.com/

For the baseline images I use Active@ Image

 

Sounds good, I will try AX , I am curious what is creating this issue. It should be pretty easy to figure out, especially if I start from a clean test system.

 

@ VoodooShield

many thanks

-cheers,
feandur

 

The problem with Windows hanging when using alt ctrl delete to access the task manager was caused by Privatefirewall, and not VS. I no longer have this problem after uninstall Privatefirewall. I'm not sure about the BSOD. I'm assuming Pf probably caused the BSOD, and failed boots as well. I have opened a support ticket with Privacyware. I hope they can fix the issue. I want to continue using Pf. It runs very light on my Laptop unlike other robust firewall HIPS I have tried.

 

I'm sending bug report I prepared to see if there is anything in it that interest you. You can see how nuts VS went after the BSOD by just looking at the screen shots. I can't post the screen shots here without resizing them because they exceed the allowed size so just take a look at them in the archive i'm sending you. The desktop gadget from VS switched to the upper left hand corner of the screen. The dump file, and everything is in there.

 

You're welcome, thank you!

 

Sounds good. I looked at the info you sent me, but could not find anything that really helps to figure out the problem. Please let me know what Privacyware says!

 

I installed AX64 on a new install of Windows 7 and completed a backup. I then installed VS, rebooted, then restored the initial backup. VS did not show expired or create a duplicate entry in the web interface. So the only thing that I can think of is that and expired version of VS was included in your initial AX64 backup. Unfortunately, if this is the case, I seriously doubt there is anything we can do to change this. Let me think about it and see what we might be able to do.

 

This is strange because none of the baseline images I have, have had VS installed. I think you are saying VS thinks that it has been installed and the trial period is over. Bearing in mind that most of my programs are on another partition, does VS leaves traces on other drives?

I will go back to my baseline tomorrow and see if it is leaving remnants in there.

 

I agree, that is odd. VS should not leave any traces on other drives. It does leave things like the users settings and logs in the appdata and programdata folders, in case the user is just uninstalling and reinstalling, but I am going to make that optional in the uninstaller soon. They are extremely small and do not effect anything, and a lot of software does this, and it has always driven me crazy that developers do this, so I need to make it optional asap.

If you have a spare HDD, you could always test the way I did. Just install a clean version of Windows on the spare drive. Then install AX64 and do a backup. Then install and register VS, and then do a restore and see what happens. BTW, am I following the same basic procedure that you are, or should I change something?

 

It appears to be a problem where Privatefirewall does not know how to handle a driver called risdsnpe.sys that I believe came installed on this Sony Laptop. I started a support ticket, but I have not heard back from Privacyware yet.

 

So does everyone think that 1.26.10 is a good stable release? If so, I will release it to the public tonight. I just want to make sure because the cmd / msi fix has only been out a few days. Please let me know!

 

What was the problem with cmd? I just tried it and it was blocked via Smart Mode just with a flicker of the VS shield no pop-up or balloon. I haven't seen any msi issues for awhile now everything is working well for me with 1.26.10

Daniel

 

Ever since we blacklisted cmd and msi, we have had a lot of minor issues that were all caused by VS not getting the path of the initial file that the user would try to launch, kind of like a parent / child process.

For example, if the user would try to run a batch file from their desktop, VS would block c:\windows\system32\cmd.exe instead of c:\users\dan\desktop\test batch file.bat. And the same applied to .msi files.

So VS could never learn the initial / parent process. This did not create too many issues, but it did create a few. For example, SB would act up a little because VS was blocking cmd lines (or something) it was trying to run. And Cutting_Edgetech had an issue with some VPN software as well from what I remember. And there were others, I just do not remember all of them.

So basically, the issue is fixed now, and we should never have to see the term cmd / msi fix again, thank God. It wasn't the end of the world, but it really is nice to have it fixed.

Edit: BTW, VS will only flicker if it blocks c:\windows\system32\cmd.exe. But, for example, if VS is OFF, it now has the ability to learn a batch file (or any other files associated with .cmd and .msi). So, for example, if a VPN program uses a batch file, it will now work right because VS has the ability to learn .cmd and .msi type files now. I hope that makes sense!

 

Wait for others to reply but I'm good with it. Next would be to Run as a service? I use a VPN at times and I have no issues ever with the software and VS.

Daniel

 

Yeah, and the new kill method that Fabian recommended. I just finished tweaking the desktop gadget so it stays in place even better. And then I will work on the installer.