Popup alerts are delayed, then show up all at once

When I first installed MSAS, a popup alerting of a change showed up when
the change got detected. Now it seems that a whole bunch of alerts get
bunched up and show up all together. For example, I might change the
hosts file, change an application's configuration to have it load on
startup, install a program, and change the home page for the browser.
These actions were done separately and with a long time between them,
like hours. Then on making some change on which MSAS would also alert,
it finally pops up that alert and along with it popup a dozen other
alert windows. One time, no alert popups had appeared until I
double-clicked on the MSAS tray icon to present its main UI, and then a
dozen alert popups showed up, some for changes that were made so long
ago that I had figured MSAS missed it or was ignoring it.

I realize that MSAS is *polling* for changes (i.e., monitoring).
WinPatrol works the same way. That's why I also use Prevx Home which
will immediately interfere with critical changes to present its alert
popup. This pends the action requested by the application or process,
lets me okay it, and then the process can continue. Because the process
making the change is still there, Prevx can also ask if I want to
remember the allow or block at a later time when that process tries to
make the same change sometime later. MSAS doesn't ask if you want to
remember your permission for an application because it is likely that
the application isn't running anymore that made the change by the time
its polls happens to detect the change. That is, MSAS' detection is
later (i.e., after the fact) but I figure it is still a useful tool in a
suite of tools to thwart malware.

I don't see why MSAS method of polling or monitoring for changes would
make its alerts queue up rather than appear at each poll interval. The
change was made, it was one for which MSAS should alert, eventually
another polling interval comes along, so MSAS should popup its alert
window - but it doesn't. Instead I get them in bunches and long after
many of the changes were made. This wasn't the original behavior of
MSAS; i.e., after a change was made, MSAS would alert on its next poll
to detect the change. Now it is like eventually a change gets detected
whose alert kicks MSAS in the butt to show all the other alerts it
should've shown long before. Then bunching up (or queuing) of alerts is
so prevalent now that MSAS is ineffective in alerting when the changes
have been made and letting the user take corrective action or giving
permission within a reasonable time frame (which is whatever is MSAS's
poll interval). All alerts from MSAS are late, but bunching them up
makes them REALLY late.

--
____________________________________________________________
** Post your replies to the newsgroup - Share with others **
For e-mail Reply: remove "DELETE", add "~VN56~" to Subject.
____________________________________________________________