Cannot find Java SE Runtime Enviroment 1.6
843798Jun 27 2009 — edited Jul 2 2009This problem has been bugging me for a long time now. I have no idea what may have caused this error to occur where an applet can't find the SE runtime enviroment, and in fact I may not even be able to recall if it ever worked since getting an upgrade to Vista. Since I don't really know how I'd go about forming an initial log or investigation for finding clues, I'll just bullet point my situation;
1. I'm using Vista 32bit with a single HDD partition.
2. I'm attempting to use 1.6 in the use of virtually all free Java applications I can get my hands on.
3. I have re-installed countless times with no effect.
Problem: Tried to use a downloadable open-source program that uses Java or access any page in Firefox that has a Java applet embedded. Programs will return with the message "Error: could not find Java SE Runtime Enviroment". Firefox applets will tell me I need to install Java.
Information: Re-installing shows that, if I don't uninstall first, the installer will detect Java being already installed. Java appears under the Control Panel. Firefox can detect a Java plugin installed. Whenever, according to the ever so useless Help Center page, I try to enable the Java Plugin through the Control Panel, it keeps claiming that a web browser window is open, even when I've made sure to terminate the processes of all browsers myself. Using regedit, I can find the folder related to Javasoft (although I have little knowledge what to look for) and that it's currentversion shows up as 1.6, but several folders keep denying me access despite having admin access, although it says I can alter permissions strangely.
I'm afraid that if you wish to help me, you'll have to assume I know nothing about Java other than the average consumer since I'm not a developer, although I understand some concepts in IT such as using the command prompt and registry unlike the average consumer.
Another possibly related problem is that .jar files haven't been associated, but that now appears to be an isolated incident with only one specific program.