Hi!
I have 23 computers on the same profile in Business Hub.
They all running the latest update of Windows 10 and are running on SSDs.
The issue has been affecting them for several months.
We have attempted reinstalling the OS from scratch and repairing Avast via the Repair App setting under Troubleshooting.
Their local File Indexing settings are the same.
Their TSRs are also the same with the only difference being that one computer has a Logitech Mouse & Keyboard Combo and the other computer has Razer components installed.
We have an Avast whitelisted software that is fully signed by a trusted source and we are running on all the computers to assist with Tech Support and Development.
Every morning, all the computers receive the exact same build created from our latest source code, although the location can vary from computer to computer.
We have the exact filenames and custom file extensions under all of the Exclusions in the assigned Policy.
On 2 of the computers with a 100% reproduction rate, we have a slowdown that can last 30 or more seconds during file access.
The slowdown appears to be related to accessing large files via ::CreateFile (filename, GENERIC_READ, FILE_SHARE_READ, NULL, OPEN_ALWAYS, 0, NULL);.
We found that if we disabled the flag in Avast for "Scan files when opening" appeared to address the issue and turned the access time from 30+ seconds to less than 1 ms.
The file type that is attempted to be accessed is in the Policy Exclusions list.
The remaining 21 computers are set up the same way, but do not experience the issue.
I'm hoping to leave "Scan files when opening" still active for these 2 computers instead of making additional Policies for these computers.
Here's an example of some of our File path Exclusions:
- *.pkg
- *.log
- *.ini
- *\*.sav
- *\smart.dat
- ?:\ProgramData\Package\*.*
Is there possibly a set of flags or a better way we can access the files on disk that is more acceptable to the Avast File Shield or are there other exclusions I can include?
Thanks so much for any assistance on this issue.
