Jump to content

Unknown Running Processes Tool Entry


Recommended Posts

Hi,

I just re-installed Windows 10 and ESET IS (latest) and decided to take a quick look at the Running Processes Tool. I noticed an unknown item called "system", is this normal? I don't recall seeing it before.

eset-scrn-01.PNG.5774c0b53ea78c53fc04560a5a5391d6.PNG

Link to comment
Share on other sites

I have noticed this new entry for the OS kernel as well, in particular that it has a question mark as risk level and that  'Time of discovery' is 'Unavailable'.

I've asked support nearly two weeks ago what the question mark means, as it is not documented (!), and been told that in this case the (unknown) risk level is nothing to worry about, - which worries me!

I've asked how long it will take before this status is updated and been told that; "...from their wording, it appears it’ll remain marked as ‘unavailable’ until an updated build is released to fix the way it identifies theses processes".

When will a fuller explanation within Eset Smart Security be available for this question mark status?

Is it likely that status will be upgraded to a green tick-mark?

TIA

ESET Smart ver. 10.1.210.0

Link to comment
Share on other sites

  • Administrators

We will consider hiding the system process from the list as its reputation cannot be obviously determined.

The blue icon with a question mark means that no cloud information about the process could be determined and should not normally be displayed for other processes than system.

Link to comment
Share on other sites

 

1 hour ago, Marcos said:

We will consider hiding the system process from the list as its reputation cannot be obviously determined.

The blue icon with a question mark means that no cloud information about the process could be determined and should not normally be displayed for other processes than system.

Thank you for the answer.

Meanwhile, somebody should hastily update the 'help' information. That would have saved me time waiting for support to reply with an ambiguous answer as to what it (question mark and time of discovery) meant. I could of course just have submitted an infection report.......though that would obviously still have left me at the same, diminished, level of confidence with regard to eset smart.

I can guess at what you mean by "..reputation cannot be obviously determined". It is also a bit ambiguous, IMO.

Yes, it is hard (impossible) for eset to ascertain whether MS is 'good' or 'bad' with their OS and to analyse all their code. Though I thought that you (eset) had some insight that would warrant better than just an undocumented question mark.

Thanks.

Link to comment
Share on other sites

FYI in regards to "system."

The process is actually ntoskrnl.exe which is the OS kernel process that controls everything in Windows. As such, no one is allowed access to it including Eset.

Link to comment
Share on other sites

Thank you itman.

And yes, I am aware of that, hence my original mention "...I have noticed this new entry for the OS kernel ...".

I'll take the opportunity to appeal to eset again that; when suddenly the kernel appears in the eset tool, with a question mark and no further info, then one has to question it rather than assume 'all is probably in safe (eset) hands...'. Documentation is often as important as the actual product.

 

Regards

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...