Download Restrictions keeping students from installing Google Extensions?

Brodie_McBeath
New Contributor III

Not sure how long this has been going on, but as of yesterday we noticed that students are no longer able to install Extensions from the Chrome Web Store. When they go to Add to Chrome on an Extension that is on their Allow List, a Chrome box now pops up in the bottom right corner saying download unsuccessful and Failed - Security settings on your computer blocked this file. When I turn off our Download Restrictions, I am able to install an extension no problem. This seems to be affecting all Non-Forced extensions at the moment. This affecting anyone else all of a sudden? Did something change? Our settings are as follows...

Extensions - Currently, we are blocking all Extensions with the exception of an Allow List.

Download Restrictions - We have always had this setting set to Block Malicious Downloads and Dangerous File Types. Opening this up allowed the extension to install.

URL Blocking - We were blocking file://* as a way to combat the HTML games. I removed this URL and unfortunately this did not resolve the issue.

--
Brodie McBeath - Sys Admin - Joshua ISD (Tx)
1 ACCEPTED SOLUTION

msnead
New Contributor II

https://issues.chromium.org/issues/391666313

Supposedly the issue is fixed in chrome 136

View solution in original post

4 REPLIES 4

Brodie_McBeath
New Contributor III

I've verified in my environment that extensions are considered Dangerous File Types now. Removing this and just leaving Block Malicious Downloads now allows for extensions to be installed from Chrome Web Store again.

I'm curious as to when this happened and if this was intentional...

--
Brodie McBeath - Sys Admin - Joshua ISD (Tx)

steve
New Contributor III

We ran across this a couple of months ago too, and had to do the same thing (step down the restriction one level). It's not clear to us whether this is a bug or whether Google has redefined the levels.

msnead
New Contributor II

https://issues.chromium.org/issues/391666313

Supposedly the issue is fixed in chrome 136

Good catch! Appreciate you sharing that.

--
Brodie McBeath - Sys Admin - Joshua ISD (Tx)