....
Then i disabled vengine.exe autorun, closed FF, killed already running vengine.exe. And launched FF again. It seems VE operating exactly like before (with running vengine.exe).
...
(seems like "VerificationEngine" plugin for Firefox which got installed by VE installer does all job for FF...)
Hi SS26,
I think you are right and actually
quite indirectly (that was not a major concern at that time) that was pointed in
Reply #2 here:
https://forums.comodo.com/verification_engine_allows_you_to_verify_what_you_see_on_the_internet/constant_crashes_of_firefox_after_vengine_27024_upgrade-t43735.0.htmlInterestingly enough I had a question for some time, which may be related to your request,... but did not ask yet:
Since Vengine indeed needed as a plug-in/add-on for the browsers it seems to me the existing startup entry on system Boot is a bit redundant... (sure I may not know all intentions by developers)
What's happening - the yellow pop-up notification window stating that V-Engine cannot connect to the server..." and so on... being displayed on every Boot when there were no request yet for any browsing session.
It looks more surprising when the user will even disable the connection and Reboot.
Vengine does not take that ("no connection") into consideration at all.
I don't see the purpose of that pop-up, but it would be nice if developers answer both our questions
My regards