It pretty much doesn't do any IO operations at all, only takes 1.6 MB of memory and not doing any CPU activity as far as I could observe. Same when doing scans. Is it something expected?
It pretty much doesn't do any IO operations at all, only takes 1.6 MB of memory and not doing any CPU activity as far as I could observe. Same when doing scans. Is it something expected?
Had just thought it was part of scanning engine(thus why it's sandboxed) of the Windows Defender, seemed strange why it's completely still. It takes about 40 MB of RAM at first after system boot. And event viewer shows some mitigation alerts. Thought it's kind of bug.