This is due to the fact that since April 2015, in Chrome, the default support for the NPAPI architecture for plugins is disabled (on which Java is based on). However, at the moment, the ability to enable support for these plugins is still available as shown below.
Enable Java plugin in Google Chrome
In order to enable Java, it will be necessary to allow the use of NPAPI plug-ins in Google Chrome to which the required one relates.
This is done elementary, literally in two steps.
- In the address bar, enter chrome: // flags / # enable-npapi
- In "Insert an NPAPI" click "Enable".
- At the bottom of the Chrome window, a notification will be notified that it is necessary to restart the browser. Do it.
After restarting, check if Java works now. If not, make sure the plugin is enabled on the Chrome: // Plugins / page.
If, when you enter the page with Java on the right side of the Google Chrome address bar, you will see the icon of the locked plug-in, then you can, by clicking on it, allow plugins for this page. Also, you can set the "Run always" marker for Java on the settings page specified in the previous paragraph so that the plugin is not blocked.
Two more reasons why Java may not work in Chrome after all described above has already been completed:
- Installed Outdated Java version (download and install from the official site java.com)
- The plugin is not installed at all. In this case, Chrome reports that it needs to be installed.
Please note that there is a notification next to the NPAPI switching on setup that Google Chrome starts from version 45 will completely stop supporting such plugins (and then the start of Java will be impossible).
There are some hopes that this will not happen (associated with the fact that decisions related to the disconnection of plug-ins are somewhat delayed by Google), but, nevertheless, should be addressed to this.