File is clean in case that's the concern. Appears to be a FP, and WD is an ok, and good enough for most people, anti-malware, but it can be a bit over-aggressive IME.

File is clean in case that's the concern. Appears to be a FP, and WD is an ok, and good enough for most people, anti-malware, but it can be a bit over-aggressive IME.

Ya I also did a VirusTotal scan and went through with it too, I was just wondering if the dev would like to try submitting BetterTrumpet to Microsoft's Security Intelligence file review system to see if they could get it whitelisted in the future. ^^

Thought that might be why you were reporting. Not sure it would help, since any future changes that are causing it to get flagged might just trip it up again. I think the issue is that it's lacking a publisher signature, so seems unlikely reporting to MS would help, but maybe, not really familiar with that process. Seems like properly signing the installer would probably be a better solution, though not sure what that involves, either. Also, interestingly, my WD didn't say anything, and it's up-to-date. Just curious, is yours? If it isn't, maybe that's why it flagged this.

Thought that might be why you were reporting. Not sure it would help, since any future changes that are causing it to get flagged might just trip it up again. I think the issue is that it's lacking a publisher signature, so seems unlikely reporting to MS would help, but maybe, not really familiar with that process. Seems like properly signing the installer would probably be a better solution, though not sure what that involves, either. Also, interestingly, my WD didn't say anything, and it's up-to-date. Just curious, is yours? If it isn't, maybe that's why it flagged this.

I think mine is up to date, I'm on v1.457.362.0 right now. =o

Yeah. I was up-to-date when I installed it and responded to you, so just behind where you are now, and I just updated and am now just ahead, and neither time did my WD say anything, so that's odd. I wonder why mine is ignoring it and yours is flagging it. I do have cloud protection disabled but it's unlikely that's a factor given the same results with different versions. Just makes me wonder if there's even an issue with BT (not a malware issue, but one where it's being misidentified by WD) or something with your particular config, though I have no idea what might cause that. Maybe a difference between W10 and W11, though it doesn't seem like that should matter, but it is MS.