Thanks again DavidR. I must be so thick - can’t see your logic.
(Sorry for long spiel…)
1. Around 13th May: New Avast programme update: I approve. It downloads, says to restart.
2. Power down. Restart on 14th. Windows XP fails, reboots. ‘Recover last good version’ fails. Safe mode: set restore point to 12th gets system up. Despite the dreaded System Restore, all seems to work fine.
3. Restart from now on is déja vu - something keeps confounding the System. Must restore-point back to the 12th each time.
4. Click Avast icon: 'In order to complete install or update of avast! av, computer must be restarted'. Yes, "boat has sailed" but that’s because I began the programme update process in step 1, not from "having done a system restore". I have no manual control over installing this Avast programme any more. Like Sisyphus forever rolling the boulder up the mountain but unable to park it, the process won’t stop.
5. Is, indeed, the new Avast programme the cause or some other?
6. If only I could cancel approval or stop the half-baked update zapping every restart, then I would know if Avast triggers the bug.
7. Yes, freezing programme level means 'nagged' every restart until bug solved (or a newer version likes my computer). Better than tedious restore-pointing that ends up the same - I continue using the old Avast.
8. If I reload the whole Avast as you say, surely there will be no difference from the current attempted programme update with its registry etc changes: restart will fail if Avast triggers the fault; but it will fail if it’s some other cause – which one?.
9. The only case I see for reloading Avast is strong suspicion it was bad before the update, and though it worked OK then, the update threw it in such chaos that it now prevents restart. This corruption would have happened before I did any system restores. Much more likely it’s the update changing some system file IMHO.
Please accept apologies for troubling you to set me right on this.