Hello!
After newest Avast update we ha an issue with Windows XP and Excel 2007 tmp files. After every changes, excel creates tmp file in working directory not int temp.
What could be the possible solution for this problem?
What exact business version of avast are you using ?
Same Problem here with XP and newest Avast Business Security
File is write protected until reboot or logoff
The problem is known and avast need to fix it.
On a note:
One should not use XP in a business environment.
It is a security risk.
As example, it only supports SHA1 hashes and more and more secure servers are abandoning it.
Thanks for such fast response.
We are using 17.2.2517, build 17.2.3419.0, virus definition version 170306-0.
Some business had to use Windows XP, because of legacy application, not every SME are rich enough to have budget to upgrade the application and don’t forget some of the application creator are no longer around, that why Avast still support Windows XP.
No, that is not the reason why avast still supports it.
Besides that, avast is not fully supporting XP for about 2 years.
I have the same problem, on machines with Windows XP SP3 and Avast for Business 17.2.2517 word, exel and pdf files saved or copied on network share cant be open by users. I need to reboot pc or unlock files on server. When i disable avast system shield before saving files everything is working fine.
The issue is known and avast need to come up with a fix.
Problems are still here with XP SP3 and Excel Files (Tmp, locked)
Microupdate to .59 doesn´t fix this …
Same issue with the Pro Version of AVAST …
I have a client with an even NEWER micro update. I think it ended in .61 or .62 or something like that. Have no idea what it is for.
I have installed .61, same Issue with Excel and XP
Contact business support: https://support.business.avast.com/hc/en-us/requests/new
Same problem with version 17.2.3419.64
XP SP3 with Office 2003 and Avast Business
All worked fine until the last Avast software update in the past days.
Now I need to reboot to unlock files.
Is there a release plan to solve the issue ?
Hi guys, this might help: https://www.avast.com/faq.php?article=AVKB268#idt_031
AVAST Software says:
We have reproduced the issue on Windows Server 2003 x86 and Windows XP x86. Micro-update is created and now is being tested. ETA for update is this week.
Thanks Infratech.
We have the micro update prepared, but the fix could affect other parts of avast, so more time will be needed for testing. The next consumer beta will contain this fix and couple days after, it will be released as a micro update. Sorry for inconvenience.
Is the micro-update included in the new release 17.3.2291 of consumer product?
Any update about this issue? Has the micro-update been delivered?