Did this work for you?
@Nesivos: Sorry … no!
I bow to Dr. Zyndstoff. I was looking for something totally systemic and evasive when the obvious remedy is right in my eye. Bravo!
Now I feel stupid. Getting upset at nothing.
Thank you EVERYONE!!! ALL you guys that helped me and offered solutions, are better than TS. Bravo!!
I read your words as “Setting that one option worked for me, problem gone”.
Is that so?
If so: glad we could help.
P.S. what is “…are better the TS”???
Yes, Professor Zyndstoff : Your recommendation was my solution. I didn’t even think to go there. As we agreed, Avast! was working, why troubleshoot.
Thank YOU!!
Oh! sorry, TS = Avast! Technical Support LV2
So, it works when you delay Avast services start? I really have hard time reading your posts.
P.S. If so, it still suggests some kind of conflict with something at startup.
@madmacs: would you then kindly proceed to your first post, click “modify” and add “[RESOLVED]” at the beginning of the thread title.
Thx.
@doctor:
Well, yes, you are right. I think it’s caused by a special combo of programs and services running on the pc, that need more time to startup with sp1 so something that is vital for avast is delayed in that process. Would be great if this was investigated a little more, maybe madmacs could provide more info about his machine / services / programs / hardware etc. as requested by the devs?
Just a proposal…
Could be the conflict was caused if Avast is not loading last but is configured to do a boot scan.
I wonder what and how many programs madmax is running at startup ???
It is best to keep the number of startup programs to a minimum.
Outside of Toshiba Drivers and their peripheral programs about 6 programs are loaded at startup. The rest are system processes.
.6-8 Toshiba required programs (for Toshiba Qosmio x505 i7) + Bluetooth
.Skype
.Rockettime
.HP Digital Imaging monitor
.Logitech Performace MX Mouse battery monitor
.Adobe Bridge
…That’s it at startup.
Addendum: Actually a lot more is being loaded in the background. I did a HiJackThis trace and there are quite a few processes firing off.
I’m one of the others with the problem. Your work around helped me also. Clicking the option to load Avast services after all others keeps the problem from occurring. Thanks for taking the time to think on it. However, I would not call this resolved. More of a work around. It is not the most secure feeling knowing that Avast protection waits to kick in after all of the other services.
Maybe it is more a workaround than a solution, maybe. However, there will always be services that start before Avast kicks in, even if this option is not selected. There is always a “gap” if you want to call it that. I don’t really think that this option poses a notably higher thread to the system.
I believe there are tools out there to edit the startup sequence and it’s timing - maybe that can be a solution also, but since I never encountered such problems I never used any of those and I’m not familiar with that.
Just a thought.
Nice that fixed my problem as well, thanks for all the help guys, and a big f u to all the evanglists that told us “it works fine on my system”. Like that is constructive…
Well your comment is hardly constructive; can’t you just be happy that the problem for you is resolved.
-1 
Thank for all the input…
Well … I tried rearranging some of the start-up sequences of the services. I have been trying for a few days, in trial-and-error,… mostly errors. You may be able to select the order of the start-up, but you cannot determine how fast the start-up of a particular service occurs. A lot of services have dependencies and those dependencies have dependencies. I used information from a the boot log as a starting point. No Luck. I played the best I can. I have an SSD. In one very poor configuration, a boot of about 4 minutes resulted. It usually take 30 sec. Good thing I made registry backups.
Originally, the Boot Log was not able to help determine the problem because Avast! did start, though only annoyingly restricted. So I did not see conflict or dependency errors.
I’m still wondering and looking.
Well, but it still works with the original sequence and the option “Start Avast after other services” enabled?
If so, maybe just leave it that way. Digging very much deeper would require a dev to step in here and guide us through the process, as I am not savvy enough to aid more than what I contributed already.
Agreed… You did very well, sir … I am happy you came to my thread… Thank you.
It was my pleasure and I’m glad I could help. And thanks for the “sir”, but that is something not needed at all. :
Have fun!