VoodooShield/Cyberlock

Yeah, it is very odd. I really think it is the adapters on install, but I wonder why it doesn't seem to affect other processes. I will play around with it and see what I can find. Thanks again.

 

While we have the logging, normally it is easier just to have the user try something else and see if that fixes it.

Speaking of that... do you still have an issue with VS in Smart Mode turning blue on startup for no apparent reason? If so, have you tried to disable the USB feature in settings to see if that fixes it? Thank you!

 

Yes, once we do these last few things, VS will be in great shape. Although, I was playing around with an Assembly compiler, and I am thinking that version 2.0 or 3.0 should be written in Assembly, like you previously suggested. We were thinking of doing a second round of fund raising, and we could just hire an experienced Assembly coder to create a killer version of VS. For now, we will just get the .net version of VS running extremely well, that way we have a good, stable version while the assembly version is in development.

 

It's my understanding that an application can be written in both a low level language such as Assembly, and an intermediate level language like C++, or C#. I'm not sure if C is a low level or intermediate level language, but it can be used with Assembly also. I hear some programmers refer to C as an intermediate level language, and other as a low level language. I can somewhat understand the argument for both sides though. Since i'm not a coder I do not know if it would be best to write VS in only Assembly or assembly with something like C++ or C#. I hear assembly is a great choice for writing drivers. I hope to learn at least 1 programming language myself. I can't do it right now though since i'm studying several foreign languages.

 

I have VS uninstalled currently. I had to test some other security software, and I don't like having too many applications on a machine for proper testing methods. I'm going to roll back my machine tomorrow so I will test it again then. I reset my whitelist after uninstall VS. I'm going to clean my machine of any orphaned files or registry entries that I know are safe to remove before reinstalling VS to see if that makes a difference. I have to leave. I will be back later tonight.

 

I am not sure we really need to develop a version in assembly, I just want to make VS the best it can be. I will check it out.

 

Like you said why would Microsoft run some Child processes in the %Temp% folder during Disk Clean Up? Very dumb IMHO.

Daniel

 

Yep right here and I think Dan has to update the folder name 0.94.0.0 as I think that was the first version I tried almost 2 years ago.

Daniel

 

I agree, they must have accidentally put it there and forgot about it. I think the best and safest solution is to let Training Mode whitelist items in the appdata directory. You would have to temporarily switch once to Training Mode once, but it will fix the problem without creating a security hole. Does this sound good?

 

Wow, time really flies, huh? Thanks for all of your help!

 

I don't really care as long it doesn't create a security hole? At this time I put it in Training mode to do a Disk Clean up then after put it back to smart mode!

Daniel

 

I was actually just working on this issue, and I noticed that MS changes the path of the dismhost file each time Disk Cleanup is ran... this might be a little tricky, but there has to be a way around it.

c:\users\dan\appdata\local\temp\813f9a58-db3e-4908-8435-cc78e4f33d0b\dismhost.exe

c:\users\dan\appdata\local\temp\4d6e70aa-3f49-4b4d-bb0c-f9b8fedc83b6\dismhost.exe

FYI, my internet keeps dropping every 5 minutes the last couple of days, so it is almost impossible to work on VS right now.

 

Just tried to allow an automatic update, but couldn't get the VS alert to allow. Just didn't respond to my clicking on the button. I was in smart mode.

 

Cool, thank you for letting me know, I see what is going on.

Whenever VS will not Allow something after clicking the Allow button, can everyone post the path of the file that is will not allow? This will really help a lot! Thank you!

 

This version should fix the ~ issue on the Allow Button. And VS will go back into your previous mode if you are in Training Mode or Disable Protection. Also, I think the USB on reboot problem is fixed too. I also added a feature that checks for an internet connection to help speed up the start up even more.

I am getting really close on the CMD / MSI issue. I still have to figure out the TH Disk Cleanup Issue.

https://voodooshield.com/freeoffer/Install VoodooShield.1.26.1.exe

 

Thank you, i'll try it here soon

 

Cool, thank you! If for some reason the Allow button does not work, please post the path. I also just fixed a problem with the AppData feature, but I will post that tomorrow, hopefully with the cmd msi fix .

 

The path was C:\Program Files and when I went to click system protection in control panel VS blocked that as well.

 

What were you trying to run when it blocked the path C:\Program Files? That is all that it gave you for the path?

Are you sure that Automatically allow Program Files and Windows System folders is enabled in settings?

Have you tried to click the Default Settings button in Settings / About?

Are you running SUA?

 

The Process Lasso update went through, with no Alert prompt this time. VS Log shows it was allowed. So, good!

 

Oh no the path in the alert was this "~"...I was opening ccleaner yes I always have those 2 options ticked.
nope admin account

 

Very cool, thank you for letting me know.

BTW, I found a small bug in the new Previous Mode feature, but it is already fixed in the version I will release tomorrow.

 

Eagerly anticipated. Thanks.

 

Have you tried to click the Default Settings button? How old is your whitelist? With all of the changes VS has been through, it would be best to reset both. Once we get over these changes, we should not have to keep resetting these. Thank you!

I am off to bed, but I will check the posts in the morning.

 

Probably a few weeks old, I haven't tried it yet