VoodooShield/Cyberlock

Thank you for tracking that down! What is the website for the VML software? I will try it and see if I experience the same thing, and will fix the issue if possible.

 

VS has extensive logging, and you can always send us your logs if we have issues. Thank you!

 

Thank you for letting us know. What is the path of the G drive process, and what is the path of the process that VS is not allowing you to run? If it is a processes that is not user launchable, this will happen. So we need to make sure VS does not prompt you if this is the case.

 

There is an option in VS in the advanced settings "Do not whitelist items in the AppData Directory". When this is enabled, VS will not whitelist items in the user space. This option was created so that viruses cannot spoof legitimate updates, like Adobe Acrobat update.

The ~ is really hard to explain, but it will be going away very soon, as soon as we run the engine as a service. I am going to start on that as soon as these other last couple of issues are resolved. Thank you!

 

I believe that would definitely be the smart thing to do. I think most users would expect it to return to same mode they were using before disabling protection.

 

I will Pm you.

 

Yeah, I think so too. I do not think there is a reason we cannot do it, so let's try it!

 

This latest version seems very buggy imo

 

Yes latest version from website...VS locks up when the alert window pops up, it blocks programs in program files even though I have it ticked to allow them, when I first boot up VS is blue when in smart mode when no web apps are running.

 

It does seem pretty buggy, but version 1.25 before this one was more buggy for me.

 

Dan, I have a request. Could we not have the same build number released more than once. It can be confusing at times to know whether everyone is testing the latest build. I myself found out I was testing the 2nd 1.25 build instead of the third 1.25 build that had already been released for a brief period. I would prefer 1.25, 1.26, 1.27 etc.. As long as the next build is a higher number build than the previous. It also makes it easier to track progress when posting about changes in behavior between builds. What does everyone else think?

 

I agree

 

Have you tried to click the Default Settings in Settings / About, and reset your whitelist?

This really should fix your issues... the release version on the website is much smoother imo than any other version to date.

Please let me know!

 

Sure, I will include the build number like this 1.25.5

Once we work out the last few bugs after changing to 4 modes, things will be a lot easier for everyone.

 

I had downloaded at least four different builds of v1.25 while I was trying to get .NET Framework to work, and I wasn't confused.

Hey! I will go with the flow...

 

I think I got it from here

http://www.vmlite.com/index.php?option=com_content&view=article&id=47&Itemid=143

 

I just tried it, and yes, I am having the exact same issue. That really is odd, I will have to contact VMLite to find out why that might be happening. I think it might have something to do with the adapters that they install during their installation. I am trying to uninstall it now, and I will try to reinstall and not install the adapters and see what happens. Thank you!

 

I see what you mean about the alert windows... this happened to me when I was installing VMLite. The VMLite installation starts an msi file and VS doesn't know the path of the file. But I am almost finished with the cmd / msi issue, so this issue will be resolved. Thank you!

 

Don't forget the child processes running in %Temp% folder.

Daniel

 

Well I am glad you can confirm the issue. Thought I was the only one creating my own confusion.

There are several other programs that have an issue with VM, one of them being Online Armor. They seem to take the stance that it is for others to work around.

 

There is a list here of known problems.

https://forums.virtualbox.org/viewtopic.php?f=6&t=48044

 

My bad. I was not aware of that.

 

I see Comodo Internet Security listed there as well.

 

I actually only use Always On mode myself when not testing. I always use Smart Mode for testing since it needs testing much more than Always On Mode. I actually have had no problems with Always On Mode except for the cmd, and msi issue you have have been working on. I believe VS will work much better when it is ready to be ran as a service.

 

I will make a special comment in the code that TH requested that we fix this . I am not sure what to do about that quite yet, but it should be easy. Thank you for reminding me .