ICEknight

Thanks, any word if they’ll fix it so that the false positive won’t happen with previous and newer (monthly) versions?

I’ve reuploaded the latest unofficial 32 bit binaries here, since the file.io link has expired and I can’t edit posts here: https://rapidshare.io/Ts5/mame230_32bit.7z

@Wesly.Zhang You have all previous official releases in this link, including 64 and (old) 32 bit binaries: https://www.mamedev.org/oldrel.html

There’s no official 32 bit builds anymore. I’ve reuploaded it here: https://file.io/xLdLyXjKerAp

Yes, though I don’t think the others who reported this do.

@Wesly.Zhang @Flood and Flood's wife I got that false positive today (with the exe getting automatically quarantined after just opening the folder it was in), with the “mame230_32bit.7z” build which can be downloaded from here: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO It seems to have been randomly happening with certain builds for some time now, as can be read in this discussion from January, which also gives some hints on its possible reasons: https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=118317

@Flood and Flood's wife MAME’s latest official builds are always posted here: https://www.mamedev.org/release.html Though this false positive also affects any alternate builds made by others, using the publicly available source (being an open-source project).