If you don’t want to go through the hassle of removing registry keys or running Powershell scripts, follow this method for a more casual route. Although we’ve been unable to confirm this, some users have reportedly managed to fix the issue by uninstalling all the remaining Java components and using the one-click installer to update to the latest version.
Some users have reported that this issue seems to be addressed with the 2018 releases of Java. If it proves to be ineffective, move down to the other methods below. We strongly advise you to start with the first method since it’s the easier out of the bunch. We managed to identify a selection of potential fixes that have helped users in a similar situation such as yourself. If you’re currently struggling with this particular issue, you might be in luck.
