Quote from: t3hpwnographer on April 04, 2018, 02:56:38 PM

Quote from: Cookie.Monsters on April 04, 2018, 10:29:55 AM

Quote from: t3hpwnographer on April 03, 2018, 10:42:18 PM

Quote from: MagicSmoker on April 03, 2018, 10:20:54 AM

Quote from: ChekaZ on April 02, 2018, 10:52:03 PM

Quote from: MagicSmoker on April 02, 2018, 10:47:10 PM

Second is that the new wallet is tagged as a trojan by Windows Defender (Fuery.a!cl) but this is almost certainly a false positive (or, I should say, it better be) so this file needs to be excluded from scanning....

Thanks for explaining this with the Windows-Defender. - We have already improved the false-positives with virustotal, still WindowsDefender doesnt like it. - Virustotal shows 0/64.

As for Windows Defender, I have had to exclude all mining programs and most wallets from it over the last 2 months as every definition update seems to target mining more and more. The conspiracy theorist in me suspects this is because lots of mining rigs running Win10 don't bother activating it... Roll Eyes

I've never had an issue with Windows Defender and mining programs or wallets, and this TZC release didn't change that. Seems odd that it would vary from user to user Huh

Are you using Windows 7 or Windows 8.1/10? The Windows Defender in Windows 7 is not really an antivirus programme but a rather simple and not very effective anti-malware programme. If you are using Windows 10, are you sure you are using the latest version of Windows 10 and also whether you are using some other antivirus programme - an installation of almost any other antivirus programme will disable Windows Defender (which is good - one should not have two antivirus programmes running at the same time).

I'm running Windows 10 Home (legitimate and activated) with no other antivirus program. Defender is definitely active and I know it's up to date.

I've also used a computer that was running Win10 Pro and Webroot SecureAnywhere, but that only got rid of mining programs (though it ignored ccminer KlausT 8.15 for some reason).

OK, further options which might lead to this are:

1. The exact version of Windows 10 Home one is using (e.g., 1703, 1709). Even though Microsoft enforces Windows 10 version upgrades, these might fail to install - at the same time, the OS might still be getting all critical patches and, if this is the case, can be considered secure (for the time being). In almost any feature update of Windows 10, MS does some changes to the Windows Defender, for example:

https://docs.microsoft.com/en-us/windows/whats-new/whats-new-windows-10-version-1709

2. Status of cloud-delivered protection of Windows Defender.
3. Any setup folder exclusions. It is enough to do it once and anything in that folder will never be scanned / reported.