I recently updated to version 2015.10.2.2214. Immediately a DotNet app that uses XmlSerializer began to throw an exception: “The process cannot access the file ‘E:\Documents and Settings\UserKen\Local Settings\Temp\vvv3qzb1.dll’ because it is being used by another process.” (actual DLL name is different each time). This is for Windows XP only. It works on a Windows 7 x64 installation. Disabling File System Shield eliminates the exception. When a DotNet app instance first creates an XmlSerializer, code is dynamically compiled to a DLL, which is then immediately loaded by the app. I’m guessing the scanner opens the file denying sharing, which prevents the app from being able to open it.
Perform a clean installation of the latest avast version and see if the problem is still there.
If it is, report it to avast through the ticket system.
- Remove avast through control panel
- Run the uninstall tool
- Reboot
- Run CCleaner (both files and registry check)
- Reboot
- Install the latest version of avast
The problem is still there after remove/clean/reinstall.
Got any other security (related) software installed ? (or did you)
No. I have 2 XP systems and 3 Win7x64 systems. Both XP systems have the problem and the Win7x64 systems are OK. Do you need me to provide a sample application with the problem?
No, I’m not working for avast so sending me the application wouldn’t do much.
I heard that next week there will be a update for avast released.
I suggest to wait and see if the problem is solved in that one.