Jump to content

In depth scan question


DinGo
 Share

Recommended Posts

Running NOD32 AV 8.0.301.0

If I run an In Depth Scan not as Administrator I get a list of files in the log with an error opening message. However if I run the same scan as Administrator then nothing shows up in the scan log.

When using version 7 of NOD32 I used to get these entries in the scan log even when running it as Administrator.

 

Is this a bug in version 8 or was version 7 incorrect.

Link to comment
Share on other sites

This is normal and we already had many topics about it:

https://forum.eset.com/topic/3055-useless-scan-info-shall-not-be-display-in-the-scan-log/

https://forum.eset.com/topic/3215-eset-error-opening-files-sorry-if-re-hash/

https://forum.eset.com/topic/3244-no-scan-as-administrator-option-custom-scan/

 

As a conclusion you can read this kb article:
Blue "error opening" notifications in Computer scan log

 

And if you really want to say that there would be some differences between v7 and v8 according these messages, then please provide us with more details like what files couldn't be open or some screenshots.

Link to comment
Share on other sites

Thanks for the reply rugk and I've had a read of the links.

However I'm not about to uninstall v8 and replace with v7 to do screenshots.

 

The most I can say is that running as administrator on v7 I got a lot of blue entries in the scan log, in v8 I get none.

 

It's not a big deal I just wondered what had changed to cause this.

Link to comment
Share on other sites

The most I can say is that running as administrator on v7 I got a lot of blue entries in the scan log, in v8 I get none.

That doesn't sounds bad at the moment.

 

However I'm not about to uninstall v8 and replace with v7 to do screenshots.

What exactly is the problem?

Here is an explanation how to uninstall.

If it really doesn't work you can even use a special Uninstaller from Safe Mode.

Link to comment
Share on other sites

I haven't got a problem with uninstalling as I've done it many times in the past. It's just not necessary to post a couple of screenshots with one showing a blank scan log and the other showing blue entries in the log.

It isn't something that bothers me too much, I was purely interested in why it was happening as I hadn't noticed with any previous version of NOD32, I've been using it since version 3.

Link to comment
Share on other sites

I haven't got a problem with uninstalling as I've done it many times in the past. It's just not necessary to post a couple of screenshots with one showing a blank scan log and the other showing blue entries in the log.

It isn't something that bothers me too much, I was purely interested in why it was happening as I hadn't noticed with any previous version of NOD32, I've been using it since version 3.

Yes IMO it isn't necessary to uninstall it too.

 

So I read your post again think your problem is not that you see the blue messages, but that you don't see them anymore in v8. Are I'm right?

So if this is the case then I don't know whether this is a problem, by design or you just can open all objects now.

I can only say that I see in almost every case these messages.

 

So to troubleshoot if this is really a problem:

  1. Have you tried to scan the boot sector. In many cases there is something that cannot be opend.
  2. Have you checked all your logging settings and you're ThreatSense settings?
  3. Do you know how to change the permission for a file? If so create a file or dir where you disallow the access for all users and especially for the user "SYSTEM". (If you are the owner of the file you can give yourself the permissions later again)

    This file should now be not possible to scan. Now try to scan the file and look whether you see this messages.

  4. If you want to see more messages (about files scanned etc.) you can activate the option to log all objects in the ThreatSense settings. For instructions read this kb article. The article describes a solution for another problem, but in step 6 there is the option I mean.
Link to comment
Share on other sites

 

I haven't got a problem with uninstalling as I've done it many times in the past. It's just not necessary to post a couple of screenshots with one showing a blank scan log and the other showing blue entries in the log.

It isn't something that bothers me too much, I was purely interested in why it was happening as I hadn't noticed with any previous version of NOD32, I've been using it since version 3.

Yes IMO it isn't necessary to uninstall it too.

 

So I read your post again think your problem is not that you see the blue messages, but that you don't see them anymore in v8. Are I'm right?

So if this is the case then I don't know whether this is a problem, by design or you just can open all objects now.

I can only say that I see in almost every case these messages.

 

So to troubleshoot if this is really a problem:

  1. Have you tried to scan the boot sector. In many cases there is something that cannot be opend.
  2. Have you checked all your logging settings and you're ThreatSense settings?
  3. Do you know how to change the permission for a file? If so create a file or dir where you disallow the access for all users and especially for the user "SYSTEM". (If you are the owner of the file you can give yourself the permissions later again)

    This file should now be not possible to scan. Now try to scan the file and look whether you see this messages.

  4. If you want to see more messages (about files scanned etc.) you can activate the option to log all objects in the ThreatSense settings. For instructions read this kb article. The article describes a solution for another problem, but in step 6 there is the option I mean.

 

Yes that's correct. My problem is that in V7 I saw the blue messages when I scanned as Administrator and not Administrator.

 

In v8 I see blue messages if I scan as not Administrator but no blue messages if I do scan as Administrator.

 

Could be that it's working correctly in v8 and locked files are being scanned  when running as Administrator therefore no blue entries.

When I run a manual scan I run an in depth custom scan on everything, every fixed drive including memory and boot sector.

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...