VoodooShield/Cyberlock

It is rare situation, but to answer... "No."

The reg hack you did for the context menu "Run as Admin" is one workaround... the other is to use the Admin commandline interface while in "Off' mode to perform the install... unless, Dan, the VDS develper adds an elevated privileges option when faced with installers that require Admin rights.

UAC disabled should not cause failed\problematic installs... maybe a little bit inconvenient but nothing onerous.

See what others think.

 

@VoodooShield I get this a few times with 2.51a Beta as I'm shutting the system down on Win 8.1 Pro x64 but it works fine on reboot! UEFI Mode with SSD's if it matters.

Daniel

 

Thanks hjlbx. I realised later I could have tried an admin command. I suppose one should just be aware that one won't be alerted re admin rights if UAC is off!

 

Ditto. And I think I have had it on my Win 7 Pro x64 machine also.

 

The VoodooShield did not close down properly message you guys are getting is due to a bug in VS self protection. I chat with Dan about that bug 3 weeks ago. It seems to keep poking it's head back out again.

 

I hope it doesn't poke it's head out on my computer. I haven't seen this Error Message on my computer (Win 7x64). Running Version 2.51a beta. Now that I mentioned that I never seen this I'll probably get it. (Hope not).

 

Sorry I have been away, but I am getting close. I keep adding new features when I probably should not be . It has been a lot of work, but a lot of fun at the same time . I could release it as early as 2-3 days, but I really want to make sure everything is working well before I do. Then again, I am sure you guys will find something that I forgot anyway . But I really cannot wait for you guys to try it.

This all started because CET was basically asking me about the multithreading stuff, and the more I looked into it, the more I realized that we needed to change some stuff. Then as I looked into it more, hehehe, I realized that we need to change even more stuff. Please don't get me wrong, if VS is running, your computer is safe, but this new version is seriously cool. Seriously.


I will be in touch soon, please let me know if there are any emergencies! Thank you!

 

Well Garsh Darnit lol, you got me all excited about this next version.

Sounds exciting, can't wait to mess around with some new stuff.

Keep up the great work!

You're doing great

 

Hi Dan,

Many thanks for the info . It's really great to hear about some new features and upcoming solutions .
Keeping my fingers crossed, I'm looking forward to the new version and simply can't wait for testing it .

Best wishes ,

Mike

 

Well, Dan, glad to see that you are being true to form...as I have said in the past...you do not seem to be happy unless you are experimenting and trying to make VS even better than it is at present.

Well, as I have also said on numerous previous occasions...take you time...we will be there when you are good an ready...ready to test the next evolution in the VS story.

Regards, Baldrick

 

Is there a way to generate a detailed log of blocked command lines ?

In other words, one that includes the entire command\pipeline - and not just the interpreter that was blocked ?

Best Regards,

HJLBX

 

2.51a running rock steady. anticipation of the new release is killin me.

 

VDS v. 2.51a beta

Windows 8.1 x86-64 (OEM) Toshiba
AMD A8-6410

Upon system re-start, the VDS widget will first appear as a black\white box in lower right of desktop and VDS hangs for about 1 minute.

Screenshots attached.

 

VDS v. 2.51a beta

Windows 8.1 x86-64 (OEM) Toshiba
AMD A8-6410

Selecting "Maximize Whitelist, User Log, Command Lines and Quarantine tabs" does not function.

FIXED

User must select "Save & Close" to enable setting above.

 

VDS v. 2.51a beta

Windows 8.1 x86-64 (OEM) Toshiba
AMD A8-6410

Command Line quirk.

 

You, and I use a lot of the same software. I have been testing Comodo FW for about a month now, and I also use Shadow Protect, Active Presenter, Peer Block, etc.. Comodo FW has been blocking most of my tray icons ever since I started using it. When Comodo does not block the tray icons it sometimes causes them all to load about 4 minutes after the desktop has already loaded. Sometimes they all load successfully, but with about a 20 second delay. I reported it on the Comodo Forum, but I have not reported it in the bug section yet. I think it could be Comodo, or it could actually be VoodooShield.

Also, do you experience delayed loading of Comodo FW when exiting Shadow Mode? It takes Comodo 30-50 seconds longer to load after exiting Shadow Mode on my machine. I'm using Windows 7X64 Ultimate OEM custom build Core i7 3.2 ghz, 8GB of DDR3, AMD Sapphire Radeon HD 6900 series, etc.. so the hardware should be able to handle to the software without these types of delays. Comodo has had a very noticeable impact on my machines responsiveness when loading applications, longer boot time, and slowed surf speed. I used Online Armor before this, and I did not experience this type of impact on my machine. I have 3 other machines like this one, and they all exhibit the same behavior.

 

I will reply via PM so as to keep forum on topic.

 

I will chat with you by PM, but the point of my post is Comodo could possibly be causing VS tray icon not to load.

 

VDS v. 2.51a beta

Windows 8.1 x86-64 (OEM) Toshiba
AMD A8-6410

If SysInternals SigCheck is used to verify that a file is digitally signed, then VDS Snapshot will detect and whitelist the SigCheck command pipeline. User can easily identify as no hash is generated and added to whitelist.

A few examples...

amdkmcsp.sys c:\program files\sysinternalssuite\sigcheck.cmd c:\windows\system32\drivers\amdkmcsp.sys



exeradar_pro_x86_x64_v3.1_22042015_build1.exe c:\program files\sysinternalssuite\sigcheck.cmd c:\users\hjlbx\desktop\exeradar_pro_x86_x64_v3.1_22042015_build1.exe

lpremove.exe c:\program files\sysinternalssuite\sigcheck.cmd c:\windows\system32\lpremove.exe

lpremove.exe.mui c:\program files\sysinternalssuite\sigcheck.cmd c:\windows\system32\en-us\lpremove.exe.mui

One of those quirks... that may cause confusion.

 

Please consider adding the following setting:

"Start VooDooShield in 'ALWAYS ON' Mode."

Best Regards,

HJLBX

 

Almost finished, sorry it is taking so long. I am hoping I can release the beta by the weekend or sometime over the weekend. And the bugs mentioned above should be fixed. I will let you guys know asap! Thank you!

 

Thanks for keeping us informed

Keep up the great work

 

Dan, thanks for the info!

Mike

 

Dan, it's best to take your time, and do it right. We are in no hurry. I'm not anyways.

 

+1, completely agree