Thanx a lot!!!
Oops, patch didn’t work at all.
-
the files contained in the patch zip file didn’t replace any files on \windows\system32\drivers) (the files aswndis2.sys and aswndis2.sys.sum didn’t exist in \windows\system32\drivers).
-
I see no change in behaviour: sf.bin continues opening and closing and the autosandbox options are completely missing from the additional protection tab).
In short: nothing changed.
too bad…
@jvidal, those patches are only for PerfectDisk/Norton Ghost/Retrospect apps – you have a problem with sf.bin
What can I do about that?
Uninstalling avast makes SUMO work ok again.
And SUMO worked fine with prev. versions of avast…
What can I do?
bye!
I’ll test it and let you know…
The patch did not fix anything on my WinXP system w.r.t.Retrospect.
The two files in the download did not exist anywhere on my system until I got them from the download.
The instructions say to disable avast’s self-protection. I wasn’t sure what that was referring to so I disabled all the real-time shields and the Self-defense module. None of these things is called “self-protection”.
–Larry
From the avastUI, Settings, Troubleshooting, there you can disable the self-defence module.
DavidR,
As I said in my post, that’s what I did (in addition to disabling the real-time shields).
Anyone getting a good result with the patch?
–Larry
Isn’t aswndis2 the Avast! firewall ? Is this applicable to the free version ?
Thanks, I’ll wait for the good news.
Strangely enough, though, everything seems fine under w7-64.
After updating to Avast!6.0.1203 I had the same symptoms:
after startup all activities were very very slow, if not impossible. After deleting Retrospect process from the list of active processes in the task manager, things worked normal.
Instead of going back to older Avast-Version I now removed RetrospectExpress HD (Ver. 2.5.108) and Avast! works fine after startup.
I will chose another backup software until this conflict is fixed in Avast!
Win XP SP3
Retrospect Ver 6.5
AVAST PAID 6.0.1.203
Same here.
Retrospect 6.5 will not load and I am unwilling to jump through all of the hoops suggested here.
I pay for AVAST and the most recent version is unacceptable.
AVAST you broke it, you need to fix it, if not I will be gone.
The patch referenced here (http://forum.avast.com/index.php?topic=81135.msg667922#msg667922) fixed my problem with Retrospect. Thanks for the quick response.
The posted patch fixed my Retrospect related problem, too.
Thanks!
Amazing! The avast folks changed the patch without telling us (at least I can’t see an announcement). The new download has different files in it (at least for the 32bit version for Retrospect). They don’t even have the same names. I think the instructions for installing the patch are different too. :-\
But the good news is that the updated patch worked for me (whereas the original patch didn’t).
Thanks for the updated patch!
–Larry
Hi all,
For the record, I can confirm that the most recent patch does work with Retrospect Express 7.6 under XP SP3. Very good to see this fixed, now I can stop doing backups manually with shields partially disabled…
DS
And for the record, I can confirm that the virus definition update 110723-0 breaks the patch.
Have not tried reinstalling the patch yet as I am trying to decide whether to go back again to the previous version or keep patching this thing over and over.
That’s a very odd result, especially given that the patch was for the actual code (aswMon2.sys), not the definitions - would be strange that definitions would be able to cause bad behavior in code. Not impossible, mind you, but very strange.
To test this, I installed the 110723-0 definitions on my system as well - again, WinXP SP3 with Retrospect Express 7.6.3.102 and Avast! Free 6.0.1203. I then cranked up Process Monitor and ran Retrospect, but saw no slowdown nor any of the activity associated with the slowdown that I reported before, so unfortunately I’m not able to reproduce this behavior. Has anything else changed with respect to your system, or did it only start doing this on reboot or something? Have not rebooted my system yet, to be fair… The only thing we might’ve done differently is that I did not overwrite the old aswMon2.sys in Avast!'s INF folder - rather, I renamed it aswMon2.sys.bak - don’t see why that should make a difference, though…
DS
Disabling shields in Avast! solved this problem for me. However the problem also existed for me with Diskeeper9, and disabling the shields in Avast! solved this problem, too. Both of these programs failed to load unless I disabled the Shields in Avast!
WinXP Home SP3 OS.
Nothing has changed.
An inspection of aswmon2.sys shows that the update reverted it back to a file date of 7/4/2011 wheras the patched file had a date of 7/18/2011.