+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Support (https://forums.dolphin-emu.org/Forum-support)
+--- Thread: DSPTool is being flagged by BitDefender (/Thread-dsptool-is-being-flagged-by-bitdefender)
DSPTool is being flagged by BitDefender - Drflash55 - 11-18-2022
When trying to use the automatic updater for the dev version of Dolphin from 5.0-17625 to 5.0-17887, BitDefender flags DSPTool as "Gen:Variant.Lazy.231870".
I can't seem to whitelist this because I have no idea where Dolphin temporarily stores files for updating the emulator. If I knew where this was, I could get BitDefender to ignore it without having to temporarily pause it so that this update can go through.
If I can get an answer to this, that'd be very helpful.
RE: DSPTool is being flagged by BitDefender - MayImilae - 11-19-2022
Sadly it is not unusual at this point for our updater (and some files being updated, like I'm assuming happened with DSPTool) to be flagged as a trojan. https://dolphin-emu.org/blog/2019/11/07/dolphin-progress-report-october-2019/#windows-defender-yelling-at-a-cloud-ai
Quote:I can't seem to whitelist this because I have no idea where Dolphin temporarily stores files for updating the emulator.
I don't know where that is exactly (I'd have to go code diving but I don't want to atm), but Dolphin keeps its files in the Global User Directory which on Windows is defaulted to [username]\Documents\Dolphin Emulator. That would be where you should start.
RE: DSPTool is being flagged by BitDefender - Drflash55 - 11-19-2022
(11-19-2022, 03:09 AM)MayImilae Wrote: I don't know where that is exactly... but Dolphin keeps its files in the Global User Directory which on Windows is defaulted to [username]\Documents\Dolphin Emulator. That would be where you should start.
Alright, I'll get BitDefender to add that folder as an exception and see if that'll work for future updates.
EDIT: Turns out it didn't work, but I was able to use a tool called "Process Monitor" to see where the updater was writing the files to, and my suspicion was correct. It was writing to the Temporary Local User directory, so I simply set BitDefender to ignore it (even though it's not really a great idea, but it'll stop it from complaining), and I solved the issue that way. Such an odd occurrence that this is only happening now when it never used to before.