New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 609145 link

Starred by 3 users
Status: Fixed
Owner:
pastarmovj@chromium.org
Closed: Aug 2016
Cc:
grt@chromium.org
zmin@chromium.org
█ dskaram@chromium.org
georgesak@chromium.org
█ saswat@chromium.org
█ blumberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Google Update ADMX Reads State of "Update policy override default" Incorrectly

Reported by woodens...@gmail.com, May 4 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36

Steps to reproduce the problem:
1. Enable "Update policy override default" and set the policy to Updates disabled and click OK
2. Open "Update policy override default" 
3. Note that the setting has reverted to just plain "Disabled".

What is the expected behavior?
Setting the Update policy override default" to Enabled with the Policy as Updates disabled should result in that setting be displayed the next time you open the policy.

What went wrong?
It would appear that the registry setting the policy checks for its current configuration is not DWORD UpdateDefault in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update.

Did this work before? N/A 

Chrome version: 50.0.2661.94m  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by tnagel@chromium.org, May 12 2016

Cc: saswat@chromium.org pastarmovj@chromium.org dskaram@chromium.org
Owner: grt@chromium.org

Comment 2 by pastarmovj@chromium.org, May 12 2016 

Greg I can take this one if you wish? :)

Comment 3 by grt@chromium.org, May 12 2016

Cc: -pastarmovj@chromium.org georgesak@chromium.org grt@chromium.org
Owner: pastarmovj@chromium.org
That'd be awesome, thanks. The ADMX generator for Google Update was added in cl/99967186.

Comment 4 by pastarmovj@chromium.org, May 24 2016

Status: Started (was: Unconfirmed)
Good news I could repro the problem. It doesnät happen with the per application policies only with the global policy this should make it easier to see what's different there and fix it.

Comment 5 by pastarmovj@chromium.org, May 24 2016 

Fix is in review - cl 123093420

Comment 6 by woodens...@gmail.com, Aug 3 2016 

Not that this bug is a show stopper or anything, I just like to keep an eye on things.  I was just curious how long things get reviewed before they are put into production? Thanks for the work guys.

Comment 7 by blumberg@chromium.org, Aug 3 2016

Cc: blumberg@chromium.org zmin@chromium.org

Comment 8 by pastarmovj@chromium.org, Aug 3 2016

Status: Fixed (was: Started)
Sorry my bad that I forgot to update this bug. The fix has been committed just a day after I posted the last update. I can't however say when an updated ADMX file will be made online by the Google Update release team. Sorry for keeping you in the dark for so long.
►

Sign in to add a comment