FULL PRODUCT VERSION :
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b20)
Java HotSpot(TM) Client VM (build 23.0-b21, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]

Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
When installing jre 1.7.0_04 on Windows (both 7 and XP) the installer no longer configures .jar association in windows. This means you can no longer launch a jar from the explorer.

Installer from 1.7.0_03 still associates a .jar correctly.

You don't notice this issue if upgrading from a previous jre7 (association still there). But on a first time installation the association is not there. If installing jre7u4 after installing jre6, the association is still using jre6, causing class version errors if using jre7 classes.

Correctly associated it results in:
assoc .jar
  .jar=jarfile

ftype jarfile
  jarfile="C:\Program Files\Java\jre7\bin\javaw.exe" -jar "%1" %*


REGRESSION. Last worked in version 7

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
On a clean system install jre7u4 and try to launch an executable .jar from Explorer

- or -

Remove the association (from elevated cmd.exe)
  assoc .jar=
  ftype jarfile=
Install jre7u4 and check the association
  assoc .jar
  ftype jarfile
both commands will result in not found messages.


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Executable .jar can be launched from the explorer

  From cmd.exe view association:
assoc .jar
  .jar=jarfile

ftype jarfile
  jarfile="C:\Program Files\Java\jre7\bin\javaw.exe" -jar "%1" %*

ACTUAL -
Unable to launch .jar from explorer

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Manually add the association (from cmd.exe, elevated on win7):
  assoc .jar=jarfile
  ftype jarfile="C:\Program Files\Java\jre7\bin\javaw.exe" -jar "%1" %*