At least for some is used predefined system application and for the second custom rule.
My Home PC not handy now, so I will check effective custom settings later.
I have checked the one with user custom rules. All items were to ask and protections to inactive. ( strange for me )
When I have checked the one with predefine system application rule and switched its rule to user custom settings to see them, all setting were the same as above ( to ask, inactive ).
while previously running CIS 4.x FW+DEF+, all was OK
I have 3 important notes to CIS 5.0, especially DEf+ part.>
I usually reinstall CIS ( without AV ) in case of major upgrade. But last time I was “cheated” by autoupdate, thinking it is minor update. After reboot i have realized I had CIS 5.0.
since then I had always strange troubles when creating and launching my own CMD, running some executable.
I had often to make multiple confirmation to override various CIS protections to run CMD smooth.
Usually by setting it as installer or system application.
If I had chosen just allow in DEF+ triggered action alerts,
I had often to allow the same action for the same CMD multiple times.
using Avast AV, it happend time by time a full single core CPU business by CFP.exe, lasting dozens of seconds till minutes ( something like that mentioned in bug reports ). Once or twice I have tried to close and relaunch FW gui ( CFP ? ). After launching it ( as limited user, because it normally runs at my limited account ) I have realize all DEF+ app rules are gone. confirmed several times.
I guess probably the clean install will be good, but until then I wait for eventual investigative cooperation.
BTW I use Comodo FW since W2K and version 2.4, then on vista64 CIS since 3.0 till 5.0
Not in my case (checked), because both c:\path\anyfile.cmd and \path\anyfile.cmd are valid records for existing files. there is no problem in deleting them, but why CIS creates them ?
I am used to work in vista 64 Home Premius SP2 under limited account, but keep running Process Explorer under elevated Administrator privileges to be able to manage all processes and able to launch elevated processes without extra providing passwords.
When I deleted DEF+ both duplicate rules for given CMD files, I have realized this>
If CMD is launched by Process Explorer, it triggers DEF+ dialog for launching EXE , recorded as a rule for c:\pathname.
If CMD is launched within limited account, it trigger vista UAC privilege elevating dialog, and than it triggers DEF+ dialog for launching EXE, recorded as a rule for \pathname.
I have checked the order of cmd trial launching does not matter,
neither matter if the other way of launching was already performed or not.