Today, two of my Windows machines (one on 7 and one on 8.1) using the development branch of Chrome upgraded themselves to 44.0.2398.0 dev-m. When I launched the browser for the first time after the update, all of my non-store extensions on were automatically disabled, and I could not re-enable them (and this happened on both machines).
Unsupported extensions disabled
To make Chrome safer, we disabled some extensions that aren't listed in the Chrome Web Store and may have been added without your knowledge.
So I figured maybe I could uninstall and reinstall all my userscripts. This works for one session, but when you close Chrome and relaunch it, the non-store extensions get auto-disabled again (and packed .crx files also suffer the same fate). Installing via Tampermonkey does not appear to help.
Is there any solution to this that does not involve switching to another OS (not feasible) or publishing my userscripts privately on the Chrome store (costs money)? Loading unpacked extensions still works, thankfully, but it's going to be quite a bit of effort for me to port all my userscripts over to proper extensions...
I'm reasonably sure that this is not a duplicate of Re-enable extensions not coming from Chrome Web Store on Chrome v35+ (with enhanced security), because I've been on the development branch of Chrome ever since they pulled this crap back in version 35 or so, and this is the first time I've had any problems since then. This is, as best as I can tell, a new issue.