Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: dreamineyez on March 24, 2010, 08:55:16 PM
-
Ever since I upgraded to Avast 5 the GUI Window loads every time I start my Windows XP computer. (On My notebook running Vista it never does this) I looked at MSConfig and also looked to make sure the /nogui is in the command line which it is. I figured /nogui would prevent it from opening at start-up but I guess it does not. Is there any way to fix this issue because It really slows down my computer when it starts up.
-
If you run regedit.exe and search for AvastUi.exe occurrences in the whole registry - do you find only the one autorun association you see in MSConfig, or are there more of them?
(you can ignore the avastlicfile associations)
-
Ever since I upgraded to Avast 5 the GUI Window loads every time I start my Windows XP computer. (On My notebook running Vista it never does this) I looked at MSConfig and also looked to make sure the /nogui is in the command line which it is. I figured /nogui would prevent it from opening at start-up but I guess it does not. Is there any way to fix this issue because It really slows down my computer when it starts up.
did u install as admin? do u use xp sp3?
if you see /nogui command with avast in the autostart section it should work.
could also be a double-install, faulty update/upgrade.
maybe also a de/reinstall could help.
asyn
-
yes I run XP Service Pack 3 and installed as admin. I have tried to uninstall I downloaded the avast uninstall utility from the website, tried uninstalling in Safe Mode and Regular, cleaned the registry and when I reinstalled the same thing keeps happening. Is there any fix for this?
I still see the /nogui in the command line but obviously isn't working
-
You didn't answer igor,
...do you find only the one autorun association you see in MSConfig, or are there more of them?
I think this is most likely where the answer lays...there was another thread somewhere that had someone with two entries, and this caused the behavior...
-
You didn't answer igor,
...do you find only the one autorun association you see in MSConfig, or are there more of them?
I think this is most likely where the answer lays...there was another thread somewhere that had someone with two entries, and this caused the behavior...
No there is 1 entry and only 1 entry in MSconfig. I see saw someone post about this problem so I am not the only one with this issue.
-
huh... :(
maybe u can try 2:
remove the /nogui entry
restart twice (see what happens!)
after that add the /nogui entry again
restart twice & hope...
last try would b 2 start the debugging protocol, but i'm not shure if this is logged there...???
sry, out of ideas if it doesn't help, since u did everything that could be done, imo.
good luck, :)
asyn
-
huh... :(
maybe u can try 2:
remove the /nogui entry
restart twice (see what happens!)
after that add the /nogui entry again
restart twice & hope...
last try would b 2 start the debugging protocol, but i'm not shure if this is logged there...???
sry, out of ideas if it doesn't help, since u did everything that could be done, imo.
good luck, :)
asyn
That didn't work either, I wonder if they will create a fix for this in an update or better uninstall and switch to a different anti-virus
-
That didn't work either, I wonder if they will create a fix for this in an update or better uninstall and switch to a different anti-virus
sorry 2 hear that. :(
still wonder why this behavior happens, since u r on same os... ???
maybe it's a conflict with one of your drivers?
asyn