I have delayed replying until now in order confirm that the problem is indeed fixed, which it appears to be, as it has not now recurred in over a week and a half.
The reason that I suspected as the cause when I made my last post turned out not to be, and the problem persisted for two days following my last post. However, on the third day no warning occurred, and on checking I found that the AVG update had proceeded 'normally' on the machine in question, and further to that, the build-up of AVG files in variously 'random-named' sub-directories of C:\Windows\Temp that had occurred during the period when the problem had been happening had all been removed.
On checking for a possible reason why the problem had suddenly 'fixed itself' I could find nothing conclusive, except that the task defined in the Windows task scheduler that ran the AVG updater appeared to have been recreated (based on its creation date).
While the problem was occurring I had examined and recorded the settings of this task definition both by making notes and by taking screenshots. On comparing the settings of the old task definition (which was dated the day three weeks previoulsy when I had first installed AVG) and the new task definition with the creation date of the day theby then seven-day-old problem ceased to occur, I could find absilutely no difference in any of the settings, except the creation date of the task scheduler entry itself.
Gary, We are sorry to hear about the inconvenience caused. In order to assist you better, we have sent you an email instruction to get connected with our technical support team. Please follow those instructions to get in touch with them and you should be able to resolve your issue. Thank you.
Thanks again for your response Ranjani - I have been looking carefully through the AVG settings on the affected machine and I may have identified what is causing the problem, I will have to wait until tomorrow to see if it was actually the cause of the issue, if it was I will post the details here so that anyone else who encounters the same issue will have access to it.
I have delayed replying until now in order confirm that the problem is indeed fixed, which it appears to be, as it has not now recurred in over a week and a half.
The reason that I suspected as the cause when I made my last post turned out not to be, and the problem persisted for two days following my last post. However, on the third day no warning occurred, and on checking I found that the AVG update had proceeded 'normally' on the machine in question, and further to that, the build-up of AVG files in variously 'random-named' sub-directories of C:\Windows\Temp that had occurred during the period when the problem had been happening had all been removed.
On checking for a possible reason why the problem had suddenly 'fixed itself' I could find nothing conclusive, except that the task defined in the Windows task scheduler that ran the AVG updater appeared to have been recreated (based on its creation date).
While the problem was occurring I had examined and recorded the settings of this task definition both by making notes and by taking screenshots. On comparing the settings of the old task definition (which was dated the day three weeks previoulsy when I had first installed AVG) and the new task definition with the creation date of the day theby then seven-day-old problem ceased to occur, I could find absilutely no difference in any of the settings, except the creation date of the task scheduler entry itself.
and thanks for your prompt response. Unfortunately this email you sent to me asked for a remote connection to be established with AVG so that someone from AVG could access the machine. Unfortunately this is not an option as the machine in question contains highly confidential files and I cannot allow any access to anyone.
I need someone to tell me the likely causes of the problem and for me to attempt the fixes myself.
Gary, We can understand your hesitation to have remote assistance. Please note that this is a very secure connection and we stand for that. You will have the control over the session to revoke remote access and can view what is being done by our technician. We need to check and analyze the exact cause of this issue. The file which you are going to run is LogMeIn Rescue, it is a secure desktop remote tool through which we can securely access your computer and perform the necessary tasks to fix the issue. You can see their live session and chat with them. If you feel your privacy is being compromised, please feel free to revoke the remote desktop permission at any point of time by just clicking "X" mark in the right top corner of the chat window. Thank you!