In addition, setting any of the plugin Enterprise policies (e.g. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI (via the page action UI) while they wait for mission-critical plugins to make the transition.
Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. All NPAPI plugins will appear as if they are not installed, as they will not appear in the ugins list nor will they be instantiated (even as a placeholder). Now that whitelist is no more, and NPAPI plugins are being booted from the Chrome Web Store: In April 2015 (Chrome 42) NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. Earlier this year, Chrome developer Google pushed along the transition by drawing up a whitelist that only allowed a few trusted plugins to run by default.
