We Keep Coding

Java JDK 16.0.1 installer crashing without even starting the wizard

I'm trying to install Java JDK 16.0.1. When I double-click the install file in the Downloads folder, it prompts me to allow changes, then does absolutely nothing.
I did some digging around in my %appdata% folder to look for crash reports/logs. It turns out every time I double-click the install file, it crashes with:
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
I do have Java Runtime Environment 1.8.0_291 installed, but that shouldn't prohibit the JDK installer, should it?
I also do have Java Runtime Environment 1.8.0_241 installed, and can't seem to be able to uninstall it. Could this be the problem? When trying to uninstall it, it looks for jre 1.8.0_241patch.msi, but can't find it. Regardless, this first issue shouldn't be a result of this old JRE install, correct?

I found this on the OpenJDK bug system:
https://bugs.openjdk.java.net/browse/JDK-8202316
for that user it was happening with the JDK 8 installer but the behavior sounds identical to the issue that you're having. In that post the original poster says "Problem solved. JDK 8u162 installer didn't remove all registry values of 8u152."
Now, I don't know why that's an issue; multiple JDKs should be able to peacefully coexist, but it might be worth a shot in your case before going to the length of doing a fresh reinstall of windows:
uninstall the JRE 8 version (your 1.8.0... version)
use tool or manually clean up any leftover java registry keys if necessary
reboot PC
try JDK 16 installer again
If you truly just have a JRE of version 8 and not a full-blown JDK, you could try using the java uninstall tool here:
https://www.java.com/en/download/help/uninstall_java.html
Also, I did find this old page about manually tracking down java registry entries (from 7.0 and older):
https://java.com/en/download/help/manual_regedit.html
Well, hope this helps. Be sure to let us know whether you get it solved, I'm curious to know. Thanks!

How can I run eclipse properly? [duplicate]

I have formatted my Mac due to some storage issues. Before this, I used Eclipse in a proper way. Now i have installed the JDK
Then, i have installed Java
Until now everything seems to be correct but when I open the Eclipse installer...
What can I do to fix this? I need to work with this the soon as possible.
Thanks

Eclipse on macOS will not start with Java 14 installed, this is being tracked in Eclipse bug 561273.
Installing Java 8 as well does not help. You need to remove the Java 14 install. You could use the Java 13.0.2 release instead.
Eclipse have determined that the root cause of this issue is a change in Java 14 which is described in this bug report JDK-8238225. The fix for this should be in Java 14.0.1
Update: Eclipse runs fine with Oracle Java 14.0.1 so the issue has been fixed.

I also asked this question which was closed, that's why I answer what I have found out: Eclipse will not install on Mac OS Catalina 10.15.4, saying the above error message
Failed to create the Java Virtual Machine.
Deinstalling jdk and install an older one wouldn't help on its own because Eclipse is refusing to install in the first place (as mentioned above). What I have done:
i´ve installed an JDK with boost (you can try several, mine worked with Version 13)
I edited the installer:
Download the dmg file
convert the dmg-file with "hdiutil convert /dev/disk3s1 -format UDRW -o devimage"
mount the converted dmg-file with: "hdiutil attach -owners on devimage.dmg -shadow"
Edit the /Volumes/Eclipse/Eclipse.app/Contents/Info.plist: there is a section which is commented and there you can try the jdk version. You have to give the full path to the java executable, for example:
<string>-vm</string><string>/Library/Java/JavaVirtualMachines/jdk-13.0.2.jdk/Contents/Home/bin/java</string>
Then my eclipse started from the (already) mounted Eclipse image without complaining

I had the same issue myself a while back. In your Eclipsepedia it provided an example of what the eclipse.ini file looks like when your trying to specify a JVM. So just change the eclipse.ini file and then make sure that you have all of the correct documents in that path to match the example.

Cannot install Ecplise on Mac:A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Eclipse [duplicate]

I have formatted my Mac due to some storage issues. Before this, I used Eclipse in a proper way. Now i have installed the JDK
Then, i have installed Java
Until now everything seems to be correct but when I open the Eclipse installer...
What can I do to fix this? I need to work with this the soon as possible.
Thanks

Eclipse on macOS will not start with Java 14 installed, this is being tracked in Eclipse bug 561273.
Installing Java 8 as well does not help. You need to remove the Java 14 install. You could use the Java 13.0.2 release instead.
Eclipse have determined that the root cause of this issue is a change in Java 14 which is described in this bug report JDK-8238225. The fix for this should be in Java 14.0.1
Update: Eclipse runs fine with Oracle Java 14.0.1 so the issue has been fixed.

I also asked this question which was closed, that's why I answer what I have found out: Eclipse will not install on Mac OS Catalina 10.15.4, saying the above error message
Failed to create the Java Virtual Machine.
Deinstalling jdk and install an older one wouldn't help on its own because Eclipse is refusing to install in the first place (as mentioned above). What I have done:
i´ve installed an JDK with boost (you can try several, mine worked with Version 13)
I edited the installer:
Download the dmg file
convert the dmg-file with "hdiutil convert /dev/disk3s1 -format UDRW -o devimage"
mount the converted dmg-file with: "hdiutil attach -owners on devimage.dmg -shadow"
Edit the /Volumes/Eclipse/Eclipse.app/Contents/Info.plist: there is a section which is commented and there you can try the jdk version. You have to give the full path to the java executable, for example:
<string>-vm</string><string>/Library/Java/JavaVirtualMachines/jdk-13.0.2.jdk/Contents/Home/bin/java</string>
Then my eclipse started from the (already) mounted Eclipse image without complaining

I had the same issue myself a while back. In your Eclipsepedia it provided an example of what the eclipse.ini file looks like when your trying to specify a JVM. So just change the eclipse.ini file and then make sure that you have all of the correct documents in that path to match the example.

Error installing JDK

I got following error while installing JDK 1.7 on windows 8.
"Error 1335. The cabinet file 'st170510.cab' required for this
installation is corrupt and cannot be used. This could indicate a
network error, an error reading from the CD-ROM, or a problem with
this package."
I have downloaded latest version of JDK from oracle foundation. previously JDK 1.6 was installed on my pc. I uninstalled it and tried to install this version and met this error.
For further information, I have already installed JRE 1.7 on my system.

Error:
"Error 1335. The cabinet file 'st170510.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package."
is not because of Issue in JDK setup or as such.
Some of the reasons may be:
Some research suggests that this problem may arise because of bad RAM.
Source - https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=65872
This is a Windows Installer error that may occur for different cabinet file names located on the installation media (usually on CD).
Source - error-1335-the-cabinet-file-filecab-required-for-this-installation-is-corrupt-and-cannot-be-used-this-could-indicate-a-network-error-an-error-reading-from-the-cd-rom-or-a-problem-with-this-package
Can be caused by User Access Control.
Source - http://www.symantec.com/connect/forums/error-error-1335the-cabinet-file-data1cab-required-installation-corrupt-and-cannot-be-used-co
Corrupted installer caused by a firewall or virus software running on your computer.
Source - http://www.tomshardware.com/forum/7992-63-error-1335-help
Occur when the installer is unable to access the necessary files from the DVD/CD-ROM drive.
Source - http://helpx.adobe.com/creative-suite/kb/install-error-1311-1335-or.html
Each link has its own list of steps to resolve the Issue.
Not sure what may be causing Issue in your case.
You can try different solutions and see if any one can help.
Thanks!!

I think it has something to do with Windows "unblock" feature. (Rich click on file, select "unblock")
We had this issue before when we downloaded a Zip file, extracted an installed, and ran it - it failed - we had to unblock the file first - we also noticed that extracted elements were also "blocked" as well.
Java Install >>- On downloading using windows, file transfer speed was fast until the very end. then it seemed to stall.
Any attempt to install from these files produced errors and a fail.
Fix >>- I then downloaded it using a MAC and then transferred the files back to the windows box and did the install again.
This time it was perfect - no errors - good install.
Rob

I was installing Oracle Java 8 JDK (version 111) on a Windows 10 machine. I got the same error as described in the question.
I disabled windows defender (all checkboxes to off), downloaded the file, went to its properties clicked unblock and apply. Then the JDK installed fine.

I had the same problem. After reading all the answers, I concluded that the downloaded .exe file was getting corrupt each time I download. Initially I used Internet Edge for the download (like 5 times) and I had the problem every time. The problem got solved when I switched to chrome browser, downloaded and installed again.

I faced the same problem, but with 1.8 on windows 7 (tried with jdk8u91 and jdk8u92). None of the other solutions here worked, but unchecking the "source code" and "public jre" options caused the error to not occur. Not a complete solution if you need the source code - the jre is available separately anyway - but it got me through the installer, and the jdk seems functional.

When you meet this problem ,you compare the two files with WinMD5Free after downloading them.
At first I used chrome and IDM to download the JDK files and always met with an error although I changed other versions many times.
Hence I use Firefox download the JDK file and problems are resolved.
^_^

OS: Windows 10 Pro
Java: 10.0.1
When trying to run the JDK installer from the "Downloads" folder I kept running into the same error (only different .cab file). I tried running as admin, different compatibility mode, scanning with the Windows scanner. Nothing helped.
Then I just downloaded to Desktop. I ran it as Administrator and Java installed without any problem.

Yomu and Heroku

I just installed the 'yomu' gem (https://github.com/Erol/yomu) in my application and deployed to heroku. On my local machine (Mac OS) it runs fine. I noticed in the documentation it states that JRE is required for it to work.
When I run the application on Heroku I get the following error:
Errno::ENOENT (No such file or directory - java -Djava.awt.headless=true -jar /app/.bundle/gems/ruby/1.9.1/gems/yomu-0.1.1/jar/tika-app-1.1.jar -t):
I'm assuming that yomu can't find the java compiler on Heroku. Am I reading this right? If I am, is there an add-on that I'm not considering?
By the way, the reason I'm using yomu is because it can extract text from doc and docx files.
Thanks!

If you're running on the Cedar stack then a JDK is available to you at: /usr/lib/jvm/java-6-openjdk
I'm not sure how Yomu finds your Java install, but it's probably looking in JAVA_HOME. If so then setting JAVA_HOME on Heroku should make it work:
heroku config:add JAVA_HOME=/usr/lib/jvm/java-6-openjdk

Not a java compiler - a java runtime (a JRE, like the documentation said). Installing a JRE as an addon is not (yet?) supported on Heroku.

In the new Heroku-16 stack, you can add jvm as a buildpack and you don't need to configure paths or anything else. Just make sure to have it set as your first buildpack. I tried it with Yomu/Henkei and it worked for me.