|
Posted by C J. on April 3, 2007, 6:14 pm
If you were Registered and logged in, you could reply and use other advanced thread options
problem was as outlined above, by Someone. I was instructed to remove
another file, which turned up being missing as well. For the moment AVG is
working normally.
> Thanks for your reply someone ... I've already tried what you've outlined.
> I'm glad it worked for you. :) I sent a 2nd email to Grisoft this
> morning, with 2 of the 3 files they'll need to examine.. For some reason
> 'avginet.log' wasn't found anywhere in All Users\AVG7data or for that
> matters elsewhere on the harddrive.
>
>>I had this same problem in February. I had to send AVG certain logging
>>files, and they determined that the problem was caused by non-standard
>>settings of Update Manager. To correct, do the following:
>>
>> Open AVG Control Center, double click "Update Manager" and choose the
>> following settings:
>>
>> (x)Update immediately.
>> (x)Require confirmation from user
>> ( )Restart immediately
>> ( )Complete at next computer restart
>>
>> Then clock on OK and delete update temp files. Again right click on
>> "Update Manager" and choose "Settings." Select the last "Advanced" tab
>> and click "Delete update temp files."
>>
>> If this does not work, navigate to program folder of AVG Antivirus; run
>> avgdiag.exe file; click "Next"; tick all items from the menu and click
>> "Next." Then enter your email address and answer the related questions.
>>
>>
>>> Hi all...
>>>
>>> I'm waiting to hear back from Grisoft about this, but in the meantime, I
>>> thought I would also post here and see if anyonelse using AVG 7.5 is
>>> having the same or a similar thing going on.
>>>
>>> As recently, as this week - after completing daily scheduled updates -
>>> Update Manager is now requiring a reboot in order to "complete
>>> installation" In the time I'd had AVG, I've never seen this happen.
>>>
>>> An inspection of the Event Log in Admin Tools seems to verify AvgUpdSvc
>>> starting normally, but its also noting a "FinishUpdate returns 8004020f
>>> " item - for the last 4 days. Going back further in the Applications
>>> log to the beginning of the month, Same items show, with normal
>>> termination of Update Manager with no reboot.
>>>
>>> I'm thinking a recent Priority update might of failed and in the process
>>> of scanning for new updates, its also detecting this update hasn't
>>> completed thus returning a " faulty update manager state " balloon in
>>> the taskbar.
>>>
>>>
>>>
>>
>>
>
>
| 
XML site map