DCS 2.9.4.53549 Update Mirage F1

[VictorDavion]

ED,

The latest update broke the game for some third party modules like the Mirage F1. Most anti virus software seems to think some of the modules are trojans specifically the .dLL files. Once it flags them the module is no longer useable and it removes your authorization to use them. Running a repair doesn't resolve the issue because it will not allow the effected .dLL files to be deleted or overwritten requiring you to force delete them. Only solution I have found is to create exceptions for all dcs files in McAfee and then disable all anti virus programs. That seems to resolve it but is incredibly annoying to have to do. Not sure why this update makes DCS elements look like a virus. 

[BIGNEWY]

Hi, 

some antivirus are triggered but it is a false positive, best option is to submit the files to your antivirus provider for inspection. Some antivirus do not like the file encryption and it it flags them as a threat. 

You can also add DCS to your exclusions and run a repair, this usually resolves the issue 

if you continue to experience issues please contact support directly 

https://www.digitalcombatsimulator.com/en/support/

thank you 

 

[VictorDavion]

Yes thats my point and what was done. Its rather cumbersome to go through and figure out what files are causing the issues and then to add each one individually to the exclusion list. 

[BIGNEWY]

5 minutes ago, VictorDavion said:

Yes thats my point and what was done. Its rather cumbersome to go through and figure out what files are causing the issues and then to add each one individually to the exclusion list. 

Yes understood,

I exclude the whole DCS folder, of course how system security is handled is a personal choice. 

thank you 

[Pappy2]

Hello “BIGNEWY”
I also had this problem with the M-2000 and the F1.
can you explain to me how in my McAfee anti-virus the method to exclude the entire DCS folder from analysis.
I can't find it, I can only exclude each .dll that poses a false-positive problem.

Thank you for your troubleshooting response.

[djcat]

Yes the last update also triggered my ESET anti-virus protection by many dll files.

null

[silverdevil]

On 4/12/2024 at 4:52 AM, VictorDavion said:

ED,

The latest update broke the game for some third party modules like the Mirage F1. Most anti virus software seems to think some of the modules are trojans specifically the .dLL files. Once it flags them the module is no longer useable and it removes your authorization to use them. Running a repair doesn't resolve the issue because it will not allow the effected .dLL files to be deleted or overwritten requiring you to force delete them. Only solution I have found is to create exceptions for all dcs files in McAfee and then disable all anti virus programs. That seems to resolve it but is incredibly annoying to have to do. Not sure why this update makes DCS elements look like a virus. 

these are the recommended folders to your exclusions. this is my defender settings.

null

14 hours ago, Pappy2 said:

Hello “BIGNEWY”
I also had this problem with the M-2000 and the F1.
can you explain to me how in my McAfee anti-virus the method to exclude the entire DCS folder from analysis.
I can't find it, I can only exclude each .dll that poses a false-positive problem.

Thank you for your troubleshooting response.

this is what i could find. i do not use mcafee. unsure of its validity.

https://download.mcafee.com/products/webhelp/5/affid/756/1033/GUID-BA648B78-244A-47F1-8AD6-4A57BA8955BC.html

[Black6]

On 4/12/2024 at 10:57 AM, BIGNEWY said:

Hi, 

some antivirus are triggered but it is a false positive, best option is to submit the files to your antivirus provider for inspection. Some antivirus do not like the file encryption and it it flags them as a threat. 

You can also add DCS to your exclusions and run a repair, this usually resolves the issue 

if you continue to experience issues please contact support directly 

https://www.digitalcombatsimulator.com/en/support/

thank you 

 

ED,
if you thing, that you are more trustworthy to me then my antivirus is, then you are wrong. Either you are unable to create your dll’s correctly or they are trully possitive. In both cases I don't accept it. If there wont be corection in next update, I’ll definitely quit.

[hornblower793]

14 minutes ago, Black6 said:

ED,
if you thing, that you are more trustworthy to me then my antivirus is, then you are wrong. Either you are unable to create your dll’s correctly or they are trully possitive. In both cases I don't accept it. If there wont be corection in next update, I’ll definitely quit.

This is always a difficult topic since AV software needs to learn as well. Their advanced heuristic analysis does sometimes trigger incorrectly because of something it has calculated might be a threat. Sometimes this makes them overly aggressive.

[BIGNEWY]

1 hour ago, Black6 said:

ED,
if you thing, that you are more trustworthy to me then my antivirus is, then you are wrong. Either you are unable to create your dll’s correctly or they are trully possitive. In both cases I don't accept it. If there wont be corection in next update, I’ll definitely quit.

Hey totally understand you have concerns. But the dll's are correct. 

As mentioned you need to supply the files to your provider so they can check them and add them to their allowed list. 

thank you 

[zildac]

ED,
if you thing, that you are more trustworthy to me then my antivirus is, then you are wrong. Either you are unable to create your dll’s correctly or they are trully possitive. In both cases I don't accept it. If there wont be corection in next update, I’ll definitely quit.

The files are clean. AV is far from perfect and packers, encryption etc typically trigger a generic detection, which I suspect is what you are experiencing. It has nothing to do with Ed not "creating their DLLs correctly". If you want to test, submit one of the files to Virus total and see the varied responses you get or no response at all.

[Hiob]

2 hours ago, Black6 said:

ED,
if you thing, that you are more trustworthy to me then my antivirus is, then you are wrong. Either you are unable to create your dll’s correctly or they are trully possitive. In both cases I don't accept it. If there wont be corection in next update, I’ll definitely quit.

Perhaps you should look into how AVs work a bit, what they can and cannot do and why there is always an error quota that involves false positives as well as false negatives.

Blind trust in AVs is naive. Even more so in the likes of McAfee.

If you wanna quit over something like that, be my guest. But it is a complete ill informed overreaction.