Dreamweaver CS5 update apparently fixes Mac FileVault problem

Question

Adobe has just released Dreamweaver 11.0.2 (build 4916), which is intended to fix the problem with running Dreamweaver CS5 on Mac OS X with FileVault enabled. Adobe Updater should automatically detect the update, and display the Adobe logo in the menu bar at the top right of the screen on a Mac. Click the logo, and select Adobe Updater. Alternatively, select Help > Updates in Dreamweaver.
I don't use FileVault, so can't verify that the update fixes the problem. Hopefully, it does.

Answer 1

I was getting the same error message on both Windows 7 64-bit as well as XP 32-bit.  When CS5 Dreamweaver installs (and several other Adobe CS5 products) it includes an older version of the Java 1.6 Runtime Environment which has known serious security flaws.  My university's computer security people got a report from Secunia PSI that I was running vulnerable software (an older version of Java) and demanded that I immediately upgrade. 
But I do have the latest updates of the JRE installed, so I was puzzled by this.  When I looked at the Secunia report, the JRE culprits were installed in the Programs\Adobe folders as part of each application such as Dreamweaver (and several others).  So I removed the insecure JRE folders under those program installations and replaced them with the updated JRE folder from the Java installation (JVM for DW). Granted, this was a bit of a gamble since the registry was not modified, but I had not experienced any problems until I kept getting the installation failure reported here for the CS5 DW update failure with no explanation.
Realizing that Dreamweaver is still a 32-bit app even when running on 64-bit Win 7, and I was running the 64-bit version of Java 1.6 v20, I thought I should have used the 32-bit version of Java to replace the insecure version installed under Dreamweaver.  I tried that, as above, but the DW CS5 update still failed.
Then I tried to reinstall CS5 Dreamweaver only, which succeeded with the older insecure JRE which then immediately got flagged by Secunia PSI.  Furthermore, the Dreamweaver update still failed with no explanation.  I noticed that some of the previous Java files (by their dates) were still left in the DW installation JVM folder, after the re-install.  So next I removed the entire Program Files (x86)\Adobe\Dreamweaver CS5 folder, and did a clean reinstall of Dreamweaver CS5 only.  It was immediately detected again by Secunia PSI as have an insecure version of JRE.  However, this time when I did the Dreamweaver update, it succeeded (v11.0 build 4916) on my 64-bit Win 7 machine.
So the choice currently appears to get Dreamweaver CS5 updates with an older insecure version of the JRE or
not get Dreamweaver updates but be secure with the latest JRE manually installed.  My university security people will not tolerate the former
I don't understand why Adobe does not put the latest JRE's as part of their standard updates.  Moreover, why put them in the Adobe installations at all--which is causing this security problem of older insecure JRE's--and instead use the main Java installation on the user's machine (and if absent, require users to install Java), if Java is really needed.