Update failed with virus alert

[Blackjack_UK]

I've added DCSUpdater to my exceptions, and have never had a problem until...

Now of course DCS Harrier doesn't work. Which is annoying because tonight I have time to actually get into it.

Suggestions welcome.

Edited July 3, 2024 by Blackjack_UK

[silverdevil]

9 hours ago, Blackjack_UK said:

I've added DCSUpdater to my exceptions, and have never had a problem until...
 

Now of course DCS Harrier doesn't work. Which is annoying because tonight I have time to actually get into it.

Suggestions welcome.

if comfortable, you need to add a few folders to the exceptions. not just the updater. this is for defender but the folders to exclude are the same.

you could also "report false positive" to help others. the files are not virus.

Edited July 3, 2024 by silverdevil

[Blackjack_UK]

Thanks. But why would this happen now after God knows how many years of DCS and AVG living together (since DCS was a thing anyway).

I appreciate the "It's not a virus" comment but you'll understand that I need someone from ED to tell me that (and be prepared to stand behind it)

[rob10]

If you do a little digging in the forums you'll find ED's response is basically the same as above.

AV programs evolve in what they're looking for in identifying potentially problematic files, so it's really not that surprising that something that hadn't twigged before is suddenly caught by it.  The only other advice would be to submit the file to your AV provider and have them whitelist it.

[Blackjack_UK]

Thanks chaps - whatever happened I ran the updater again this morning and it went through fine. Everything works.

 

[silverdevil]

14 hours ago, Blackjack_UK said:

Thanks. But why would this happen now after God knows how many years of DCS and AVG living together (since DCS was a thing anyway).

I appreciate the "It's not a virus" comment but you'll understand that I need someone from ED to tell me that (and be prepared to stand behind it)

 

14 hours ago, rob10 said:

If you do a little digging in the forums you'll find ED's response is basically the same as above.

AV programs evolve in what they're looking for in identifying potentially problematic files, so it's really not that surprising that something that hadn't twigged before is suddenly caught by it.  The only other advice would be to submit the file to your AV provider and have them whitelist it.

as rob says, the AV classifies anything encrypted and not seen before as suspicious. then out of the abundance of caution quarantine the file. this allows the user to decide keep or kill. these files are encrypted to provide some defense of stealing intellectual property. these files are frequently updated with new encryption. so they get flagged again.