User:Mjb/Java updates

From Offset
< User:Mjb
Revision as of 06:54, 21 December 2015 by Mjb (talk | contribs)
Jump to navigationJump to search

Here are some notes about Java updates on Windows 7.

The 32-bit JRE installation (in C:\Program Files (x86)\Java) updates itself, but produces strange warnings about certificate problems. There's apparently no fix for it.

The 64-bit JRE installation (in C:\Program Files\Java) does not support auto updating yet (a known issue since 2006). So you have to manually install the latest version whenever is convenient.

The Java verify/uninstall page (doesn't work on Chrome) will tell you what you have installed and will let you uninstall and replace outdated versions. If your 64-bit version is outdated, it will uninstall it, but it won't install a replacement for you. You have to do that manually.

Here's where to download the latest versions (this week):

Java and Serviio

If a 64-bit Java app like Serviio is running when you do the update, you'll be prompted for a reboot. But even after the reboot, Java doesn't be installed correctly and the Serviio service won't start. You'll get a warning (from Serviio Console, although it won't say that) about needing to set EXE4J_JAVA_HOME to point to a 64-bit JRE. Ignore the warning and just re-run the 64-bit JRE installer without Serviio running. It should prompt you about that version of Java already being installed; just continue and it should complete the installation without error. Then you can go start the Serviio service manually.

Next time, before running the 64-bit JRE installer, just right-click on the Serviio icon in the system tray and choose "Exit Serviio" to shut down Serviio Console and the Serviio service. After installing the new JRE, restart both from Start Menu > Serviio.

Java control panel

If you're running a 64-bit version of Windows, the Java control panel will be the 64-bit version, which doesn't have an Update tab due to the issue mentioned above. I assume this control panel only affects the 64-bit JRE. You can also point it to your 32-bit JRE, but I don't know if doing so has any effect.