I'm running AVG 2014 (build 4592) on Windows 8.1 (with update 1) Professional.
It appears that the AVGIDSAgent service is timing out when attempting to shut down or restart the machine, and this causes the laptop to pause for about 30 seconds when shutting down. If I uninstall AVG the laptop behaves just fine.
The irritating thing is that I did not install the identity protection feature, just the anti-virus.
Is it possible to install AVG without the AVGIDSAgent service? Or if not, does anyone know how to stop AVGIDSAgent from affecting the machine shut down?
Try opening-up your firewall to enable both "inbound and outbound" access for avgidsagent.exe.
I previously had only allowed oubound access for avgidsagent.exe and experienced the same shutdown problem. As soon as I enabled both inbound and outbound, the shutdown problem was solved. That worked for me. Hope it works for you as well.
Try opening-up your firewall to enable both "inbound and outbound" access for avgidsagent.exe.
I previously had only allowed oubound access for avgidsagent.exe and experienced the same shutdown problem. As soon as I enabled both inbound and outbound, the shutdown problem was solved. That worked for me. Hope it works for you as well.
Cheers
This was selected as the best answer
Mark Gray
Hi Nicholas
Thanks for the solution, it worked; my shut down time has now shrunk to about 5 seconds.
At first I thought it had no effect until I realised that adding a program exception to the Windows Firewall only creates an inbound rule. Once the outbound rule was added it worked fine.
Hey, I apologize for ressurecting this old thread, but I am having the same issue as stated above and I tried the mentioned method to solve the slowdown, however it didn't work. I may have set up the in/out-bound rules incorrectly, as I am not all that knowledgeable about all this techstuff. How is the proper way to go about it? I am running Win10 by the way.
Well I'm not familiar with Windows 10, but assuming that it is similar to the process in Windows 8.1:
- Access Windows Control Panel (the standard desktop Control Panel) and select Windows Firewall - Click on "Advanced Settings" on the left hand side of the window - Right click on "Inbound Rules" and choose "New Rule.." - Select "Program" and "Next" - Use the "Browse" button to locate avgidsagent.exe (inside the AVG install folder) and "Next" - Select "Allow the Connection" and "Next" - Apply the rule to "Domain", "Private" and "Public" and "Next" - Give the rule a name. - Repeat the above process for "Outbound Rules".
You should find 2 new rules added for both outbound and inbound; one for the TCP protocol and one for the UDP protocol.
That's all I did, and it fixed the issue (When I upgraded to a newer version of AVG I had to delete the old rules and add them back again, because AVG had changed the path of the executables).
I experienced the same issue a while ago.
Try opening-up your firewall to enable both "inbound and outbound" access for avgidsagent.exe.
I previously had only allowed oubound access for avgidsagent.exe and experienced the same shutdown problem. As soon as I enabled both inbound and outbound, the shutdown problem was solved. That worked for me. Hope it works for you as well.
Cheers
All Answers
I experienced the same issue a while ago.
Try opening-up your firewall to enable both "inbound and outbound" access for avgidsagent.exe.
I previously had only allowed oubound access for avgidsagent.exe and experienced the same shutdown problem. As soon as I enabled both inbound and outbound, the shutdown problem was solved. That worked for me. Hope it works for you as well.
Cheers
Thanks for the solution, it worked; my shut down time has now shrunk to about 5 seconds.
At first I thought it had no effect until I realised that adding a program exception to the Windows Firewall only creates an inbound rule. Once the outbound rule was added it worked fine.
Cheers
Mark
I apologize for ressurecting this old thread, but I am having the same issue as stated above and I tried the mentioned method to solve the slowdown, however it didn't work.
I may have set up the in/out-bound rules incorrectly, as I am not all that knowledgeable about all this techstuff. How is the proper way to go about it?
I am running Win10 by the way.
- Access Windows Control Panel (the standard desktop Control Panel) and select Windows Firewall
- Click on "Advanced Settings" on the left hand side of the window
- Right click on "Inbound Rules" and choose "New Rule.."
- Select "Program" and "Next"
- Use the "Browse" button to locate avgidsagent.exe (inside the AVG install folder) and "Next"
- Select "Allow the Connection" and "Next"
- Apply the rule to "Domain", "Private" and "Public" and "Next"
- Give the rule a name.
- Repeat the above process for "Outbound Rules".
You should find 2 new rules added for both outbound and inbound; one for the TCP protocol and one for the UDP protocol.
That's all I did, and it fixed the issue (When I upgraded to a newer version of AVG I had to delete the old rules and add them back again, because AVG had changed the path of the executables).
Cheers
Mark