As I posted in another thread, I updated the Avast Free Program to Version 5.1.864 and had a problem with the Avast File Shield. When engaged this Shield blocked Explorer from accessing my Windows XP Pro SP3 32-bit Recycle Bin in all Accounts on my WinBook Laptop. When Explorer was blocked, Windows froze and had to be restarted with a hardware reset.
I removed Avast completely, and installed Avast 5.1.874 beta and the problem went away.
Since updating the program through the interface to 5.1.884, I can report that there have been no further issues. This is the version currently being offered through the Avast Interface.
Thanks for the swift action on this problematic update.
Hi RC Primak.
I wanted to ask if the "transient cache" was activated at the time of freezing of explorer. Yes?
Sorry about the long delay in replying, but I have not been following this Thread. My issue is resolved, and I saw no reason to continue the discussion.
I see from an earlier post that you thought you had a similar issue to mine. Even when the symptoms look similar, in Windows a more specific freeze involving only one Explorer function can mean something very different from a general Explorer freezing problem. My issue was (thankfully) very specific. And this is why I suspect the update had a bad parameter somewhere, or a bad path, and the File Shield was "protecting" the Recycle Bin from being changed by Windows Explorer. Hence my freezing issue. The next update seems to have completely solved my issue.
I do not know nor care what the Avast "Transient Cache" is, nor how it works.
I did do a complete Avast Uninstall and reinstall from the Avast interim update version .864 which froze on Windows Explorer when trying to open the Recycle Bin. This happened as I installed the .874 Build. And that was when my issue disappeared. There should have been no "Transient Cache" present after the first reboot, if there was even such content before that reboot. Still, before that clean reinstall, who knows?
Build .864 was in my experience, just a bad update. Period. The Avast staff have admitted as much in this Thread and others at this Forum.
Updating to the most recent Build (.884) completely solved the issue, and my update methods were identical for both Builds (.874 and .884). The Windows Recycle Bin issue has not recurred with the current (.884) Build. In conclusion, I would not expect that any "Transient Cache" should have anything whatsoever to do with my (.864) issue.
In any event, I am not going to downgrade just to try to reproduce this time-consuming and frustrating incident. I just want Avast to work. Which most of the time, it does.