September 2, 2010
Here
I am human
August 9, 2011
Hey FD - You certainly seem to be having your fair share of problems with Avast of late.
[quote:1llu4dec]if it
September 2, 2010
Hi Jim,
No 3rd party firewall, just Win firewall - this machine is behind a router with firewall enabled and other strict security settings.
Other security app running in real time is only WinPatrol Pro (it's a quite old machine, so I run it light), but I have it like for ever, i.e. not a recent addition.
What next?
P.S.
[quote:38cht2r6]You certainly seem to be having your fair share of problems with Avast of late. [/quote:38cht2r6]
Rubbing salt in my wounds?
I am human
August 9, 2011
Just searched for aswMon2 on my Win7 system and the only file found was [b:3dzp039d]aswMon2.sys[/b:3dzp039d] which is located in: C:Program FilesAlwil SoftwareAvastSetupINF
Perhaps that is the problem; that file should actually be in the Avast Program Files folder??
September 2, 2010
Hi Jim,
[quote:2xvg0j3o]that file should actually be in the Avast Program Files folder??[/quote:2xvg0j3o]
I didn't notice if aswMon2.sys was in Avast's folder and I don't know if on Win XP it should also be in there, it must definetely be in C:WINDOWSsystem32drivers.
Anyway, problem solved. How? No idea. Two things preceded my latest (& successful) installation of Avast:
1. Started my machine as usual today. Then tried to clean boot. Upon restart, Windows said that there has been a significant change in hardware since Windows was first activated (amazing how replacing your CD-RW drive with a DVD-RW drive is perceived as significant change in hardware five months after the replacement took place ) and needs to be reactivated. I did and Windows was happy.
2. I turned the "Windows Time" service on - maybe that's what triggered the reactivation thingy.
Then attempted to reinstall Avast (in normal mode) and to my surprise all went and is now well .
Cheers
I am human
August 9, 2011
Hey FD,
[quote:38wypsgm]I didn't notice if aswMon2.sys was in Avast's folder and I don't know if on Win XP it should also be in there, it must definetely be in C:WINDOWSsystem32drivers.[/quote:38wypsgm]
Hmmm, well I don't have a copy of aswMon2.sys in System 32/Drivers folder and my Avast works perfectly.
System 32/Drivers folder contains the following asw files: aswFsBlk.sys, aswMonFlt.sys, aswRdr.sys, aswSnx.sys, aswSP.sys, aswTdi.sys.....definitely no aswMon2.sys. As I said, the only copy of that particular file is in the Avast Program Files folder.
Maybe something to do with XP vs Win7, or 32-bit vs 64-bit.....but I wouldn't have thought so.
Oh well <shrug>....main thing is, all is working fine for you now.
Cheers....Jim
September 2, 2010
Hi Jim,
aswMon2.sys is strictly related to Win XP (avast only supports XP 32bit) - if you hover over it you'll see it in the description.
So, if you have Avast on a Win7 system, there is not need for that file to be in your system32/drivers folder for Avast to work properly.
Reason for the file being in AvastSetupINF is that the installer is the same for all systems and as far as I can tell, that folder just holds "info" related to setting Avast up.
Bottom line, as you said, everything's good and I'm !!
Cheers
I am human
1 Guest(s)
