Windows Defender quarantines 0.2.4.2 & 0.2.5.0

[celynw]

Windows Defender is quarantining v0.2.4.2 before I get a chance to run it.
The problem is reported as Trojan:Win32/Azden.A!cl.
Perhaps the cause of this was introduced in the dependencies updates?
I am running Windows 10 build 17763.316

[Otiel]

Thanks for reporting this.

It's probably a false positive. VirusTotal screams 1/69.

I'll have a look at the updated dlls and see if anything pops up.

[Otiel]

This should be fixed in v0.2.5.0

VirusTotal now reports 0/69:

[dermalikmann]

@Otiel sorry, but... not anymore

[Otiel]

@M4Lik thanks for the warning.

I'll see how I can submit a false positive report to Microsoft - never had to do this before.

[celynw]

On the plus side, it seems fine if I build it myself 🤔

[Otiel]

@celynwalters I have no Windows Defender report as well on the machine I use to build it. I'm not sure how Windows Defender works, maybe it whitelists every exe you build via Visual Studio?

[Otiel]

Case submitted to Microsoft. We'll see what they say.

[Otiel]

Got an answer from Microsoft, saying they've "removed the detection".

It seems all good on my machine now (threat definition version: 1.289.1250.0). VirusTotal is back to 0:

Can you let me know if you can run it now?

[celynw]

Nice - works perfectly for me.
Thanks!