JeremyNicoll

I successfully repeated the scan (1207668 files, about 48 minutes) later in the day.

Files sent.

WIn 8.1 64bit, EAM 2019.5.0.9476 I set up and started a custom scan, which would normally take about 45 minutes and scan about 1.2 M files. I wasn't watching the machine as it scanned; when I came back to it I found the scan screen saying the scan was complete, only 510 files examined, no report file available. I don't know how long that took, though presumably not very long. Couldn't see anything in event viewer. I'll PM the debug logs to @GT500

> When it updates ... I've never seen that.

Here (Win 8.1) such a file is shown as 0 bytes by File Explorer... but it's open to a2service, so I suppose what FE shows is misleading. Sysinternals says: C:\Windows\system32>handle -a \temp\tmp Nthandle v4.21 - Handle viewer Copyright (C) 1997-2018 Mark Russinovich Sysinternals - www.sysinternals.com a2service.exe pid: 9140 type: File 27E0: C:\Windows\Temp\tmp0000049d\tmp00000000 C:\Windows\system32> and dir also shows it's empty C:\Windows\system32>dir /s "c:\windows\temp\tmp*.*" Volume in drive C has no label. Volume Serial Number is F607-7930 Directory of c:\windows\temp 11/06/2019 20:48 <DIR> tmp0000049d 0 File(s) 0 bytes Directory of c:\windows\temp\tmp0000049d 11/06/2019 20:48 0 tmp00000000 1 File(s) 0 bytes Total Files Listed: 1 File(s) 0 bytes 1 Dir(s) 210,853,363,712 bytes free C:\Windows\system32> So... did something get unpacked into it,then removed, or what?

> Did it update when it ran? Not so far as I know. I always download the newest available version immediately before running that. It never asks if it can update or shows any sign of doing so. Should it?

I think you need to contact: [email protected]

> Perhaps I can send the debug logs ? Only if you had debug logging turned on before and during the problem. Most users do not ever have it on because it can slow EAM down. It also creates files which grow in size very fast... You can check - the place where you'd choose to turn it on is at Settings -> Advanced -> Debug Logging.

Yes. I've PMed you a link to that too. But note that it's been (a) scanned again ok, and (b) run ok, since then.

Links to files PMed.

Win 8.1 64bit, EAM 2019.5.0.9476 Every couple of weeks I run FRST64.exe, just so I have a set of its reports going back through time, for comparison with a current report, if I need it. Today, having downloaded that file, I used File Explorer's context menu to ask EAM to scan it. I have a 4 cpu, 8 core machine, and instead of getting a near-instant response, one cpu core went 100% busy - ie Process Hacker showed cpu at 12.5%. After a quick look at it in PH, and restarting PH under Admin auth, I dumped a2service. After doing that, EAM reported the scan complete. I've since scanned an innocuous text file and also FRST64.exe again, both without a2service going mad. I'll zip up the dump and debug logs and PM them to @GT500 .

Thanks!

> I suppose you could argue that it should be called Mon Emsisoft ... Or "Ma"? What gender is an "Emsisoft"? Maybe it would be more, umm, sympathetic (or do I mean sympathique?) to say "Ma". Or "Mes" if they're a plural entity?

Does Settings -> Advanced -> User-interface language say English or French? (I don't know why it might have changed, but at least you should be able to get French back.)

You said, and I asked: > I saw plenty in the forums of people losing data and wiping drives. Do you mean the forums here, or somewhere else? and you replied: "Forums here.". I read everything (in English) here, and I am amazed that you say "you saw plenty"... I have no recent recollection of anyone reporting this problem, at least not in the English part of the forum. How about the URLs for these "many" occurrences? Moreover, if there were lots of these, surely you saw that Emsisoft support would have been involved? So why go off on a rant by yourself; why not wait for help?