Yes. I’m aware of the solution. Thank you. The issue is not the solution (although, I’m glad there is one.)- the issue is that Trivantis allowed this to happen in the first place. These Microsoft Defender changes don’t just suddenly happen with no notifications to software manufacturers- or else, every time they updated, all software would suddenly throw these false flags. It seems like you folks have gotten lax over the years when it comes to QC.