VoodooShield/Cyberlock

Dan and VS just have a new home, it's not that confusing or drama filled.
Here is the link: https://malwaretips.com/threads/voodooshield-discussion.63827/
PS: VS is doing just fine

 

Yeah, I also am not keen on joining yet another forum, sorry.

I'll keep watching from a distance.

 

Everyone please remember that version 4.0 is a BETA version! It's not a final release! If you don't like dealing with bugs, then I suggest that you wait for the final version.

 

Right on. Either that or try again the next day, the developer is so attentive, it's possible whatever problem you had is gone or going.

If you're running 4.0 beta yourself, you would have no problems following this thread.

 

+1

 

@JohnBurns, @Krusty

Since I decided to follow VS at MT I still share my findings on here. I wonder though, with Dan not active on Wilders, on the long run sharing from both forums may just validate your points.

 

Well, after a few more zzzz's [sleep], I just started VS again after starting the laptop [coming out of hibernation].

CPU usage is back to normal for VS .

>

 

Yes mate welcome to the seesaw, this is the life of a beta tester

 

Yeah, got the re-registration on both machines with reboot, even though both had registered successfully initially. But we know Dan is applying fixes there.

The CPU usage problem is inconsistent for me: but generally around 12-13% on secondary machine, and around 23% on the primary (when it occurs). I don't think disabling scanning of child processes makes a difference, though can't be sure yet. Edit: It doesn't, in my case at least.

On my primary machine only, VS does not auto-start, but setting VS service to 'automatic, delayed start' seems to be the easiest way to fix this.

Otherwise, indeed there is no 'drama'. Will still need to wrap my mind around the (optional) Rules builder.

Posting this for info only. Maybe Dan does still read here, but maybe only worth posting at his 'new home', even though it does cut into drinking time @digmor crusher ; at least he interacts there.

 

Just noticed my innocent comment which was posted at #17434 originally, has been removed. I am disappointed!

 

Thanks for alerting me to the Alerts feature on Wilders anyway, never noticed or used it before .

 

I happened to be on "the other forum" just now and here is the 4.01 beta. Timing is everything.

https://malwaretips.com/threads/voodooshield-discussion.63827/page-26#post-668625

The only way I can get a clean shutdown is to exit out of VS 4.0 first. Exclusions in EAM don't work right now. Let's see what this does.

Addendum: Yep, shutdown is still hindered unless VS is exited prior. That's it so far: no registration boxes, no CPU (very quiet there) issues, no excessive memory usage, no errors in Event Viewer. The only observation persisting from 4.0 is that VS is in the systray from the moment the desktop loads yet is not in Startup programs/task manager.

 

Just installed VS v4.01b beta over the top, and no reboot, so far. Still have the CPU utilization problem.

>

>

 

Back, after a reboot... and CPU is OK. I don't understand. But, I can't access my screenshot, because my browser [freshly loaded] is now in an isolated environment because of ReHIPS, which I have started using again, recently.

 

Just took a screenshot, and it shows CPU...not good.



Just noticed in that other VS forum, that the registration of VS is still a problem. However, it is not an issue for me with this new beta.

 

I don't know how you could have missed that feature, all this time. But I am glad, you are now in the picture, so to speak.

 

Verify same here as above. Also, notice HKLM/Software/Microsoft/Windows/Current Version/Run----is gone. VS not showing in startup either. Also with VS 401b had to re-register 4 times after re boots. No CPU issues though which is a plus. At the moment have uninstalled 401b and will wait for the final stable version.

 

Yes, that's a chunk of your CPU, @Tarnak Here's something, I left the machine for a bit, when I came back, Automatic Maintenance was running and so was VS 4.01. Jiggled the mouse and that stopped the maintenance but VS executable kept going. Like you did, a restart made that go away. Also, on shutdown, this time VS specifically came up as preventing shutdown, so there's that. Hope the developer looks in here periodically, the CPU problem is not insignificant, right?

 

I looked in registry then, on main PC with release VS 3.59, VoodooShield subkey is there. On machine with 4.01 beta, there is nothing there. Hmmmm.

 

Yes exactly the same here. VS Run subkey is there with 3.59 but as soon as 4.00/4.01beta is installed, the Run key in HKLM disappears...like magic So for me anyway, with this problem and the shutdown problem I am going to give it a rest for now. Maybe a more stable version will be available later and then will try again.

 

There is no need for an autorun-entry, if VS is started by the service:

Code:

v3.59 (Autorun)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"VoodooShield"="C:\Program Files\VoodooShield\VoodooShield.exe"
v4.0 and newer (Service)
VoodooShieldService (Auto Start) => VoodooShield.exe

Edit: Nevertheless, in some cases the service doesn't seem to start VoodooShield.exe and VoodooShield.exe has to be started manually or the user must add an autorun-entry for it.

 

mood, I wasn't aware of this--obviously. This is obscurely a relief.

 

Well I guess that answers that problem then. Maybe you have the answer to this problem also....."Experiencing mild shutdown delays with a message related to Program Manager when VS 4.01 is installed"....."The only way I can get a clean shutdown is to exit out of VS 4.0 first"..."Shutdown is still hindered unless VS is exited prior".

 

Oh, OK. This was already addressed then.

https://malwaretips.com/threads/voodooshield-discussion.63827/page-21#post-667648