Open Xaaali opened 5 months ago
This happens every time we update XIVLauncher. This is the reason we don't update it unless absolutely necessary. It's a false positive, either make exceptions or remove MalwareBytes entirely.
This happens every time we update XIVLauncher. This is the reason we don't update it unless absolutely necessary. It's a false positive, either make exceptions or remove MalwareBytes entirely.
Gotcha, Ill keep it in mind. Ive made the entire install folder as an exception.
This happens every time we update XIVLauncher. This is the reason we don't update it unless absolutely necessary. It's a false positive, either make exceptions or remove MalwareBytes entirely.
Gotcha, Ill keep it in mind. Ive made the entire install folder as an exception.
Funny thing is yesterday's release wasn't quarantined or anything like that, only started happening just now when i booted up. But yea, C:\Users\<Username>\AppData\Local\XIVLauncher
to the mbam allowlist will fix it.
Confirmed false positive on MBAM side, expect to be resolved soon. Can remove the allowlist exception whenever.
Edit: Looks like mbam has already whitelisted it
Update disclaimer
What did you do?
Tried booting XIVLauncher after recent patch, and now MalwareBytes is classifying XIVLauncher.exe as Malware, immediately quarantining on startup. Doing this with both versions 6.3.10, and the newest 6.3.16. Never happened before latest patch, now having to add all versions to MalwareBytes allow list.
Platform
Windows
Wine/Proton runner version
No response
Relevant log output
No response