The ColdFusion 10 Update 4, released on November 2 2012, includes several important bug fixes. ColdFusion 10 Update 4 is a cumulative update. It includes all the bug fixes from previous updates of ColdFusion 10. All the issues reported in Update 3 have been resolved in this update. Adobe recommends that you apply this update to ColdFusion 10.

Note: This update is specific to ColdFusion 10; do not apply it to any previous versions of ColdFusion.

Prerequisites

1. If you have not already applied ColdFusion 10 Mandatory Update, apply it first.
2. On 64-bit computer, use 32-bit JRE for 32-bit ColdFusion and 64-bit JRE for 64-bit ColdFusion.
3. If the ColdFusion server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties below in the jvm.config for a stand-alone installation, or corresponding script file for JEE installation.
   • http.proxyHost
   • http.proxyPort
   • http.proxyUser
   • http.proxyPassword
4. For ColdFusion running on JEE application servers, stop all application server instances before installing the update.

Install ColdFusion 10 Update 4

For instructions on how to install this update, see Server Update section.

Note: Microsoft Windows 7 and Microsoft Windows 2008 users must use the “Run as Administrator” option in the above operating systems to install either through the Administrator module or through the command-line option.

• The update can only be installed from the Administrator of a ColdFusion instance. To apply the update to individual instances, run the installer from the command prompt. Microsoft Windows users can run the Administrator module using Start>All Programs>Adobe>Coldfusion 10>Web Server Configuration tool or install using the ColdFusion Administrator of the ColdFusion instance. Then, when prompted, select the instance to apply the update. The update is applied to the main instance as well.
• After applying the update, reconfigure the connectors using wsconfig tool. It is in{cf_install_home}/cfusion/runtime/bin.
• You can encounter a Signature Verification Failed error when downloading and installing this update. To resolve this issue, download and install the ColdFusion 10 Mandatory Update first, before installing ColdFusion 10 Update 4. For more information, see this article. If this error persists, then download ColdFusion 10 Update 4, afresh. This error is primarily due to certain issues with download.
  
• If you get the following error when installing the update using the Download and Install option, ensure that the folder {cf_install_home}/cfusion/hf_updates has write permission: "An error occurred when performing a file operation write on file {cf_install_home}/cfusion/hf-updates/hotfix_004.properties"

Uninstall ColdFusion 10 Update 4

To uninstall the update, do one of the following:

• In ColdFusion Administrator, click Uninstall in Server Update > Updates > Installed Updates.
• Run the uninstaller for the update from the command prompt. For example, java -jar {cf_install_home}/{instance_home}/hf_updates/hf-10-00004/uninstall /uninstaller.jar

If you can't uninstall using the above-mentioned uninstall options, the uninstaller could be corrupt. However, you can manually uninstall the update by doing the following:

1. Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
2. Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-10-00004}/backup directory to {cf_install_home}/{instance_name}/

Remember

1. In the ColdFusion Administrator, if you see the update listed in both Available Updates and Installed Updates, it could be a caching issue. Do the following:
   1. Navigate to Server Update > Updates > Available Updates and check Check For Updates.
   2. Press Ctrl+F5 to remove the bulb notification from the top banner of the ColdFusion Administrator.
2. If ColdFusion server doesn't start automatically (grep command indicates ColdFusion is running, but the ColdFusion Administrator cannot be accessed), restart the server manually after applying the update. This issue is rare and occurs on few *INX-based operating systems (when buffer allocation size of the machine console is almost zero).