I set D+ to Safe mode and installed FrostWire 4.17.1
(I attached a md5 signature of all Frostwire files generated using DVDsig
I manually added FrostWire.exe to D+ Pending files List to manually run the Lookup function and have D+ contact Comodo just in case this new FrostWire version was not added to the bundled safelist released with CIS 3.5.54375.427.
FrostWire 4.17.1 policy was automatically created by D+ safemode but the resulting policy Run an executable
access right didn't have any allowed nor blocked application entries.
To confirm this I manually closed Frostwire soon after it was fully loaded and running.
In the attached pic I manually copied an help file to Frostwire shared folder and I launched it by right-clicking (doubleclicking on each file will work in the same way), only then hh.exe was added to Frostwire policy - Run an executable
To confirm this I manually closed Frostwire soon after I launced the help file.
D+ safe mode automatically added to Frostwire.exe Run an executable
allowed applications access right only other executables already safelisted by Comodo as soon as I launched them from Frostwire library.
Since Firefox recently released a 3.0.4 update which was not included in CIS 3.5.54375.427 bundled safelist, double clicking on Frostwire upper-right logo did not automatically launch Firefox but triggered a Run an executable
As soon I performed a manual lookup for firefox.exe (manually adding it to my pending list to perform the lookup and removing it from pending list afterwards) D+ safe mode automatically added firefox to Run an executable
allowed application access right of Frostwire.exe since Firefox 3.04 has been safelisted.
Provided that frostwire.exe is only a stub to launch the actual FrostWire.jar java application I can confirm that the frostwire.exe bundled with FrostWire 4.17.1 is the same you got on your PC hence any difference in observed behavior could be related to the other java files loaded by frostwire.exe stub executable.
It would prove useful to uninstall your current frostwire version and remove your current frostwire.exe D+ policy to install FrostWire 4.17.1 (or a more updated version)