@ al2
Currently there is a beta version for the new avast 2016 version, 11.1.2236 and there are differences to 10.4.2233 the last regular release version of avast. I was trying to answer your question specifically, but the troubleshooting options for both versions above are essentially the same.
I was trying to be humorous about my seemingly ambiguous question not trying to criticize your answer
Yes running on an LUA is going to be more hassle for some functions and you have to jump through a number of hoops and that is why I went down the route of DropMyRights.
Thanks for your as usual detailed interesting informative reply. Sorry for my lack of clarity, Avast has NEVER been ANY problem EVER before wrt my LUA account since around five years(?) when I started using an LUA/Surun account as main. Its still working as it always has before this blip ( + loss of the "LU open avast setting"??) last time I was on XP earlier in the week. I learnt early on that "Drop my rights" (from the wise at
www.wilderssecurity.com) is a half way measure in my opinion the additional effort to
use LUA with NB 3rd party "Surun" - this makes ALL the difference in convenient LUA management - making convenient what is natively next to impossible, gives MUCH more security than in an admin account where the privilege is still built into the background ( plenty of detailed explanation about this on wilderssecurity) ONLY in an LUA are Admin rights partitioned + Software Restriction policy ( built into windows from XP onward) using the built in metadata of objects security policy - UAC is not as strong as this for example wrt malware attack. Its common for people who run LUA account(with 'Surun' of course) to not even run an AV but imo this is tempting fate + going against the theory of "
defence in depth"( is a security principle that a system should provide multiple layers of defence, in case one layer is ever breached. ) which leads me too;
I gave up on System Restore in XP many, many years ago as it was:
A. Not 100% reliable and often had unforeseen consequences.
B. It didn't cover everything, it isn't like a backup
My preferred option for a backup and recovery strategy is hard disk imaging software, which makes an exact copy of your Partition or Hard Disk.
Sure of course I image the partitioned OS ONLY ( + conventional back up of data too were imaging is redundant not the infinite changes an OS makes through time) very carefully, SR its not a back up + has never really been marketed as such but another "
layer of defence" does not have to be 100% relied upon but its been reliable enough to be a time saving convenience + even saving my bacon odd times :)7's SR is infinitely superior of course still
its better for me to have SR actively recording my main XP's process than NONE at all :-).
The later versions of avast are more tolerant of System Restores actions, but it is still wise to disable the avast self-defence module.
Putting the Avast program in a separate partition is easy with todays GUI/graphical intuition lead partition managers and from my own research/on my PC at least it neutralizes the Avast self-defence module (without disabling it) effect on XP RESTORE as srdiag.exe results show 'START of UNDO' action is no longer present with contents of all users/aplic data/avast folder as I posted yonks ago in the HUGE SR/Avast hosing thread here.
NB. In my msg I didn't mean to imply Avast support doesn't help XP users since, for example, they helped sort out mine when ( early this year(?)) a new edition of avast caused XP to freeze up not long after start up
