Author Topic: Chrome: Managed by your organisation (Avast 20.2.2401)  (Read 77924 times)

0 Members and 2 Guests are viewing this topic.

Offline David_27

  • Jr. Member
  • **
  • Posts: 98
Re: Chrome: Managed by your organisation (Avast 20.2.2401)
« Reply #90 on: May 25, 2020, 07:27:01 PM »
So I found a solution to this if you don't want it appearing. Opening avast antivirus on your computer, selecting the top right menu bar, then select settings, after that select protection, select core shields, then scroll down to "configure shield settings". after that select web shield and then disable the enabled "Enable QUIC/HTTP3 scanning". then close avast, and restart your browser, the "managed by your organisation should disappear as that is what i did to make it disappear from my browser. sadly this does remove a minor protection from your browser but gives you extra privacy.
Privacy? From what exactly? And you prefer having tat instead of protection?

You could just use the new Edge, it's a much better browser and that message doesn't appear, you don't need to disable any protection in Avast.
Edge is built on Chromium as are many others including Google's Chrome. 'Better' is in the eye of the beholder.

Just because it's chromium based it doesn't mean it's the same as chrome, almost all those other chromium browsers are better than chrome.
It's not news that the new Edge is chromium based, but still a very different browser. Just test it or watch reviews, it uses less resources, way better optimized, those are just facts.
A whole better browser. It's replacing legacy edge as windows default, so you can even save disk space by not installing chrome.
Again, you're voicing your own, personal opinion. :)

It's a fact that the new edge uses less resources, lower cpu load and ram usage, not an opinion.
But we're already going offtopic here. I brought Edge to the topic to say that it doesn't show the give you the "managed by your organization" message.
« Last Edit: May 25, 2020, 07:34:04 PM by David_27 »

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48552
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Chrome: Managed by your organisation (Avast 20.2.2401)
« Reply #91 on: May 26, 2020, 12:01:36 AM »
@David_27,
No one is telling you not to use it.
Browsers are usually a personal choice and we all have our favorites. :)
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline evvie01

  • Newbie
  • *
  • Posts: 1
Re: Chrome: Managed by your organisation (Avast 20.2.2401)
« Reply #92 on: June 07, 2020, 05:39:19 AM »
Is the QuicAllowed supposed to stop purchases, or disallow transactions?
Life happened as computers, software, and the internet  change stuff, it all got away from me. Any help is appreciated. Thank you.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Chrome: Managed by your organisation (Avast 20.2.2401)
« Reply #93 on: June 07, 2020, 06:26:38 AM »
Is the QuicAllowed supposed to stop purchases, or disallow transactions?
Nope.
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline TheOwner

  • Poster
  • *
  • Posts: 406
Re: Chrome: Managed by your organisation (Avast 20.2.2401)
« Reply #94 on: June 07, 2020, 03:14:53 PM »
Chrome is no longer managed by organisation in Avast 20.4.2410, that means QUIC is enabled and scanned? Strange is for example youtube used QUIC and now always use TLS 1.3, maybe is QUIC disabled somewhere else?