Windows Security not Happy with F-14 File

[Igor4U]

Malware Warning popped up recently - after the latest update (2.9.12.5336); but I don't suspect the Update at Fault because it doesn't look like the F-14 was included in the Update.

Here's what Windows Security Found:

Detected:  PUA:Win32/GameHack
file: F:\DCS World\Mods\aircraft\F14\bin\F14-HeatblurCommon.dll

 

Possible False Positive ?   - Anyone have any more Info on this Booger ?'

TANKS in Advance 

 

Warning Attached !

[Igor4U]

MalwareBytes also fingers this sister File:

DCS World\Mods\Aircraft\F14\bin\F14-FlightModel.dll

 

Guessing I'll need to delete both files and run a Repair - Any Guidance from DCS Masters out there Appreciated

[Rudel_chw]

3 minutes ago, Igor4U said:

Guessing I'll need to delete both files

no need, your AV already did

[sleighzy]

2 hours ago, Igor4U said:

MalwareBytes also fingers this sister File:

DCS World\Mods\Aircraft\F14\bin\F14-FlightModel.dll

 

Guessing I'll need to delete both files and run a Repair - Any Guidance from DCS Masters out there Appreciated

Things of this nature are very common with DCS files being flagged. These are false positives. You should add an exclusion for the entire DCS installation folder to your anti-virus software and run a slow repair. If no exclusion is added then you may find that other files are quarantined/deleted and then you'll get unauthorised errors for your game modules.

Note, some anti-virus software does not allow folder exclusions to be added, in which case remove that software and just use Windows Defender. 

[Igor4U]

Replaced the suspect files in F14\bin with backup of files from July-2024 (files exact same size).

Same Malware Warnings.    So I suspect that these Malware Warnings are False Positives generating from Updated Malware Signatures that are identifying previously clean files now as Naughty Ones.

Flew the F-14 (sort of Rusty - caught the 4 Wire) and all seemed A-OK !

[Igor4U]

So beyond my F-14 Module Malware Detections, logging on yesterday (12-Mar-2025) resulted in the F-14 Module Failing Authorization.

Seems like others have experience the Same, ref:

F14 not authorized (By Semaphore;  17 hours ago in Bugs and Problems)
https://forum.dcs.world/topic/370469-f14-not-authorized/

A few Quick Google Searches (DCSW F-14 Not Authorized) hinted at often times a Solution:

- Add the DCW World Folder as an Exemption to your Anti-Malware Software (especially Windows Defender)
- Then run a DCS Repair (good re-acquaintance with CMD DOS-like Commands)

Seemed to Work - Next Logon - A-OK !

Just an observation here - me 2 cents:

Look - Eagle Dynamics and Heatblur Simulations must know about the certain F-14 Files that Trigger Malware Alerts.    As Smart as their Developers and Programmers are - there has to be a Fix so that these anomalies (Malware Alerts, and Failed Authorizations) don't interfere with enthusiastic DCSW Users who just want some Good Clean Kills. 

Hope this gets rectified before bothering too many Honest (and paying) DCSW Aces out there - TANKS !    

[BJ55]

Yup, but I see it in a different way: the smart AV developers and programmers must fix the false positive issues of their products.

[Rudel_chw]

1 hour ago, BJ55 said:

Yup, but I see it in a different way: the smart AV developers and programmers must fix the false positive issues of their products.

Agree, the fault lies within the AV software, yet people expect a different developer (ED) to fix it.

[Igor4U]

On 3/13/2025 at 1:55 PM, BJ55 said:

Yup, but I see it in a different way: the smart AV developers and programmers must fix the false positive issues of their products.

Yupper - That Too - Especially True !

SHACK lead !