Disable resident shield. Restore the file from the virus vault. Create an exception for the file. Re-enable resident shield. OR This can be done with the network edition from the AVG admin server console and pushed to any clients configured to use it.
Steve Straw Network Services Manager Lynchburg College -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Isabelle Graham Sent: Tuesday, March 31, 2009 3:53 PM To: [email protected] Subject: Re: AVG latest sigs misidentify CCAAgentLauncher executable We've seen this here as well. Leaving the file in Virus Vault will prevent CCA from starting up automatically at boot (CCAAgentLauncher.exe is the file called by the link in the Startup folder of the Start menu), but does not seem to impact running in manually. -- Isabelle Graham Information Security American University Miller, Paul wrote: > Yes, we have the same problem here. > > > > Paul Miller > > Network Administrator > > Dominican University > > > > From: Cisco Clean Access Users and Administrators > [mailto:[email protected]] On Behalf Of Straw, Steve > Sent: Tuesday, March 31, 2009 2:30 PM > To: [email protected] > Subject: AVG latest sigs misidentify CCAAgentLauncher executable > > > > Anybody else seeing AVG v8.x and 7.5 misidentifying the file > CCAAgentLauncher.exe as a virus? It looks as though today's signature > updates to AVG have the Resident Shield program detecting this exe as a > threat. Restoring it from the virus vault and making an exception for > the file seem to be the work around of the moment. > > > > Steve Straw > > Network Services Manager > > Lynchburg College > > > >
