You may need to install updates via command line. This at least is a major requirement if you run ColdFusion in a locked down environment with limited permissions. In this case the ColdFusion instance runs with a specified windows user account that has very limited permissions on the local system. The user ColdFusion runs under will not be a member of Administrators group. In this case you are unable to run automatic updates via ColdFusion Administrator. The updates will silently fail and the update notification will just not get away in ColdFusion Administrator.
Analysis has shown that the update log has problem in renaming the coldfusion.exe file. This at least happens for Updater 12 if you had no other updates installed. It may be possible that the updates succeed, if this file is not going to be replaced. The root cause of this issue is that the ColdFusion Service user has no Administrator permissions and only Administrators can stop and start Windows services.
First of all create a properties file with all you named instances. For more details see admin guide section Download hot fix for later installation.
[hotfix.properties]
INSTALLER_UI=silent USER_INSTALL_DIR=C:$/$ColdFusion10 DOC_ROOT=C:$/$ColdFusion10$/$cfusion$/$wwwroot$/$ # The following applies only to multi-server scenarios. INSTANCE_LIST=cfusion,myinstance1,myinstance2,myinstance3
Download the hotfix files you need to install. The ColdFusion 10 Mandatory Update cf10_mdt_updt.jar is required before you install any updater hotfixes.
ECHO Upgrade to version 10,283111 C:\ColdFusion10\jre\bin\java -jar C:\Install\ColdFusion\Hotfixes\cf10_mdt_updt.jar -i silent -f C:\Install\ColdFusion\Hotfixes\hotfix.properties REM Wait for Windows services to start up timeout 60 ECHO Upgrade to version 10,0,12,286680 xcopy "C:\Install\ColdFusion\Hotfixes\hotfix_012.jar" "C:\ColdFusion10\cfusion\hf-updates\" C:\ColdFusion10\jre\bin\java -jar C:\ColdFusion10\cfusion\hf-updates\hotfix_012.jar -i silent -f C:\Install\ColdFusion\Hotfixes\hotfix.properties REM Wait for Windows services to start up timeout 60