Could you describe in more detail what is going on? What do you mean with Registry file output is First-In First-Out?
I see that after each boot more and more entries get created in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BFE\Parameters\Policy\Persistent\Filter . I have a long list of entries in my own registry on Win 8.1 x64.
As far as I understand the problem it means that CIS keeps on adding entries to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BFE\Parameters\Policy\Persistent\Filter with each Windows session. Does the count go up further during the Windows session?
With versions beofre 6420 CIS would only create one set of rules? Or would it create new rules deleting previous rules? Do you know?
Edit: CIS does not depend on BFE service. Windows Firewall Service does depend on BFE; I checked the dependencies of the services. May be we’re looking at BFE entries generated by Windows Firewall Service or Windows Firewall? CIS has a bad reputation of not disabling Windows Firewall so we could be looking at entries generated by Windows Firewall.
I did a clean install of 6474 and before I installed it I had my two favorite registry scanner, Auslogics and Eusing, deleting unneeded registry entries. There were no entries removed in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BFE\Parameters\Policy\Persistent\Filter . So I cannot deny nor confirm the plethora of entries are caused by CIS.
In the video it did not happen with version 10.0.1.6294 but started to happen on v10.0.2.6420 and it also happens with the latest version. If you double-click any of the values you will see references to Comodo, e.g. comodo connect v4, comodo resource release v6, comodo closure v4. You have to scroll down some to see them with a dot separating each letter witch represent a null byte.
Also it can’t be said that CIS does not depend on the BFE service as on Windows 10 it can not be stopped or disabled. So you can’t know how CIS will react when the service is not running.