Hi major28,
Again, very odd - this did not happen when I applied the most recent definitions update. Did you disable Avast’s auto-protection module then copy all patched files to both directories as indicated in patch instructions? In any event, I would just try again, it does work…
DS
The fix is here: http://public.avast.com/~kurtin/patches/
Use it…!! 
Yes, did the patch in accordance with the instructions.
Reapplied it again…and it looks like it stayed ok after a shutdown/startup.
I am sure it was applied correctly before also…was fine for a couple of days.
I don’t think I am the only one with the issue, as I believe I read that another person also had it revert back after an update, so we’ll monotor it and I’ll post if it happens again.
Glad to hear it worked on reapplication at least! Not sure what to say otherwise, as I say the only potential difference I can think of is that I renamed instead of overwriting… Odd.
DS
Ditto – WinXP SP3
The latest program update to Avast Free also broke my Ghost 12 – the service is apparently blocked from starting by Avast.
Use the patch: http://public.avast.com/~kurtin/patches/
Thanks for the info on the patch. My copy of Retrospect Express 7.6.123 now seems to be running ‘normally’ and is in the middle of my first backup for a few weeks! 
Avast! 6.0.1125 upgrade also killed my System Mechanic Professional 10.5. Previous version of Avast! worked fine together. Now I’m getting “Invalid Floating Point Operation” error when I try to load SM and it tries to load continuously. Will Avast! 6.0.1203 update fix this issue?
Hi major28,
In regards to your previous post:
…I think I now have an explanation. As I’m sure you recall, my own experience was not the same in that when I updated my definitions, the patch kept working. That said, I recently scheduled a full boot-time scan on my machine. Once I did that, the patch stopped working and the problem returned. Recopying the files solved the issue. Bizarre behavior, but likely a result of the self-protection routines built in to Avast, I’m guessing - presumably it restores the original files during the boot-time scan… Anyway, just wanted to let you (and others) know, in case they ran into the same issue. I’m now wondering if perhaps any sort of scan of the directories in which the patched files reside would do the same. Anyway, let’s hope a more permanent fix emerges soon. Best wishes,
DS
Still having problems as it seems every update “breaks” the patch. If I continually re-install the patch after every update, then all works again. But REALLY??? This is getting ridiculous.
Just to add another voice to the chorus: Since upgrading avast! yesterday to 6.0.12, my Retrospect 7.0.5 is running riot, rendering our network server practically useless. Since there appears to be no solution in sight and rolling back avast! isn’t very practical, I guess it’s time to replace avast!..
Correction: Found the patch and can confirm that it appears to resolve the issue. I am surprised that avast continue to distribute the 6.0.1203 build. Why not replace with a patched 6.0.1204 image?
After several weeks of troublefree performance with Retrospect, something (possibly a virus definition update) broke it again today. Why this happens from time to time is mysterious. It reverts aswMon2.sys back to the 7/4/2011 date as opposed to the “patched” 7/18/2011 date. And, it only does this in the program directory…the \Windows\System32\drivers copy of the file remained intact.
Use the latest beta: http://forum.avast.com/index.php?topic=83583.0