I may just be missing something here.  I have a short MIDI clip with mod wheel automation on it.  I want to play it back with the mod wheel changes muted/ignored.  So I add the MIDI Event Filter MFX plugin to the MIDI track.  I check the controllers box.  I'm expecting this to filter out all the controller events. 
 
But nothing gets filtered. 
 
So I press the All button. I expect everything to get filtered, so no notes.  But oddly enough nothing changes.  So I try None.  No change.  So I think perhaps it's a routing issue so I try a bunch of combinations with LoopBe and additional MIDI tracks.  But nothing changes, no matter what I select. 
 
Is this plugin just completely broken? Is a recent thing, I couldn't find anything in the forums but the search is kind of weak? 
 
Is it an install issue?  Do I have an older version and it doesn't work right and the installer didn't put the current one out there?  The about box for the EventFilter.dll says version 17.5.4.0 Copyright 2016, which makes me think it isn't some old relic from X1-X3 days.  But I'm kind of confused why I can't get it to do anything.

OK it doesn't filter what you specify, it allows.  So to block all the CCs you have to set the controller range to 0 (on top) to 127 (on bottom).  You also can't seem to toggle it on and off while playing.  I had to restart the transport to get it to take effect (must be something to do with how MFX plugins work I guess).
 

Seems to work OK here using the same plug-in version here and SONAR 23.6.0.24. Here is the setup to filter ModWheel.

Keep in mind MIDI data is buffered. Changing values on the fly does not immediately effect playback.

I believe you had it right - click the controllers box, but drag the value slider beside it to 0.
Very fiddly interface, and would definitely like to see this get a real update.
 

I see Scook replied - 
Yes that works too - 
Either set all controller Values to 0, or Filter out controller 1 (Scook shows 2 - 127)
The IFace is geared for filtering blocks - I use it often for filtering ranges of notes for specific instruments.
 
 

I think for routing note ranges it makes more sense. Mostly my fault because I just wanted to block CC1 but let CC0 and 2-127 through, which I'm not sure can be done with it in one step.  That All and None being the same thing with the default settings was also kind of confusing.

msorrels
I think for routing note ranges it makes more sense. Mostly my fault because I just wanted to block CC1 but let CC0 and 2-127 through, which I'm not sure can be done with it in one step.  That All and None being the same thing with the default settings was also kind of confusing.

Yes exactly right - (not about it being your fault). It's a strange interface and not well suited to blocking individual CC's especially in non-contiguous blocks. Glad you got it working.

Just in case anyone else ends up here via a search, the key range in the MIDI Event Filter MFX plugin doesn't take into account your SONAR setting for base octave for pitches.  Mine is set at -2, but the plugin doesn't see that.  So C4 is C6 in the plugin.
 
In addition it doesn't seem to apply to the Piano Roll View's left hand virtual keyboard.  Every key lane will pass though.  It only seems to process incoming MIDI from a keyboard or MIDI recorded on the track.  Which was super confusing.
 
With a MIDI playback buffer of 2500ms (I got tired of missing notes so I went to extremes) it really makes it hard to test also, since you make a change and it doesn't show up for 2.5 seconds.  Most users won't have that high a MIDI buffer, but it definitely is an issue.