Google Chrome "Managed" status issues 🤔

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Simon Zerafa

Sep 18, 2020

If you find that Google Chrome is blocking or disabling some of its own settings (DNS over HTTPS for example) because the browser is "Managed" then check chrome://policy in the browser.

Anything that is configured here will likely flip the browser into Managed status. Something has changed one of the Password Policy settings and I suspect it's the Lastpass browser plugin.

I'm in the process of investigating this at the moment, updates to follow when available 😏

KInd Regards

Simon Zerafa
Chrome Policy Settings: chrome://policy
Chrome policy Documentation:
Cloudflare eSNI Check:
  • Like
Reactions: Barry Wallis
It’s also important to note that company-issued devices might put their browsers in Managed mode, even if they didn’t come with the device initially.

This shouldn’t be the case if you never connect your personally-bought device to any employer’s services.