4X for Ever
Posts:
Recents
.
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Changes
Home
Help
Search
Posts
Recents
Calendar
Staff List
Login
Register
Aurora 4x
»
C# Aurora
»
C# Installation
»
Windows Defender Marked v2.1.1 exe as a Trojan
« previous
next »
Reply
Send this topic
Print
Pages: [
1
]
Go Down
Author
Topic: Windows Defender Marked v2.1.1 exe as a Trojan (Read 1585 times)
0 Members and 1 Guest are viewing this topic.
M_Gargantua
(OP)
Gold Supporter
Leading Rate
M
Posts: 12
Thanked: 1 times
2023 Supporter : Donate for 2023
Gold Supporter : Support the forums with a Gold subscription
Windows Defender Marked v2.1.1 exe as a Trojan
«
on:
September 12, 2022, 01:09:57 PM »
Quote
When updating from v2. 1. 0 to v2. 1. 1 Windows Defender isolated Aurora. exe as "Trojan:Win32/Bearfoos. A!ml"
Maybe there is some memory hook that is similar?
Report to moderator
Logged
Erik L
Administrator
Admiral of the Fleet
Posts: 5633
Thanked: 347 times
Forum Admin
Discord Username: icehawke
2020 Supporter : Donate for 2020
2022 Supporter : Donate for 2022
Gold Supporter : Support the forums with a Gold subscription
2021 Supporter : Donate for 2021
Re: Windows Defender Marked v2.1.1 exe as a Trojan
«
Reply #1 on:
September 12, 2022, 03:16:09 PM »
Quote
Various AV tend to flag Aurora.exe randomly. McAfee does. Windows Defender does. Norton does.
Just whitelist it and let the AV whine
Report to moderator
Logged
Erik Luken
Arkayn Game Designs
Kashada
Petty Officer
K
Posts: 21
Thanked: 8 times
Re: Windows Defender Marked v2.1.1 exe as a Trojan
«
Reply #2 on:
September 12, 2022, 03:35:11 PM »
Quote
This happened to me the other day, after about a day it stopped flagging but I have no idea why.
Report to moderator
Logged
Reply
Send this topic
Print
Pages: [
1
]
Go Up
« previous
next »
Aurora 4x
»
C# Aurora
»
C# Installation
»
Windows Defender Marked v2.1.1 exe as a Trojan
It appears that you have not registered with
Aurora 4x
. To register, please click here...
There was an error while thanking
Thanking...