Java Runtime Environment 7 Update 45

Java software allows you to run applications called "applets" that are written in the Java programming language. These applets allow you to have a much richer experience online than simply interacting with static HTML pages.

Java Plug-in technology, included as part of the Java  Runtime Environment, Standard Edition (JRE), establishes a connection between popular browsers and the Java platform. Java allows applications to be downloaded over a network and run within a guarded sandbox. Security restrictions are easily imposed on the sandbox. Many cross platform applications also require Java to operate properly.

Download 32-bit: Java Runtime Environment 7 Update 45 | 27.7 MB (Freeware)
Download 64-bit: Java Runtime Environment 7 Update 45 | 29.3 MB (Freeware)
Download: JavaRa 2.3
Release Notes: >> Click Here <<
View: Java Website

Report a problem with article
Previous Story

Six things Microsoft got right in Windows 8.1 and others still missing

Next Story

Microsoft talks about merging SkyDrive programming in Windows 8.1


Commenting is disabled on this article.

How do I rollback to 7 40 on Mac OS X 10.7.5? Can I copy something over from a machine I didn't update on? Approximately the same OS.

I don't know why so many people hate on Java updates so much. Do they also hate Windows Updates? Firefox updates? Chrome updates? Office updates? All get updated often.

The fact is most people don't need Java on their desktop these days unless they use a specific piece of Java desktop software which is pretty unlikely these days unless they are using a legacy app as Java never really caught hold on the desktop outside of some line of business apps and other specialised apps. The only reason I can think that a regular computer user would need Java is that some online banks still use horrible, old Java applets however they are few thankfully.

If you don't need Java then don't install it and don't bother commenting every time there is an update. If you do use Java then be glad it is getting security updates! Just like Windows Updates they are a bit of a pain but not really all that bad.

Their new version numbering scheme is rather convoluted:

- Limited Update releases will be numbered in multiples of 20.
- Critical Patch Updates will continue to use odd numbers. The numbers will be calculated by adding multiples of five to the prior Limited Update and when needed adding one to keep the resulting number odd.

...which means U45 is the 1st critical patch for Limited Update 40.

Rather convoluted? More like rather putrid!!

One of the most useless programs ever written, not to mention most insecure!

I know it has uses but not on any of my machines. I think I've had this thing installed 3 times since 1997 and uninstalled it immediately after what ever reason I installed it for.

Actually Java is one of the most secure platforms available. The browser plugin is horribly insecure but that has more to do with its 90s design than anything specifically 90s related. There is a reason that the majority of enterprise backend systems are written in Java one of them being security. While you may not use Java directly on your desktop dozens of online systems you use will rely on Java to power them on the backend.

My god, it's relentless... we're only just getting around to rolling out u40 at work, which I now note expires in December. Might just recommend jumping straight to u45 and be done with it until Feb next year. Does mean our devs will have to re-test though, and clients stay on u25 for another week or two.

Lastly, anybody have any idea why they've started jumping release numbers?

They incremented by 1 up until 11, then they missed alternate numbers until 17, then they started missing large chunks of numbers. 25 - 40 being the worst. Is there some point to it?

The expiration is simply a way of Java to encourage updates. It is easy to disable this check and should be disabled for any large business rollout. It is designed to prompt people who know nothing about these things to keep up to date but the expiration does not actually "expire" anything.

We've discovered that the registry key we used to set to disable the updater, doesn't seem to work any more since something like update 21. From what we've discovered so far, there's a way to compose an XML file, that you then have to package into a JAR file and sign with a certificate to whitelist sites and turn off the update checking. This is less than straightforward. Do you have an easier way?

The number isn't relevant any more... there hasn't been 45 updates, so it's misleading. They've been skipping large chunks of numbers recently, from 25 to 40 is the worst example. Not entirely sure why they think that's a good thing