VoodooShield/Cyberlock

Same here.

 

@mekelek reckon that %appdata% does not get deleted when deleting VS Program data folder with Revo . I did notice that Revo even after advanced scan removal leave things in the computer. I used Everything search tool to scan afterward and manually removed the remnants leftovers.
Without Everything I wouldn't know how to access the leftover files.

 

that 1.4% or 4% can become 50-60% on a low-end CPU real quick.
either way, this CPU usage thing doesn't seem to be related to how VS functions rather leftovers or badly migrated settings/whitelist.

 

It make sense. I came to the same conclusion.

 

I'm manually removing the ProgramData\Voodooshield folder. Is there also an %appdata% folder as well that needs to be cleaned up?

 

%appdata% is from XP as there was no ProgramData Folder, all newer OS's it's ProgramData.

 

Thank you for clearing up the confusion.

 

Well to make it more clear newer OS's have appdata as well but no VoodooShield files in there just in Program Files and ProgramData. But since XP never had ProgramData the VS files would be in AppData. https://social.technet.microsoft.co...ers-and-locations-vs-windows-7-and-vista.aspx

 

Mme plat strikes again. So, I'll try a 100% absolute tabula rasa next time. Who knew?

 

@plat1098 Yes Mme! That seems the way to go. Clean uninstall (tabula rasa) clean install.

 

+1. I saw no VS appdata files on either of my machines.

Edit: Also, regarding the high CPU usage, it doesn't seem to persist ... no evidence of it now.

Edit 2: Strike that. It's back up there, must be some sort of contention.

 

Something strange happened this morning, when I turned my computer on a VS box popped up, I needed to re-register my Pro subscription, everything is working fine now but am wondering if anyone knows why this would happen or if it has happened to anyone else? Thanks.

 

digmor crusher, howdy...Dan is having some issues with the registation and he is working
to fix it..be patient

 

Thanks hayc59

 

Your very welcome...if you want to join another forum Dan landed here for some reason why..?
you got me..strange place for sure
https://malwaretips.com/threads/voodooshield-discussion.63827/page-26

 

Yah, I've been reading that forum for a couple weeks now seeing Dan has been absent from here for awhile, not sure about joining though, too many forums takes away from the beer drinking.

 

Yes, same thing happened to me a little while ago. And, after I re-registered, a popup asking to taking a snapshot, which I the allowed.

>

Also, the CPU usage problem is back, for me. This occurred just before I had to re-register VS, as above. VS had just failed to load at start, and I had to manually load it.

 

It must be a bug because I have the exact same problem.

 

On a machine with EAM on it also, I'm experiencing mild shutdown delays with a message related to Program Manager when VS 4.0 is installed. CPU use was abnormally high as of two days ago. I reinstalled 4.0 after also deleting the folder in ProgramData, as well as two registry keys and the driver. CPU stays at 0% but this doesn't mean much now. Later? I have VS on two computers and the license should be good to cover both, right?

1. Registration boxes pop up after every startup.
2. Re-registering VS and clicking "save" does not survive the startup
3. If VoodooShieldService is disabled via clicking "yes" in below white box, shutdown is not impeded in any way. Clue.
4. If all EAM's real time components are disabled, no shutdown message about Program Manager appears but shutdown is still mildly delayed. EAM doesn't seem to affect registration issue.
5. If release v. 3.59 is installed over top of v. 4.0 beta, registration is remembered and there are no problems at all.



The developer made it very clear on MalwareTips he's aware. I see that reported problems affect some and not others Also: clicking the "Update Check" tab doesn't show the "You are running..." message right away, there's a marked delay there.

Edit: It's been a few hours now and maybe there's some flow from VS to here because CPU/registration problems haven't materialized again. Very nice! Still a Program Manager message at shutdown but that's comparatively no big deal. Great!

 

I am going back to back bed, and CPAP. I am I like the zombie apocalypse.

 

Thanks for that plat1098

I guess I will go back to version 3.59 until this problem is solved.

 

Doesn't seem to be a problem here.

 

Happened to me just this morning.
I registered then after making sure all worked fine I turned the computer off.
When restarted VS did not startup, I had to do that manually. Note that VS is set to logon at startup.
Turned the machine off and restarted once more and all is fine, for now...

 

No CPU usage problem here neither.
And yes @hayc59 Dan is working on it. Sent feedback as requested.

 

This thread seems to be very confusing and not at all favorable for VS - too bad.