Home Support

English

X

Select your language:

AVG Support Community

Share tips and solutions on AVG Products

Have a question?

Community topics

AVG Gurus

These community experts are here to help

  • (AB) Alan Binch
  • (BA) Borislav Angelov
  • (VB) Vladimir Bartl
  • (SK) Subhadeep Kanungo
  • (MS) Miloslav Serba
Mr AnonymousMr Anonymous 

“Managed By Your Organization” in Google Chrome after AVG Update

After updating AVG’s application and virus definitions two days ago, I immediately received the annoying message, “Managed By Your Organization” on Chrome Browser’s latest version 80.0.3987.162. I’m currently running AVG Virus Definition version 200403-0I and Application version 20.2.3116 build 20.2.5130.564. I assumed my Windows PC was infected with malware. However, after running a full scan with AVG and Malwarebytes at least three times over, no infections were reported. I tried what other people suggested online. First, I downloaded and ran the Automatic Google Policy Remover. Second, I manually deleted Google Policies in the Windows Registry. Third, I also uninstalled and re-installed Google Chrome twice. None of these methods worked. The annoying message “Managed By Your Organization” finally disappeared after I disabled AVG’s Web Shield and rebooted my PC. Since AVG and Avast share the same engine, it’s no surprise so many people are suddenly experiencing this problem. Within the last day, several complaints have been posted on Google Chrome forum about this problem. I’ve re-enabled AVG’s Web Shield and the problem has reappeared. Hopefully this will be fixed in the next update.
 
AvinashAvinash (Avast) 
Dear customer.
We regret the inconvenience caused.
Management is a feature that lets administrators control Chrome browser settings. If you use the Chrome browser on a workplace computer, your employer can set hundreds of policies that control how Chrome functions.
However, if you are seeing this on your personal computer, please follow the steps below to disable it.

1. Open Google Chrome web browser and type chrome://flags/ in addressbar and press Enter. It'll open the advanced configuration page.
2. Now type managed in the "Search flags" box.
3. To disable/remove the "Managed by your organization" message, select Disabled from the drop-down box.
4. Google Chrome will ask you to restart the browser. Click on "Relaunch now" button to restart Google Chrome.

Please let us know if the issue is resolved or not.
Mr AnonymousMr Anonymous
Thank you for your suggestion. However, I already tried that old solution prior to me posting my problem on the AVG Community Forum. It appears that Google no longer allows the user to disable “Managed by your Organization.” In earlier versions of Chrome it could be done by simply disabling “Show Managed UI for Managed Users.” Unfortunately, that is no longer the case. Any more suggestions would be greatly appreciated. Thanks
 
Dinesh KrishnanDinesh Krishnan (Avast)
Appreciate your efforts in notifying this to us. We'd like to check this with our next level of support. Once we receive the info from them, we'll write back to you. Thank you for your understanding in advance!
Mr AnonymousMr Anonymous
A solution to this problem was recently posted on the Avast website. Since AVG and Avast share the same engine, is it safe to completely disable “Enable QUIC/HTTP3 Scanning” to fix this problem in the Chrome browser. I will post below the link and the direct quote of the Avast Team.

I am the developer responsible for this side-effect and I am sorry for this experience. Let me explain, what we did in the version 20.2 that causes this message.

Background:
There is a network protocol currently in development called QUIC. As it is in the active development by Google and others, there are some versions of this protocol that we cannot check properly for malicious traffic.
Therefore, we decided to block these protocol versions and the way how we do it is using Chrome Policy setting (which is, according to Google, the preferred way to do it).

You can check the policy by visiting chrome://policy

Kind Regards,

Jindrich
 
 
“Hello friends,

in the uUpdate 568 we have updated the behavior of the "Quic scanning" checkbox in the WebShield settings (under core shields). If you disable QUIC, we are now removing the blocking policy immediately. You can go to chrome://policy in chrome and click "Reload policies" to update that without a browser restart.

In order for this to work, you need to be on 20.2.5130.568 or higher. (a reboot or two is the safest way to induce the update if you are not already on it)

We are still considering disabling QUIC blocking completely - in order to save you from the hassle of going into the settings and turning it off manually.

Cheers,
Lukas.

>https://forum.avast.com/index.php?topic=233117.15
>https://forum.avast.com/index.php?topic=233117.45 (https://forum.avast.com/index.php?topic=233117.45" style="color:blue; text-decoration:underline)
 
Santhosh PannerselvamSanthosh Pannerselvam (Avast)
We appreciate your efforts in notifying this to us.

We suggest you to disable QUIC/HTTP3 scanning in the Web shield. However, it isn't recommended.

Further, our senior team has sent you an email. Please send your queries to the same email.

Keep us posted.
Jim smithJim smith

Hi team,

I'd like to report a similar issue, I've also tried the chrome policy removed as well as the methods you have suggested here excluding the web shield options, I've run full scans and tried re-installing chrome and have had no success.

Is this still an issue? I'm currently on software version 20.3.3120 (build 20.3.5200.573)

Looking forward to your reply. 

AvinashAvinash (Avast) 
Jim, there is a network protocol currently in development called QUIC. As it is in the active development by Google and others, there are some versions of this protocol that we cannot check properly for malicious traffic.
Therefore, we decided to block these protocol versions and the way how we do it is using Chrome Policy setting (which is, according to Google, the preferred way to do it).
You can check the policy by visiting chrome://policy

We plan to change the behavior of the QUIC scanning. For the period of time until a full blown scanning is released in AVG, we will continue to provide security of the connections by blocking QUIC in google by the policy (the most transparent way, as opposed to other mechanisms that are available, like simply blocking QUIC traffic and let the browser handle it).

However, once you, the user, disable QUIC scanning - we will ignore such connections completely and won't block QUIC inside browsers. (and remove the policy from the registry).
Ask a question