Unable to scan files on mapped network drive

Avast Free Antivirus / Premium Security
1

Whenever I try to scan a file on a mapped network drive (Samba share) from the Windows Explorer right-click menu → Scan (filename), I receive the following error:

“Some file could not be scanned”, and when I click on Show Results it shows the following error message in the Status column:
"Error: A specified logon session does not exist. It may already have been terminated (1312)

The same thing happens when I create custom scan within Avast and try to scan items on a mapped network drive. I’ve tried scanning different files/extensions. When I copy the file over to a local drive, I can scan these files without any problems.

The Windows Event Viewer shows no error messages, and also the Avast log files do not seem to contain any additional information.
Is there any specific Windows service that is required to be running for this functionality within Avast?

avast! free Program version: 11.1.2241 (only File Shield active)
running on Windows 10 x64 version 1511 (build 10586.11)

2

does this help? https://www.youtube.com/watch?v=6qpVmefYI7U

3

What path are you scanning - UNC or do you have that mapped to a drive letter?

4

Thanks for the prompt reply.

Hm, now that’s interesting.

  • When I create a custom scan and choose the Scan Area “Interactive selection”, start the scan and select for example my D-drive (network mapped drive), it will fail with the above mentioned error
  • When I create a custom scan and manually add “\COMPUTERNAME\SHARENAME” (which is the same location as this D-drive) and start the scan, it runs without any issues!

So, is this a bug within Avast or is the free version of Avast not capable of scanning mapped network drives?
I can actually not imagine the error I receive is normal behaviour. IIRC it has worked correctly in the past (even from right-click → Scan), so it could be related to the Windows TH2 updated build.

Can anyone try to reproduce this error?

--------EDIT
@ igor: so UNC path works, but I can not scan a mapped network drive letter.

5

I believe the problem is that the mapping is valid for your account only; the scanning service (which runs under the SYSTEM account) doesn’t know about that - it doesn’t have any D: drive.
There are some attempts to convert the mapped drives to UNC before passing them to the scanning service… I’ll try to check why it should fail.

6

Thanks for the update. I have tried the method described on this page: http://woshub.com/how-to-access-mapped-network-drives-from-the-elevated-apps/

This will make the network shares available from elevated applications, and indeed allows me to access the shares from an elevated command prompt. Unfortunately Avast still throws me the same error when scanning files on a network share. Were you able to reproduce the problem?

7

@ igor: I’m just wondering if you have been able to investigate this issue any further. With the latest version of avast!, the issue still exists, same error message.

It would be really nice if we can fix this.