From time to time it’s possible that the PolicyPak Browser Router extension for Chrome will be installed, but not active, like in this example.
This can occur if you are attempting to force deploy the extension via Group Policy or PolicyPak Application Manager or if there is some kind of error.
The first workaround to try is to rename the problematic extension folder:
i.e. %LocalAppData%\Google\Chrome\User Data\Default\Extensions\fmbfiodledfjldlhiemaadmgppoeklbn
Then close and relaunch Chrome, also check the Systray to ensure Chrome is not running in the background, if it is then disable that option.
If that does not work then rename the %LocalAppData%\Google\Chrome\User Data\Default\Extensions folder to reset the Chrome extensions.
This should snap it back in place the next time Chrome re-launches.
As a last resort, if the above does not work you can rename the %LocalAppData%\Google\Chrome\User Data\Default folder to reset Chrome and then close and relaunch Chrome.