eshimpach Bronze Medal

Yes, last week I experienced this when I upgraded to Chrome 58.0.3029.110. I think our System Admin disabled an Add-in, but not sure which one(s). Chrome is still upgraded and it is working fine now.