Google rolled out version 42 of the Chrome browser this week. Along with security fixes, the biggest change is the disabling of NPAPI plugins by default. This means sites using Java, Silverlight, and other plugins will no longer work in Chrome. This NPAPI deprecation has been a long time coming with the Chromium documentation starting in January 2014.
The April 2015 stage introduced in Chrome 42 disables plugins by default but does allow the setting to be reversed. Come September 2015, it will not be possible to enable NPAPI plugins in Chrome. On Chrome 42, you will receive a message “This plug-in is not supported.”
To change the newly introduced default behavior, Chrome can be started with plugins enabled by including the –enable-NPAPI parameter on Chrome’s shortcut, such as Chrome.exe –enable-NPAPI. Another workaround is to use the Enable-NPAPI flag on Chrome by visiting chrome://flags/#enable-npapi in the browser and clicking the corresponding ‘Enable’ link.
To re-enable plugins administratively using Group Policy, you can use the Chrome Administrative Templates. Using a setting that enables plugins will switch the Enable-NPAPI plugin for those computers receiving the policy.
The setting is under Computer ConfigurationAdministrative TemplatesGoogleGoogle ChromeContent Settings.
Allow plugins on these sites – Enabled and with a domain in the listed site actually enabled Java on the other sites I tested as well.