Avast WEBforum

Business Products => Avast Business => Cloud Management Console & Clients => Topic started by: REDACTED on March 06, 2017, 09:21:41 AM

Title: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: REDACTED on March 06, 2017, 09:21:41 AM
The new Windows client 17.2.2517 cause problem with Excel File on share folder, so far this only happen on system with Windows XP, user cannot save any Excel file they open on the file server, once they close the Excel file, next time they open the same Excel file again, Excel will prompt the file is lock by the user, the Excel file also cannot be delete as well.
Title: Re: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: Eddy on March 06, 2017, 09:26:34 AM
Please (re)search before posting as there are already threads about this.

It is a know issue and avast knows about it.
Title: Re: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: REDACTED on March 07, 2017, 02:25:00 AM
I am 1 guy supporting 40 over user in a SME, do you thing I have all the time sitting here read every post..
Title: Re: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: Eddy on March 07, 2017, 02:28:33 AM
There is a reason why someone a long time ago developed a search option ;)

40 people to support is nothing.
I supported +/- 2500 on my own without a problem.
Title: Re: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: REDACTED on March 07, 2017, 06:54:38 AM
@Eddy would you be kind enough to provide a link to the thread which shows that it is a known issue?

I for one did search, and couldn't find any other threads specific to this problem, none that I felt were related and being addressed by Avast anyway.
Title: Re: Windows client 17.2.2517 issue with Excel file on share folder Windows XP
Post by: REDACTED on March 07, 2017, 01:16:44 PM
I think he is talking about this topic:

https://forum.avast.com/index.php?topic=198341.0

I have the same problem as you, but with word and pdf files too :(.