I noticed this on a laptop (XP Pro) which has been running excruciatingly slowly, mainly due to a lack of memory, which I have now corrected. I have not seen it on two desktops, one running XP Home, and one W2000.
What seems to happen during boot (from the Event Log) is that numerous attempts to start ashwebsv occur, but ashwebsv does not come up fast enough, so the start is considered failed, and another start is attempted. I’m guessing this goes on until one copy gets running, but this leaves multiple started ashwebsv processes running. I have seen as many as 20 or so in Task Manager. When the system finishes booting(10, 15 or 20 minutes!), the extra processes gradually disappear and we end up with just one, as it should be.
This does not seem to happen with any other of the avast processes, just ashwebsv.
Since I’m not familiar with Windows process start mechanism, I don’t know what avast can do – perhaps avast could tell Windows to wait longer for the ashwebsv to come up? Perhaps ashwebsv could report back that is running sooner? Or is this just one of those things…