Windows Defender reports M-2000C\bin\M2KC_FM.dll is a PUA:Win32/Packunwan

[MAXsenna]

So…then this is not dcs’ problem and it’s just left up to each of us individually to just tell our microsoft defender or whatever antivirus to ‘ignore’ this find? Is that the consensus? But what happens if we encounter this virus for real from somewhere else? Does it just get through then? And also, I just want to make sure that there was indeed another update since the one posted in the changelog on 6/5/24? That my dcs updater did not somehow get hijacked during the update check into downloading an actual virus from another site mimicking dcs?

No, you exclude the DCS folders. If the virus surface elsewhere you're good.

Sent from my SM-A536B using Tapatalk

[cfrag]

32 minutes ago, KevinAu said:

So…then this is not dcs’ problem and it’s just left up to each of us individually to just tell our microsoft defender or whatever antivirus to ‘ignore’ this find? Is that the consensus?

Hardly. And even if it was, any professional company with a competent, client-focused business would strive to work with the AV DB to make sure that their products are on the whitelist with discriminatory fingerprints. I'm sure that ED and their partners are professionals. They'll know how to handle this correctly.

[draconus]

1 hour ago, KevinAu said:

And also, I just want to make sure that there was indeed another update since the one posted in the changelog on 6/5/24?

The last update was that day:

What another one you talk about?

[KevinAu]

My dcs had already been updated to the 6/5/24 update last week, with the kiowa warrior availability. But on tuesday 6/11/24, when I started dcs, it showed another update was available. As usual, I selected to run the update. This one went extremely fast. But when dcs started afterwards, the problems started with the pua detections by windows defender. I indicated the build version displaying on my start wrapper in my first post on the previous page. So if 6/5 was really the latest update and truly nothing since, then somebody might be hijacking the dcs updater.

[BIGNEWY]

there was a small update with the same patch number, it was a small change. The updater is fine. 

[KevinAu]

Ok thanks.

[maxTRX]

15 minutes ago, KevinAu said:

... So if 6/5 was really the latest update and truly nothing since, then somebody might be hijacking the dcs updater.

Hehe, I wouldn't doubt it.  The way this entire kaboodle is running...  

[draconus]

19 minutes ago, BIGNEWY said:

there was a small update with the same patch number, it was a small change. The updater is fine. 

Why no changelog?

[BIGNEWY]

11 minutes ago, draconus said:

Why no changelog?

it was literally a small folder change, if we put out a change log for it people would be say "why you putting out a change log for a folder change" 

[draconus]

13 minutes ago, BIGNEWY said:

it was literally a small folder change, if we put out a change log for it people would be say "why you putting out a change log for a folder change" 

Oh, I know, Jester folder, ok