Author Topic: Windows XP, Excel 2003 sharing violation  (Read 10156 times)

0 Members and 1 Guest are viewing this topic.

Offline brett45

  • Jr. Member
  • **
  • Posts: 21
Re: Windows XP, Excel 2003 sharing violation
« Reply #30 on: March 02, 2017, 01:18:39 PM »
Has anything been fixed in this regard? For me, the issues I posted in comment #23 still occur -- even with the new version build 17.2.3419.0 from Feb 27.

I am discussing this problem with the AVAST support team.

It seems they are unable to replicate the problem but I am working with them to help find a solution.

I will keep this thread updated with any information as and when it becomes available.

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
Re: Windows XP, Excel 2003 sharing violation
« Reply #31 on: March 02, 2017, 04:35:54 PM »
Have you tried adding an exclusion for Windows Network Shares?

Just the following one for File System Shield: \\*
The exclusion will match all servers, so if you want to narrow it down, just add the server name in the UNC path too: \\SERVERNAME\*

Offline brett45

  • Jr. Member
  • **
  • Posts: 21
Re: Windows XP, Excel 2003 sharing violation
« Reply #32 on: March 02, 2017, 04:44:31 PM »
Have you tried adding an exclusion for Windows Network Shares?

Just the following one for File System Shield: \\*
The exclusion will match all servers, so if you want to narrow it down, just add the server name in the UNC path too: \\SERVERNAME\*

Good idea!  8) That has worked as a temporary solution.  But AVAST still need to fix the bug.

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
Re: Windows XP, Excel 2003 sharing violation
« Reply #33 on: March 02, 2017, 05:54:33 PM »
Hope they do. ;)

If you want to be more secure, you can tick the checkbox under X.
That way, Avast will only scan the executable files you may try to run from the share.