New
#31
My method removes what is wrong fromt he logon process at Windows start. So surely it does fix the error message. There just should show something like "TuneUp Registry Defrag finished sucessfully" but since AVG doesnt let it to even start, the message returned is just wrong.
Repairing the disk may be an option, but that shouldnt be really a reasson to fix the problem. Scandisk just scan for corrupted files and tries to repair them, nothing to do at all with executing an app at Windows startup. Also, you dont need TuneUp Disk Doctor for that. Just go tou your computer, right click in your HDD, select tools and there select the scan option. Actually TuneUp doesnt have any dedicated tool to check the disks. TuneUp just uses the own Windows scandisk.
So usin scandisk may "fix" temporary the error message, but those invalid entries will still in the registry and in the worst of cases you can end being unable to start Windows for trying to acces to invalid files. So I recommend 100% my method because is really safe and harmless. I DO NOT recommend to unnistall either AVG and even less TuneUp till you have already fixed this problems and deleted the entries I wrote on my post.
The problem have been fixed already (I posted the solution above). I use AVG since 4 or 5 years ago. Installed in all Windows 7 computers of my home and my customers. Never had a problem before with it fortunately. Working perfectly and smooth in Windows 7 32 and 64 bits, Home Premium and Ultimate.
I was wondering if gmsmagic1 has got his computer fixed. I hope that is not bothersome to anyone. I might of missed gmsmagic1 post that everything is okay.
I know your method is safe and definitely right
Before I got that message i tried to do the tuneup registry defrag. If the defrag success, there will be the notification. but in my occasion there isn't.
After I do the tuneup disk doctor, the registry defrag success notification shown up.
I tried to use the Autoruns software and in the logon tab there is no RegistryDefrag Success Message entry. And also in the boot execute tab. Maybe because the registry defrag process already finished. And I think now the problem already fixed.
Thanks for sharing your method too, its better to have more than one method to fix this problem right?