The server and express installers for Adobe ColdFusion (release 2016) have been refreshed. The installers are available for download at the ColdFusion product page at The new installer includes the following changes:

  • The API Manager installer is decoupled from the ColdFusion Server installer.
  • The new API Manager installer incorporates certain new features such as multi-tenancy, enhanced security, configurable policies, a dedicated update mechanism and support for Redis cluster and request/response compression. For a detailed description of these new features follow the links embedded in this technote. The API Manager installer would be made available very soon. We will update this post to share the location where the installer would be hosted.
  • The ColdFusion installer incorporates ColdFusion 2016 Update 3 and updates JDK to version 1.8.0_112. For details on the changes that went out with Update 3 refer the Update 3 Release Notes document. The build number for this installation should be 2016,00,03,301771.
  • The features listed below have been retired from the product and no longer ship with ColdFusion. For a detailed overview of the affected areas, refer the "Portlets" and "YUI and Spry" sections of the coldfusion-deprecated-features technote. In case you need to use any of these libraries you can download them from locations mentioned below.
    • Portlets. download (md5 checksum : 93273a7b4ab8c650e5fa9cece518e099);
    • YUI. download (md5 checksum : 827e0f8395d176ac28f46ed5e78004fd);
    • Spry. download (md5 checksum : 750c275c20b291f00c1ba92c855a09d7).

 To integrate the downloaded library, follow the instructions below:

  1. Stop ColdFusion sever.
  2. Download the libraries from the links mentioned above.
  3. Extract the downloaded files to the following locations:
    • Extract file to <cf_root>/cfusion directory. Update the web.xml file at <CF_HOME>/cfusion/wwwroot/WEB-INF to re-introduce the mappings mentioned in the "Portlets" section of this technote.
    • Extract and to ColdFusion's webroot at <cf_root>/cfusion. If your scripts directory is mapped to a non-default location (setting at CF admin > Settings > Default ScriptSrc Directory), unpack the zipped package manually and place it in the custom location following the structure in the package.
  4. Restart ColdFusion server.

If you are restoring just the YUI or Spry libraries, restarting the ColdFusion server is not required.


20 Dec, 2016 -  added the web.xml mappings step in restoring portlets instruction. added reference to coldfusion-deprecated-features article.



18 Comments to “ColdFusion 2016 installer refreshed.”

  1. Charlie Arehart
    Great to see this new CF2016 installer, first for the unbundling of the API manager (reducing the CF installer back to its normal size) and for the incorporation of update 3 and the jvm update.

    But did support for Windows Server 2016 make it into this refresh also? I thought adding win2k16 was another reason for needing a new installer (discussed in other recent blog post comments).

    If it got pulled, any estimate of when it's expected? If it made it, could the blog post and technote be updated to reflect that?

    Thanks as always for the efforts.
  2. Aaron Neff

    Finally. NOW we're talkin'!!

    Thanks Adobe!!,
  3. Adam Cameron
  4. Piyush
    We don't yet have support for Win Server 2016. We are still working on sorting out some issues with using that platform. And, I'm afraid I don't have a timeline for the support for now.

    Your views and suggestions are always appreciated. We'll look forward to some feedback from you on that and the other new features.
  5. Leith
    You show how to add Portlets/Spry/YUI to a new installation from the fresh installer but what's the proper process to go about removing these from a CF 2016 Gold installation that's been patched to CHF3?
  6. Gary F
    I'm pleased the API Manager has been removed but disappointed that Win 2016 still isn't supported. I'm holding off buying new CF licences until it's supported, but if we have to deploy onto 2012 then we will be stuck with 2012 for 5 years. Will you announce 2016 support in this blog as soon as it's available? Thanks.
  7. Poonam
    We do not recommend removing Portlets manually from CF 2016 installation that is patched to CHF3 because we have jar dependency which can break the sever.
    As for the YUI/Spry libraries, you may simply remove the js/css/image files from your CF webroot, that correspond to the files in the YUI/Spry package available for download in this post.
  8. Freelance Coldfusion
    Do you expect Windows 2016 support ?

  9. Chris Pittillo
    Where's the API Manager installer?
  10. Piyush
    You can download API Manager from the CF product page at Click on the free trial link, The APIM downloads appear at the bottom of the user details input form.

    Freelance Coldfusion,
    We don't have a timeline on Windows 2016 support yet.
  11. Gary F
    A post in the Adobe forums says the issue with Windows Server 2016 installation is with a known bug in the Flexera installer, not with CF itself. If the CF product team download the latest version of Flexera and update the CF install package it should work.
  12. Charlie Arehart
    Gary, it's possible that there's more to the CF team's "full support of Windows 2016" than just that installer issue. And I'd think it's likely "more to it" or, as you say, they could have resolved this some time ago as InstallAnywhere (from Flexera) has supported Windows 2016 for a few months.

    Let's see what they may have to say in reply.
  13. Kama
    That's nice that there are threads and blog posts about the Windows Server 2016 issue, but I have been unable to find the issue at I'm not familiar with how the ColdFusion community normally handles these things, but this seems strange to me and irresponsible of both parties to not place known issues there. However, since it is not even selectable under System I'm not even sure how you appropriately could represent it.
  14. charlie arehart
    Kama, if you mean that you don't see a means to pick, in the CF bug tracker, the choice of Windows Server 2016 as an OS, that's because they still don't support CF2016 (or any CF edition) on Windows Server 2016.

    The comments above show some of us asking about that and the only answer so far is that they "don't have a timeline on Windows 2016 support yet." That was Jan 10.

    It is surely lamentable that now 4 months to day since its release (Oct 12 2016) we still don't see a CF2016 installer for Windows 2016. Sadly, it's been pretty typical, whenever there's been a major new OS (Windows, Mac, or other). No point in mentioning that OS previous may have existed for months or indeed years. For whatever reason, the CF Teams' stance seems to be that they don't attempt things on previews (I could be wrong there, and perhaps they'll speak up).

    As for what one can do now, I commented above how the real showstopper for most is that the installer fails--and that's because the installer has an embedded JVM which doesn't support the new OS. There are ways to extract the installer files and run it by pointing it to an updated JVM (that does support Windows 2016).

    But again I understand the frustration of those who don't think they should have to jump through such hoops, and that Adobe could/should do a better job of at least clarifying here a timeline for support--if not a commitment to try to also speed up such "new OS" support in the future.
  15. Brian S
    I've just installed Update 3, and it's showing as build 2016.0.03.300466.

    This matches the note at the top of :


    If you are using API Manager and are on ColdFusion (2016 release) Update 3 build 300357, we recommend that you uninstall this build, rollback till ColdFusion (2016 release) Update 1 build 2016,0,01,298513 , and then apply Update 3 build 2016,0,03,300466."

    But it's in direct conflict with the note at the bottom of the page:
    "After applying this update, the ColdFusion build number should be 2016,0,03,301771."

    We went from Update 1 to Update 3 directly, on a test server.

    Update level shows: "Update Level I:/CF2016/cfusion/lib/updates/chf20160003.jar"

    Which should it be? 301771 or 300466?

    Additionally, the "download and install" option for updates never works for us. I've posted about this before but have never received any actual support about it. We've installed CF into a separate partition (I:) instead of the default (C:), according to the security lockdown guide. (We also have L: for logs and W: for the actual website .)

    The installation directory has write permissions for everyone and I can't find any log about the actual "download and install" process. I always end up having to stop the services, perform the update manually (stop server, java -jar update.jar, upgrade connector, start server, verify update level & build number).

  16. Charlie Arehart
    Brian, I can confirm that on installing CF2016 from the updated installer releases in Dec 2016, which comes with update 3 included, the version ends with 301771.

    You say that you see 300466. I'm curious: is that from you having applied the update yourself? Maybe that version number refers to some other variant of update 3. I notice two listed at the page listing updates for 2016: The pages they link to don't indicate the different versions.

    Perhaps Adobe can help clarify things.

    BTW, you mention your problems running the automated installer in the Admin. It may not be a "permissions" issue (I know some resources, including from Adobe, mention that). My experience (helping people with this weekly) is that rather it's that the CF services don't STOP, before the update process tries to PROCEED, and due to locks on files leaves things incomplete.

    Finally, you refer to not being able to 'find any log about the actual "download and install" process'. Well, there's none about the "download" step, but there is indeed one about the install step.

    The problem is that many either miss it, or look at the wrong one, or they don't look in the right place in the right one. It will tell you if and why there are any errors during the update, and I expect you'll find your explanation there.

    The good news is that in most cases, the "solution" in such cases is to do what you did: stop CF yourself, and run the installer jar from the command line. (Or you could find out why CF is taking so long to stop.)

    I talk about all this in more detail in a post I did:
  17. Brian S
    Yes, 300466 is from applying the update myself. Downloading the update from the update page also lists that version number. I'm not sure why there's a discrepancy.

    The log includes these lines:

    Moving files failed:
    Status: FATAL ERROR
    Additional Notes: FATAL ERROR - Could not move the file I:\CF2016\cfusion\lib\updates\chf20160001.jar to the backup location I:\CF2016\cfusion\hf-updates\hf-2016-00003-300466\backup\lib\updates\chf20160001.jar

    Moving files failed:
    Status: FATAL ERROR
    Additional Notes: FATAL ERROR - Could not move the file I:\CF2016\cfusion/lib/xmpcoreold.jar to the backup location I:\CF2016\cfusion\hf-updates\hf-2016-00003-300466\backup/lib/xmpcoreold.jar

    Failed to delete directory
    Status: ERROR
    Additional Notes: ERROR - Failed to delete directory:I:\CF2016\cfusion/lib/xmpcoreold.jar
    ERROR - Unable to delete file: I:\CF2016\cfusion\lib\xmpcoreold.jar

    CF should have full access to I:, but I hadn't considered the files being locked and the service not stopping in time. I can watch for this the next time I have to update. But if the solution is to stop the services manually, I may as well update manually as well.

  18. charlie arehart
    Thanks for the update, Brian, and glad to have helped.

Leave a Comment

Leave this field empty: