I believe the plan is to update Voodooshield with the engine now being tested in DefenderUI Pro... will Voodooshield also need Tamper Protection disabled too in the future assuming it will share some of the behavourial monitoring etc? Apologies if this is a silly question but where each product's protection starts & ends sometimes goes over my head
The Tamper Protection restriction only applies to the handful of MD settings, and since VS does not include these MD settings, this will not be an issue for VS. A couple of years ago I was going to include some of the MD settings in VS, but I think it is much better to have a completely separate product (DefenderUI).
And yes, the Contextual Engine I am working on for DefenderUI will most likely replace a lot of code and features in VS. When I first started building the new Contextual Engine, I was unsure if it was even possible to build such a thing, and I was also not sure if it would actually protect the system while further reducing unwanted blocks. But it looks like we are in the clear now, so it is full steam ahead. BTW, if I would have tried to build the new Contextual Engine in VS, it would have been a total mess. But since I built it with DefenderUI, it allowed me to build it from scratch. So I am not putting VS on the back burner by any means... it is just better and easier to do it this way.
Once everything is in place, I will explain how the new contextual engine works, even though it is quite difficult to describe. I am actually still coming up with new features within the engine, but I believe it is almost complete. And once it is complete, VS will behave essentially like DefenderUI Pro, so it should be just as robust as VS, with fewer unwanted blocks, and we may be able to completely remove Command Lines from VS. Command Lines are still handled in the Contextual Engine, but in a really unique way that should not involve user intervention. Thank you!