Enterprise customer noted that this issue is reproducible on Chrome Browser versions 51,52,and 53 (Windows)

TYPO:  
In "what steps will reproduce the issue"...

(3) Set "Configure extension installation blacklist" to lhpbckonakppajdgicbjdfokagjofnob

should be:

(3) Set "Configure extension installation whitelist" to lhpbckonakppajdgicbjdfokagjofnob

Matt: This seems like a very bad bug. Can you triage this ?

untriaged w/ owner -> assigned

Krishna, can you see if we can reproduce this?

If yes, we should see when this change went live and mark as p0.

+ bustamante@ on repro and prioritize as M54 is already in stable for Desktop.

Per #2 this has been around since M51, if administrators have already adjusted to how the blacklist/whitelist rules work, changing that may have unintended consequences.

I reached out to our test folks to work on repro'ing it.

Making this is ReleaseBlock-Stable for M55 since it's been around for a while.

Assigning to few folks who can try a repro from TE. Meanwhile requesting yyefet@ to try a bisect since you already have the system setup. 

Instructions for bisecting.

https://sites.google.com/a/google.com/chrome-te/home/tools/bisect-builds

I have quickly checked this on my Windows 10 machine with Chrome version 55.0.2883.21(x64) everything works correctly, below are the steps which I have followed :

Steps Followed :
(1) Download and install Chrome ADM on windows 10
(2) Set "Configure extension installation blacklist" to *
(3) Set "Configure extension installation Whitelist" to lhpbckonakppajdgicbjdfokagjofnob
(4) Exit and relaunch Chrome
(5) Visit chrome://policy and make sure the policies has been set i.e., "ExtensionInstallBlacklist : * " and "ExtensionInstallWhitelist : lhpbckonakppajdgicbjdfokagjofnob"
(6) navigate to https://chrome.google.com/webstore/detail/visor/lhpbckonakppajdgicbjdfokagjofnob?hl=en
(7) try to manually install extension...   

Observed behavior :
Able to install the the extension which is being whitelisted.

Note : I am not sure it makes any difference w.r.t setting the policies on Windows 10 or Windows 2012 server and enforcing thtoughout the domain. Please correct me if I am wrong.

**** Bulk edit -  please ignore if not applicable ****

A friendly reminder that M55 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Yehuda & Royans,

Can you guys please confirm that this is an issue? I am removing release-block-stable  and marking as 'wontfix' as Prudhvi was able to confirm that everything is WAI yesterday.

Please re-open if you see other behavior.