I would be more likely to try getting some debugging info before I start pointing fingers.
If this were a direct conflict with Windows itself, or a select stable of popular 3rd party software, I would agree. For example, were there conflicts with Adobe products (there have been over the years), they get more attention.
But as you aptly pointed out:
As a total nobody developer I also get treated poorly by security software (Heuristic scans are the worst for people like me).
If you \ we had a nickel for every false positive an AV product has produced for either of our software products over the years, we would have retired long ago.
For the record, we have reached out to AV software houses over the years (ForcePoint inc). If we get answers from them at all, we have worked with them to better identify and classify our products.
Lastly, this is one feature being observed on a product, Fences 3, that is 2 full major versions ago. While we make every effort to make sure nothing catastrophic happens with prior versions, it would be a form of malpractice if our primary focus was not making sure the current version was as robust as possible.
Thank you for the feedback, b0b0baggins8712; it is well received.
Sean Drohan
Stardock Product Lifecycle Manager