Unchecking any filter items with a "Result" column should fix it. The problem that results are coming after the operation completes, where new events may have already occurred. We don't currently remove an event which is not the last.
I will look for ways to improve this.
Possible bug - Drop Filtered Events not working anymore in Process Monitor 3.70

Drop Filtered Events is not working anymore in Process Monitor 3.70.
Drop Filtered Events works ok in Process Monitor 3.60.
Behaviour in 3.70: enabling Drop Filtered Events has no effect
Behaviour reproduced in Windows 10 Build 18363.1443 Version 1909
Behaviour also observed on other windows 10 builds and also on win server.
Behaviour can be observed in the UI as following:
- in 3.60, enabling Drop Filtered Events stops the counter in the status bar.
- in 3.70, enabling Drop Filtered Events does not stop the counter in the status bar.
Tested on 64 bit.
Filter list used:
4 answers
Sort by: Oldest
-
Pavel Yosifovich @MS 11 Reputation points
2021-04-29T09:24:21.807+00:00 Claudiu C 1 Reputation point2021-05-10T16:31:29.633+00:00 That's correct @Pavel Yosifovich @MS . this seems to be introduced in 3.70 though as 3.6 and 3.5 don't have this issue.
ssrmm 1 Reputation point2021-05-27T19:17:30.393+00:00 I ran into this as well.
In addition to the events not being dropped I'm also seeing a performance problem when "Drop filtered events" is enabled while there is a "Result" row in the current filter. I haven't measured anything, but it's really significant. Purely from eyeballing it I would say it's somewhere in the range of two to three orders of magnitude slowdown in this situation!