senofy/autofirmer-expanded
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

The managed-machine rule is Chromium's, not Edge's

Browse Source 
Chrome blanks an off-store ExtensionInstallForcelist entry on an unmanaged
machine exactly as Edge does - the qualifying states are AD domain join, Entra
join, or Chrome Enterprise Core enrolment, and this box is none of them. The
guard now covers every browser and refuses up front, with the three ways
forward, instead of skipping Edge alone and letting Chrome fail the same way.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Brandon Li
2026-08-31 13:30:04 -05:00
co-authored by Claude Opus 5
parent e42e729189
commit ce6fa6c0e1
3 changed files with 71 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -4
View File
@@ -144,10 +144,11 @@ powershell -NoProfile -ExecutionPolicy Bypass -File scripts\install-extension-po
sudo scripts/install-extension-policy.sh
```
No administrator rights on Windows, where it goes into the user's own policy
hive; root on Linux, where Chrome only reads policy from `/etc`. **Not Edge** —
an unmanaged Edge refuses to install anything that is not from the Microsoft
Store, so use Chrome or Brave, or run the unpacked copy there. See
**This only works on an enterprise-managed machine** — domain-joined,
Entra-joined, or enrolled in Chrome Enterprise Core. No Chromium browser will
force-install an off-store extension on an ordinary PC, whatever the registry
says; the scripts check and refuse rather than leave a dead policy behind. On an
unmanaged box, load `extension/` unpacked and let it reload itself. See
[deploy/README.md](deploy/README.md). Either way the extension notices when
the dashboard is running newer code than it is: a policy install asks Chrome to
fetch the new CRX, an unpacked one reloads itself from disk. Clicking the reload