(In reply to Bryce Seager van Dyk (:bryce) from comment #28) > I've submitted the most recent installer and gui executable (post install) to Microsoft for analysis as false positives (via https://www.microsoft.com/en-us/wdsi/filesubmission). I'll report back if I hear anything. > Microsoft have followed up for both cases and state the detection of these cases should be removed. I'm not sure how fast the definitions roll out, but will keep an eye out to see if these stop getting picked up in the near future.
Bug 1647533 Comment 29 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Bryce Seager van Dyk (:bryce) from comment #28) > I've submitted the most recent installer and gui executable (post install) to Microsoft for analysis as false positives (via https://www.microsoft.com/en-us/wdsi/filesubmission). I'll report back if I hear anything. > Microsoft have followed up for both cases and state the detection of these cases should be removed. I'm not sure how fast the definitions roll out, but will keep an eye out to see if these stop getting picked up in the near future. Edit: Part of the instructions from Microsoft include the following to clear my cached entries > 1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender 2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures” 3. Run "MpCmdRun.exe -SignatureUpdate" I was still having issues until I did this, and now the files no longer appear to be picked up. My hope is that this happens without prompting at some point and this just speeds up the process.
(In reply to Bryce Seager van Dyk (:bryce) from comment #28) > I've submitted the most recent installer and gui executable (post install) to Microsoft for analysis as false positives (via https://www.microsoft.com/en-us/wdsi/filesubmission). I'll report back if I hear anything. > Microsoft have followed up for both cases and state the detection of these cases should be removed. I'm not sure how fast the definitions roll out, but will keep an eye out to see if these stop getting picked up in the near future. Edit: Part of the instructions from Microsoft include the following to clear my cached entries > 1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender > 2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures” > 3. Run "MpCmdRun.exe -SignatureUpdate" I was still having issues until I did this, and now the files no longer appear to be picked up. My hope is that this happens without prompting at some point and this just speeds up the process.
(In reply to Bryce Seager van Dyk (:bryce) from comment #28) > I've submitted the most recent installer and gui executable (post install) to Microsoft for analysis as false positives (via https://www.microsoft.com/en-us/wdsi/filesubmission). I'll report back if I hear anything. > Microsoft have followed up for both cases and state the detection of these cases should be removed. I'm not sure how fast the definitions roll out, but will keep an eye out to see if these stop getting picked up in the near future. Edit: Part of the instructions from Microsoft include the following to clear my cached entries > 1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender > 2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures” > 3. Run "MpCmdRun.exe -SignatureUpdate" I was still having issues until I did this, and now the files no longer appear to be picked up. My hope is that this happens without prompting at some point and the above steps just speed up the process.