Hello Chris,
Thank you for your message.
This is a
false positive detect - unfortunately, new detections are usually expected when there is a new version out and it might take a while before a/v software learns to recognize new files as harmless. Unfortunately, we don't have much control over this process other than regularly submitting f/p reports ourselves (which we already do, but sometimes vendors are very unresponsive, unfortunately).
Please try submitting a False Positive report to Microsoft following the steps provided on
this page - this should help to resolve the issue and remove the detection pretty quickly.
Meanwhile, as a temporary workaround you can also add the detected files and installation folders to the exception list as described
here.
Please let us know if you have more questions.
