5.0.36 out now

[Lumin]

What differences have you made codewise between V5.0.35 and V5.0.36 Campbell? AVG had no trouble with previous versions of ADRIFT.

Pretty sure being new would be all that's needed, the last version has been out in the wild for years and so is looked at as being safer.

[Campbell]

What differences have you made codewise between V5.0.35 and V5.0.36 Campbell? AVG had no trouble with previous versions of ADRIFT.

Which version of 5.0.36 did you download? I packaged 5.0.36.1 differently, in the hope that it would trigger less false positives, but 5.0.36.2+ were using the same method as previous versions. The only differences in the code are those listed in the release notes, but as Lumin says, the fact that there are any changes will mean virus software will have to become familiar with the new version to deem it safe.

[NickyDude]

Which version of 5.0.36 did you download? I packaged 5.0.36.1 differently, in the hope that it would trigger less false positives, but 5.0.36.2+ were using the same method as previous versions. The only differences in the code are those listed in the release notes, but as Lumin says, the fact that there are any changes will mean virus software will have to become familiar with the new version to deem it safe.

ADRIFT5Setup.zip. The one on the Download page (12th September 2020).

Clipboard01.jpg (42.71 KiB) Viewed 677 times

[Campbell]

Did you click on Report as false positive?

[NickyDude]

Hmm, seems like AVG may have sorted it as I'm not getting any threats any more!

[Denk]

Now Bitdefender starts complaining about dev500.exe (but not run500.exe), so I just sent them the file. It should be fixed within 72 hours they say:

Dear Kenneth Pedersen,

Thank you for your file submission.

The file has been automatically sent to our laboratories for specialized analysis. If the file is indeed a False Positive, the detection will be removed in the next 72 hours and the modification will be implemented in the product through a Signature Update. Please keep your Bitdefender up-to-date.

Please be informed that this is an automated process. Reply to this email if you have any other issues regarding your Bitdefender product and one of our engineers will take over.

Have a nice day!

[Campbell]

...I just sent them the file. It should be fixed within 72 hours they say

Thanks.

[Denk]

...I just sent them the file. It should be fixed within 72 hours they say

Thanks.

Just tested Bitdefender to see if it had stopped flagging dev500.exe as infected. The problem is gone from Bitdefender now

I also checked run500.exe. No problem.

Still, I expected user-generated ADRIFT exe-files to be regarded as "infected". But there were no problems with that either!
(it might depend on the game though...)

[Campbell]

That's great. So hopefully we're good until the next release.

[Kennedy]

McAfee flags the files for "suspect!211caec1322e"

[P/o Prune]

McAfee flags the files for "suspect!211caec1322e"

Can you report that it's safe, like suggested earlier in this thread?

[Denk]

McAfee flags the files for "suspect!211caec1322e"

It is "funny" how each Antivirus Software claim that they know the name of the "virus". None of the software agree on the name, which makes sense as there isn't a virus.

[Lumin]

Would Campbell registering Adrift with the Microsoft Store sort this out with all of them at once? I thought I saw someone mention this, and if so it seems to be the simplest and most obvious fix. (Or does it even have to be Campbell himself?)

Might as well take advantage of the only perk of being a Windows only program.