Well a while ago I did a format on my system and made the move to a 64-bit OS (Vista Home Premium 64-bit to be specific) and I noticed a couple of interesting things upon installing avast! after a clean install and update. The main issue here is just as the title says where avast! doesn’t show up at all in Windows Defender’s Software Explorer for Startup entries even though it used to back in Vista 32-bit. Strangely enough it seems like some sort of compatibility issue since the entry for ashDisp.exe still shows up in other programs that have options to view the startup, like CCleaner. This is relatively minor I suppose but I do have a relevant issue that is a bit more concerning.
Basically avast! seemed to delay the startup procedure of windows by a significant amount, where instead of instantly proceeding from the “Welcome” page to the actual desktop it would stay there for a long period of time before finally doing so (which was not exhibited at all in Vista 32 bit). The interesting thing though is other than that avast! performs quite admirably on my 64 bit system making me guess that only the startup procedure seems to impacting it the most. That being said, if any testing or other information is needed, I’ll see what I can do.
avast! Settings / Troubleshooting / Delay loading of avast! services after other system services
Does it make any difference (regarding the startup time) if you check this option?
Well it seems that this issue is rather odd in how boot-up times are now varying from long to short—this could potentially just be an issue with Windows and how it loads things such as my older sound card which could potentially be adding to the problem here. I’ll try that out though if I notice this again, so thanks for the tip on how to approach this.
Also have a non-related bug to report that involves those black little error messages that pop up on the bottom right corner of the screen, where avast! says there was an error writing a registry value. I thought these were gone in the past few updates but it looks like it suddenly reappeared when performing a simple manual update.