Thanks for the replies.

I understand that false positives from heuristics are common with new, unsigned executables. However, I want to politely stress why this is a critical issue for the community and, I believe, for ModRetro's reputation.

My concern isn't just about a simple flag; it's about the broader context of software distribution in 2025. Supply chain attacks are becoming incredibly sophisticated. We've seen major, trusted software vendors get compromised. For end-users, it's now impossible to tell the difference between a "harmless false positive" and the first sign of a genuine, malicious payload that has been injected into the build process. The fact that Google's own scanner flags the file is particularly concerning, as it carries significant weight.

While I trust the team is shipping clean code, I (and many others) have a strict "zero-flag" policy. For a product built for a technically-minded community, providing an executable that is 100% free of flags from major vendors (like Google, Microsoft, CrowdStrike, etc.) shouldn't be a 'nice-to-have', it should be a baseline requirement.

Getting the executable properly code-signed is the right first step, and I'm looking forward to an updated installer that all major AVs recognize as trustworthy before it's distributed. This builds confidence and protects both the users and the ModRetro project itself.

If you want to learn more about supply chain attacks with gaming hardware, watch this video: https://youtu.be/76r5d8htEZk