Something to try:
1.Run the installer again, and have it fail.
2. Use File Explorer and navigate to "C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\" There should be a folder created recently similar to the Java version/update you were installing. Java 7 update 45, for example, would be jre1.7.0_45. You should be able to just sort by date modified and find the latest one.
3. Inside that folder, there should be a file with a ".msi" file extension. (Of course file extensions need to be on; the 'Type' should be listed as "Windows Installer" or something similar.)
Determine the full path to this file.
4. Now open Start->Run, and try this. Be sure to replace the first segment with the path you determined!
"C:\Path\To\File\installer.msi" /fa REBOOT=ReallySuppress IEXPLORER=0 MOZILLA=0 JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0 /qn METHOD=joff REMOVEEXISTING=0
Explanation: Java has had a ridiculous and annoying bug in it's installation script for almost 4 years now. Effectively what happens is the installer finds a key that indicates Java is installed, but then when it looks further it finds it isn't, but at that point it panics and doesn't know what to do. The reason it looks for previous versions is because it typically tries to uninstall/remove them if they are an update to that version. The executable you run normally to install Java effectively just unpacks a few files and runs that msi that it unpacked, but if it exits due to the error those files stay around. This approach effectively tries to run it again, but this time specifying "REMOVEEXISTING=0" to tell the installer to not look to remove existing versions, which should sidestep the problem in most cases.