Excellent,
Qim — that ESET log confirms it:
- Scanned files:
417658
- Detected files:
0
- Cleaned files:
0
- Status: finished
So yes:
all clean now.
Why Defender did not find them
There are a few likely reasons.
1. They were inside Thunderbird mailbox files
Thunderbird stores many emails inside large mailbox files such as:
AndorraIN
Inbox
Trash
These are not normal separate files like:
invoice.pdf
Instead, the malicious PDF/email was buried inside a large mail container. Some antivirus engines inspect those containers more deeply than others.
2. Defender may detect the threat only when extracted or accessed
Defender often does very well with active threats and files being opened, downloaded, or executed.
But if the bad item is just sitting as an old attachment inside a Thunderbird mailbox archive, Defender may not unpack and inspect it in the same way ESET did.
3. Different antivirus engines have different signatures
ESET detected it as:
PDF/TrojanDownloader.Agent.BRZ trojan
Defender may not use the same name, same signature, or same detection logic. VirusTotal showed not all vendors detected it either, so this was not universally detected by every engine.
4. It was not active malware
This is important: the threat was
stored, not running.
It was an old malicious email attachment inside mail storage. Since you did not open it, it was more like a dangerous item in an archive than an active infection.
Bottom line
Defender missing it does
not necessarily mean Defender failed badly. It means ESET was better at detecting that particular old PDF threat inside Thunderbird mailbox storage.
What I would do now
- Keep Defender active.
- Keep Windows updated.
- Keep Thunderbird compacted occasionally.
- Do not keep old suspicious mail archives on the live PC unless needed.
- Keep the USB backup, but remember it may contain old infected mail if it is the original uncleaned copy.
You did very well. This was a complicated Thunderbird mailbox cleanup, and the final ESET result is exactly what we wanted.