Java Installer doesn't run
-
I'm not sure where Java was before all this started, but I think the Program Files folder. But with JavaRa, it put 8.111 in another drive entirely, the one where I kept some old files from Win 8.1. I emptied that drive, as well as my Win 10 files backup drive, onto a USB stick and haven't hooked them up yet. Before I do so, I wonder how I could get the install pointed in the right direction. A clean install isn't going to happen just for Java, at least not at the moment. Many thanks for looking!
-
-
Okay so then we are back to your comment, the registry. Have you search it for references. The installer must be getting info from it.
Its obvious you know what you are doing so I won't go into all the warnings.
If I were to experiment I would ensure I have a system Image that I can restore. I would have a full copy of the registry and specific instruction on backing up pieces I might change. (Don't want to go nuclear because of a finger slip.)
-
So for all the posts.
from the log
TRACE: Installed Java detected: version=1.8.0_111; arch=64; productCode={26A24AE4-039D-4CA4-87B4-2F64180111F0}; type=0
Maybe you want to search the product code to see it it is somewhere with Windows or program / programdata folders.
-
-
Didn't find anything with the product code.
Update: I went hunting for registry entries and deleted the first couple of groups of JRE entires that looked like possible suspects. The good news is doing that restored the installer; the bad news it it still leads to the 1603 error (run as Admin). The problem now is that the instructions for getting around the 1603 error assume an install, which I no longer have.* There must be other likely registry entries to look for. I ended up with four log files from the install attempt, and have submitted a bug report with the contents of one of the files. Thanks for your patient help.
*https://java.com/en/download/help/error_1603.xml
Update 2: Now that the installer is working, I used the defunct JavaRa program to install 8.111 on the system drive. 8.121 still brings the 1603 error.
Last edited by highstream; 30 Jan 2017 at 00:22.
-
Well given they know they have a problem you may have to wait it out with 8.111.
Sorry I couldn't be of more help. Sometimes we just have to wait for the coders.
Did you try their two alternate methods?
-
The alternate methods are either/or and neither has worked. Just submitted some logs to Oracle on the bug report showing uninstall method doesn't work.
-
Have you tried this
File Explorer
Then C Drive
Then Programs
Also Programs x86
You may find traces of the folder in there
If there is Right Click it and delete it that should get rid of it
I have had to do that with my Antivirus I wanted removed
Also another program I needed removed
You may have to do it 2-3 times
-
From the OP: "I removed Java from my computer via...and did a bit of additional removal via file manager searching." So the answer is of course I checked the program folders and other places - many times. Oracle support asked me to look too, as well as for other mentions, and the upshot of that is my last post. Please understand that the 1603 error is recognized on the Java site as a known bug and that the alternate methods have not worked for some (many?) people. My hunch is that the culprit is something in the registry, but don't really know. it's in their hands.
-
-
What if you logged on as local admin and installed? If an older version of Java is detected then most likely you have a reg key hanging around. Ccleaner should be able to tell you if it is in the "uninstall" key as there are 3 of the "uninstall" keys in the registry.
-
In Win 10, isn't the normal account local/admin? In Win 8.1 and earlier they were split. The initial problem in the OP was definitely a registry issue and I found it, or got close enough. Not sure from where I am now that the uninstall entries would solve the 1603 problem, since I did try the current version from scratch. And I'm not sure how you are suggesting to use CCleaner, since I didn't notice a Java entry in its settings when I checked the other day.
Quote