VoodooShield/Cyberlock

I will wait for the next build since this one already has confirmed bugs.

 

good to hear you're feeling better

 

Dan, will VS be able to run on dotNF 4 anytime soon?

Thanks,
TS

 

Right he doesn't understand our security fanatic (Guru) from down under.

 

Ok, I THINK this version is bug free, but then again, I thought that last time . I am not sure how that bug came up, but it has been around for 8-9 months, but we just have not seen it. Anyway, here is the latest version, please let me know how it does. Thank you!

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.48 beta.exe

 

Hey Baldrick, I did not post several versions before 2.47... I think the last one was 2.41. But please try 2.48 when you get a chance, I think we are just about there!

 

Thank you MrGump!

 

Hey The Shadow... yeah, once all of the bugs are worked out I can compile a .net 4.0 version. There are several ways we can do this... I might just include both versions in the installer so that VS uses the native .net version and so that the installation completely seamless. Thank you!

 

hehehe, you guys crack me up!

 

1. using Launchy http://www.launchy.net/ when i attempt to launch Programs and Features or Windows Update i receive "wuapp.ese -system error the program can't start because MSVCR100.dll is missing from yor computer. Try reinstalling the program to fix this problem." Programs and Features and Windows Update still launch I just never used to get this alert.

2. I have been viewing the VS log and it is not behaving like it used to. It no longer lists apps run for the first time. It does however list Webroot and Peerblock and VS and OpenVPN as allowed. No other programs I launch seem to register.

 

@Baldrick

Methinks what FleischmannTV meant is that he holds the deepest sympathy for developers to explain why things break for users that are already running so many security applications that the they should either contradict, cancel each other out, or quite simply melt down the operating system almost at boot-time. (How much is too much, eh?) The F-TV man will correct me otherwise and I will stand corrected accordingly.

 

Hi Dan

Thanks for the new version. Just installed it so will see how it goes, but for starters I find that VS is popping up for programs already added to the Apps list.

Update - it is generally blocking programs from "Program Files" etc.

 

Sorry Dan to bring up more problems.

Had to access my fonts from Control Panel but it was being blocked by VS. Then noticed that the VS icons and sys tray had also disappeared sometime previously, so the only option left to close VS was the remaining running process in background processes. This enabled me to access the fonts.

Once VS has been closed like this it will only run as a background process and will not be active in protection. System has to be rebooted to start correctly.

 

Hi MrGump, MSVCR100.dll is part of the C++ runtime that is installed with VS, and apparently Launchy. This should not be a common issue because VS and most likely Launchy does not uninstall "Microsoft Visual C++ Studio 2010 x64 (or x86) Runtime" when VS or Launchy is uninstalled. But either way, it should be an easy fix. I would uninstall VS (there is a new version anyway ), and uninstall the "Microsoft Visual C++ Studio 2010 x64 (or x86) Runtime". If you can temporarily disable Launchy from starting on startup, that would be cool (otherwise you will probably get an error on startup). Then reboot, install VS and reboot again. Then you can reenable Launchy on startup. If you have any problems, please let me know. These runtimes usually do a great job of maintaining themselves, but as you have seen, sometimes anything that can go wrong, does .

On your second point... I fixed a bug this morning... I will describe it a few posts down, along with a link to the new version. Thank you!

 

Hi ThreeCubed!

 

There was a pretty big bug that everyone's posts helped me figure out. If you look at VS's userlog, you will notice that the process names are not all lowercase. Well, I am not sure how this happened, but they all need to be lowercase (like in every other version of VS), otherwise when VS compares the process name, path and hash, if it does not match up, VS will block it, even if it is on the whitelist. Somehow it ran fine on my test systems all day yesterday, although I am not sure how it did with a bug like that.

Anyway, it is fixed now... I have not tested this version a great deal, but it was a simple bug that needed to be fixed asap, so I just fixed the bug and kept the 2.48 version.

Please let me know if any processes ever show up as not lowercase!

Edit: I removed the link, I need to do a little more testing. As soon as it is working perfectly I will repost the link.

 

TH was right, hehehe, VS really should start in Training after installation at least for 5 minutes or so. In the last few versions, I made it so VS would start in Smart OFF mode, thinking that the initial snapshot was enough to train VS. Well, that turns out to not be the case, so 2.48 now starts in Training Mode after installation. Sorry for all of the troubles and thank you for your help!

 

Kwel will download now and install!

Thanks Dan,

Daniel

 

Hey TH, please try the new version in a few hours, I will let you know as soon as it is ready!

 

Sure thing!

 

Hi Dan

Apologies for being late to the party but just finished work for the day and seem to be late to party once again. Luckily I read to the end of the thread before installing .48...as it looks like a further versions is due shortly...is that correct? If so then I will wait for that and then test the latest.

Regards


Baldrick

 

I appreciate your point (and think the whole conversation is funny), but on the other hand, if VS will run well on Tarnak's system, it should run well on just about everything . My test systems are the opposite, they need to have more software installed to better emulate real world testing. So I hope Tarnak (and everyone else) knows that I appreciate everyone's help tremendously! BTW, have you tried VS yet? Please email me at dan@voodooshield.com if you want a Pro license. Thank you!

 

LOL...Everything, but the kitchen sink runs on my system.

However, trying v2.48 has not improved things on my system, and is the same as v2.47 for me, with the same problems. However, this time around I didn't get the popup from Zemana AntiLogger.

 

Yeah, that's funny .

Here is 2.49, I really think it is good to go now. I know, I have thought that before, but for real this time .

BTW, VS will act differently on Windows XP compared to Vista and above. There MIGHT be some small issues with XP, but I think it is good to go.

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.49 beta.exe

 

A bit sluggish getting the system up and running, with the systray and sysclock freezing for about 2 minutes from about 6.57 pm.

However, it is running and my browser opens. So, I am feeling better with v 2.49.