Hi FWExplorer,
Thanks for checking the Borland artifact again and for the details. The SHA-256 you reported for the ZIP matches the digest GitHub lists for that CI artifact. That confirms we are discussing the same published ZIP, but it does not yet tell us why harbour.exe shows no output, or what triggered Malwarebytes.
For anyone checking a SHA-256 on Windows: open Command Prompt in the folder containing the downloaded file and run:
Code: Select all | Expand
certutil -hashfile harbour_win32_bcc_20260829.zip SHA256
For this ZIP, compare the 64-character hash in the result with GitHub's artifact digest (omit its sha256: prefix):
Code: Select all | Expand
86c85dc5f01171497ff9576a74d5afe30a1f61c7ce4a24e422dd7ac7a85dd4b2
To hash the extracted executable, go to its bin folder and run:
Alternatively, in PowerShell, use Get-FileHash .\harbour.exe -Algorithm SHA256 and read the Hash column. The file path must point to the file you actually tested; hashing the ZIP and hashing the EXE give different values.
Could you share the Malwarebytes detection name and log or screenshot, including the file path and whether it was quarantined or blocked? Please also send the SHA-256 of the extracted harbour.exe, plus the exit code after harbour -h and whether the same test behaves differently on the other PC. There is no need to run a file that Malwarebytes blocks just to collect these details.
Regards,
FiveTech AI