FULL PRODUCT VERSION :
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)


ADDITIONAL OS VERSION INFORMATION :
the problem exists in win xp, 7 and 8. 32-bit and 64-bit.

A DESCRIPTION OF THE PROBLEM :
I am developer of a webstart application.
CouldNotLoadArgumentException or FileNotFoundException is raised at a lot of users with every java update. The Application cannot be started any more. It seems, that the cache or parts of the cache(my App)
crashes on the updates.
The benefit of webstart (Easy Distribution and Update Management) is away.
It always pointers to a non existing file in the Java Cache. Here an example:
 

File Associations are also often corrupt when a Java Update was made.

ADDITIONAL REGRESSION INFORMATION:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Install an old jvm.
2. Install http://0030000030.finnymede.com/Finnymede.jnlp.
3. Update to the newest jvm.
4. take some file and name it to xxxx.x33
5. click on that x33 file

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
the application starts with the given file
ACTUAL -
the above error raises

ERROR MESSAGES/STACK TRACES THAT OCCUR :
java.io.FileNotFoundException: C:\Dokumente und Einstellungen\User\Lokale Einstellungen\Anwendungsdaten\Sun\Java\Deployment\cache\6.0\46\63ba43ee-13a29ae4 (Das System kann die angegebene Datei nicht finden)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(Unknown Source)
 at java.io.FileInputStream.<init>(Unknown Source)
 at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
 at com.sun.javaws.Main.launchApp(Unknown Source)
 at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
 at com.sun.javaws.Main.access$000(Unknown Source)
 at com.sun.javaws.Main$1.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

REPRODUCIBILITY :
This bug can be reproduced often.

CUSTOMER SUBMITTED WORKAROUND :
uninstall - reinstall - very unsatisfyingly. The users are very angry.

Starting with Windows 7 often removing all x33 nodes in the registry ist the only way to get the application flying again. Assoc shows no association after uninstalling with javaws -uninstall, but it still remains.