Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Is it possible to remove Java Deployment Toolkit from the add on list

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by Reynardine

more options

I decided to uninstall the Java Deployment Toolkit from windows as it is permanently disabled in add ons. Not sure having read some of the posts that this was such a good idea, but if it is never activated what is the point of having it installed or listed in add ons ?

I decided to uninstall the Java Deployment Toolkit from windows as it is permanently disabled in add ons. Not sure having read some of the posts that this was such a good idea, but if it is never activated what is the point of having it installed or listed in add ons ?

Modified by Reynardine

All Replies (2)

more options

Like most plugins, you'll need to uninstall Java Deployment Toolkit from outside Firefox. But... I don't see it in the Uninstall a Program Control Panel. So if you want to still have Java, I think your choices are:

(1) Leave it fully disabled ("Never Activate") (2) Remove the registry entry Firefox uses to locate the plugin (3) Delete the plugin's DLL file from disk (or rename with an inactive extension like .OLD)

The third is probably easier than the second, because you can learn the location of the DLL on disk by typing or pasting about:plugins in the address bar and pressing Enter.

more options

I found the Java Deployment Toolkit listed below 'Java 8 update 40' in uninstall programme list in Windows, so what I probably uninstalled was Java Deployment Toolkit update 75 (?). I find all this a bit confusing, did I just uninstall an update ?

It all seems a bit more complicated than I thought having read some of the posts on this topic and probably beyond my expertise , which is fairly basic. I think I might just download the latest update for Java Deployment Toolkit and leave it fully disabled. A post in MozillaZine reckoned the plug in might come back anyway when Java was next updated.

Modified by Reynardine