Document DefaultBrowserSettingEnabled caveats for Windows 10
Reported by
niroshan...@kp.org,
Sep 19
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Enable "DefaultBrowserSettingEnabled" policy using GPO or using Intune. 2. Run GpUpdate and/or Sync to apply Chrome policy to your device. 3. Open Chrome and run chrome://policy to validate that "DefaultBrowserSettingEnabled" is enabled (true). 4. Open Default Apps in Windows 10 and scroll down to "Web Browser section. What is the expected behavior? Google Chrome should be set as "Default" Web Browser in Default Apps. What went wrong? Chrome is not set as Default browser and instead, MS Edge stays as the default browser. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version:
,
Sep 21
,
Sep 21
,
Oct 31
,
Nov 22
The documentation in the policy description has been fixed. We could as a further polish also change the "Supported on" label in the GPO Editor to say "Supported on Windows 7" only instead of "Supported on Windows 7 and newer" as is currently the case for all policies.
,
Dec 10
,
Dec 13
The documentation bug was fixed in r596188 and is live at https://www.chromium.org/administrators/policy-list-3#DefaultBrowserSettingEnabled. The improvement mentioned in comment 5 is being tracked in issue 900206. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by niroshan...@kp.org
, Sep 19