Welcome to The Bug Genie
Please fill in your username and password below, and press "Continue" to log in.If you have not already registered, please use the "Register new account" tab to do so.
Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
This issue has been closed with status "Upstream" and resolution "Not determined".
Create a comment There are no comments
There is nothing attached to this issue
The following issues are duplicates of this issue:
There are no code checkins for this issue |
|||||||||||||||||||||||||||||
Really delete this comment?
Seriously though, there isn't really anything we can do about this. With the current state of Windows antivirus I suggest ignoring all machine learning detections like those that contain "!ml", "!ai", "!cl", "Generic", ".Gen", "Artemis", "ML." in their name. It is disappointing to have to give this advice since there is legit malware out there, but the current state is ridiculous.
As for signing the executables: That is expensive and complicates the build process while not even making any guarantees or allowing reputation to carry across different releases from the same publisher or of the same software, unless you get an EV certificate which are only available to corporations. I'd be happy to use signing if there was a sensible solution (like there is Let's Encrypt for SSL), but there is none.
If you want, you can try submitting the file as safe here, but it is unlikely to do much as the next release will be flagged again by our artificial "intelligence" overlords: https://www.microsoft.com/en-us/wdsi/filesubmission
The issue was updated with the following change(s):
Really delete this comment?