It seems some recent OpenMSX builds from https://openmsx.fixato.net/ are detected by Windows Defender as
"Trojan:Win32/Detplock".
I'm assuming it's a false positive, but the official release or earlier builds are not detected as such.
Just to let you know.
I've manually scanned some of the latest x86 and x64 windows builds from my site with both ESET NOD32 and Windows Defender for Windows 7 with its latest definitions, and neither found any threats.
Can you link specific downloads that are being flagged as threats, and tell us which version of Windows and Defender (should be under About Defender in the '?' dropdown menu?) you are using?
I've tested it with
Clientversion: 6.1.7600.16385
Engine version: 1.1.16800.2
Anti-spyware definitions: 1.311.4.0
the virtual machine that builds openMSX is pretty much a headless setup which only purpose it is to build openMSX. As a precaution I have installed McAfee (Intel) antivirus (legit paid copy). I'm running a full scan of the system. Stinger Antivirus came back as negative.
You guys probably have a personal/dev environment for building OpenMSX from source code. Why not building the executable in such secondary environments and comparing the binary with the "official" build?
I have been building openMSX for Windows myself since the build for openMSX.dev was behind a while back but I did not get any detection by Windows Defender, I will run a manual scan and compare my build to the download as well...
My build 661 passes a manual scan whilst the download of the 661 zip from openmsx.dev is blocked on my machine. I build on Windows using Ubuntu via WSL (Windows Subsystem for Linux). I installed the Ubuntu app from the Microsoft Store.
Then inside that Ubuntu I installed the required packages for building (tcl is needed because the openMSX build runs a tclsh command but can't run it from what it just build under the active environment):
sudo apt install mingw-w64 gcc make tcl
You have to tell mingw-w64 to use possix threads by running these 4 commands:
sudo update-alternatives --config i686-w64-mingw32-gcc
sudo update-alternatives --config i686-w64-mingw32-g++
sudo update-alternatives --config x86_64-w64-mingw32-gcc
sudo update-alternatives --config x86_64-w64-mingw32-g++
Choose option 1 for each...
My build command is then:
make OPENMSX_TARGET_CPU=x86_64 OPENMSX_TARGET_OS=mingw-w64 OPENMSX_FLAVOUR=opt staticbindist
Finally to 'install' the build:
cp -RvP derived/x86_64-mingw-w64-opt-3rd/bindist/install/* /mnt/c/Program\ Files/openMSX.dev/
Well you mentioned you use McAfee, which is of course different from Windows Defender. Do you build with Visual Studio? I suspect it might add some info that triggers Windows Defender, info that is not in the mingw build.
