Question ASXP Update 041619 recognized as malware

Chrix

Member
Hi,

am running Windows Defender on my machine, and upon installing & running the ASXP 041619 Open Beta update it will prevent ASXP to open.

"Recognized threat: Trojan.Win32/Fuery.C!cl"

No problems with official SP1.
 

WoDi

New member
Hi,

am running Windows Defender on my machine, and upon installing & running the ASXP 041619 Open Beta update it will prevent ASXP to open.

"Recognized threat: Trojan.Win32/Fuery.C!cl"
Here the same problem.


Dieter
 

maxam

Beta Team Member
It is a false positive, I have installed and run the update and I use Windows Defender with the latest definintions (update).

Best bet is to exclude ASXP from being scanned.
 

WoDi

New member
There's never been an alarm before.
Another virus scan did not produce a result.

Dieter
 

Chrix

Member
It is a false positive, I have installed and run the update and I use Windows Defender with the latest definintions (update).

Best bet is to exclude ASXP from being scanned.
Thanks! No problems today with the 041619 update. :)
 

nirgal76

New member
have the same problem with ASP P3D4 and windows defender. A false positive for Fuery malware is detected since i have updated to 7208 (andof course, AS crash at start up. Had to autorize this malware (putting all possible folder / executable / dll /process into exlusion list without success).
 

DLipsitz

New member
I've run into multiple instances where Windows Defender (Windows 10 Developer), one which results in AS being blocked from Internet access (Fuery malware), one that causes AS to crash outright on startup (Wader malware). As I general refuse to exclude entire directories (in the Wader case AS places it in the system's temp directory on the system drive, which I insist be scanned nightly), I instead allowed the files themselves, pending what it does to the overall operations of the systems. This allows AS to operate as it should and to access the Internet as well, without putting at risk the system drive. I did likewise with the other, which uses a directory in P3Dv4, to protect the simulator while allowing AS to operate as it should.

This has never occurred before today (though I haven't flown since installing the last update due to multiple real world events taking priority, rare events indeed, lol), this did NOT happen with the initial installation of the latest update to AS, but did with the flight for today. My system runs pre-release editions of almost everything from Microsoft, plus anything I'm testing within the sim (mostly panel instruments). Copies of suspected or flagged threats to the system are submitted to MS automatically by default, hopefully MS and HiFi will get together on this to resolve the issue. :concern::israel::typing::plane:
 
Top