I am using WRSA Essentials 188.8.131.52 beta therefore I am posting this here even if I am sure the release version has the same problem. I am using Aurora as browser (it's really fast and great experience btw!) and even before that with beta Firefox mostly I noticed often a strange behaviour of WRSA: if I install new updates - let's say now daily for Aurora - then WRSA doesn't seem to realize that at first. - Why not!? I am talking about the monitor function. That does often only kick in after another (!) restart of the program - or reboot - (I guess when firewall first sees "new" activity of the new version and "old" activity "cache" of older version is outdated?). And that is extremly annoying to me! I don't want Aurora/Firefox to be monitored at all and never because for performance reasons (stopping unnecessary log writing activity etc.) and because I trust Mozilla. But as it is I simply cannot tell WRSA immediately after installing the new browser version to NOT monitor it (that would be quite annoying also of course, always having to do that I mean!) as it DOESN'T seem to be aware for a long time of the mentioned update. After a certain much to long period of time (as I said: maybe first firewall event of new version triggers that?) then "monitoring" is ON and only then I can disable that even if I used the new browser version for let's say half an hour until then!? Believe me: it's really annoying! And some flaw in detection of new programs in WRSA anyway. So please fix that bug ASAP. - New programs (updates) should either immediately be monitored (if not known to the cloud yet) or maybe - even better - we could chose an option for browsers like Firefox, Aurora etc. to *NEVER* monitor them. - That thing is bugging me for quite a time and now finally I had enough and thought I should report that.