This article came out this morning and explains how Java does (or did) not clear older versions of itself off the disk, leaving it there for older security holes to be exploited by malware:
http://www.zdnet.com/article/oracle-ordered-to-blitz-users-with-java-security-warnings/
In addition to being security risk(s), on Windows the earlier installer earlier versions (< 1.6, I think) also created new registry links instead of removing the older link(s), sometimes causing the older version to continue to be used.
As the article states, in the US the FTC has ordered Oracle to warn users about this. Prepare for e-mail. Hopefully they'll change their website to stop auto-loading the 32-bit version even if you have the 64-bit older version installed as well...
http://www.zdnet.com/article/oracle-ordered-to-blitz-users-with-java-security-warnings/
In addition to being security risk(s), on Windows the earlier installer earlier versions (< 1.6, I think) also created new registry links instead of removing the older link(s), sometimes causing the older version to continue to be used.
As the article states, in the US the FTC has ordered Oracle to warn users about this. Prepare for e-mail. Hopefully they'll change their website to stop auto-loading the 32-bit version even if you have the 64-bit older version installed as well...
Last edited: