Forum Discussion
Web content filtering and indicator aren't working on third party browser
CharlieAD we have heard from Microsoft support that disabling Quic in chrome will resolve this as network protection for defender does not support quic protocol. Since testing with it disabled in chrome we have seen it working correctly so far. No word whether or not support for this is coming in the future for network protection.
I did the below to test but ended up pushing out in Intune for some of our staff devices to test further
To disable HTTP/3 (QUIC) in Google Chrome, please follow these steps:
Open Google Chrome.
In the address bar, type: chrome://flags#enable-quic
Locate the Experimental QUIC protocol flag.
Set the flag to Disabled.
Relaunch Chrome for the setting to take effect.
Nweber531 Looks like you and Microsoft Support found the solution. I have tested across multiple machines and its consistent with what you said. Now I just need to figure out how to disable QUIC remotely on our deployed chrome instances. Thanks again for jumping in with the answer!
CharlieAD Awesome its great to hear it working beyond our environment. If you use Intune, we setup a Congifuration Profile for Windows 10 and Later, Templates > Administrative Template, Create, then after naming it, if you search "Allow QUIC Protocol" you can see options for Edge and Chrome to disable for user or device based.
We have been testing since yesterday. So once this pushes out to devices for example, we noticed when you go into the chrome settings, it still shows as default (and if changed to enabled), but the pushed out setting from Intune is still taking priority.