ColdFusion 2016 : Support for Windows Server 2016

We have updated the Windows 64-bit installer for ColdFusion 2016, to support Microsoft Windows Server 2016. The Add-on services installer and the .NET service installer for ColdFusion 2016 have also been refreshed.
You can access the server installer by clicking on the "free trial" or the "buy now" link in the ColdFusion product page at You may download the aforementioned additional installers at the ColdFusion support page

The ColdFusion 2016 support matrix would be updated soon to reflect the support for the new platform.

The refreshed installer comes with the Update 3 baked-in. After installing the server, you may bring it up to the current update level, by installing Update 4. You can follow the instructions at this technote to download and install Update 4. If you need any help with installing ColdFusion server you may refer the installation instructions at this technote.

The installers for ColdFusion Builder 2016 and ColdFusion API Manager would soon be refreshed to support Windows Server 2016.

20 thoughts on “ColdFusion 2016 : Support for Windows Server 2016

  1. Anton,
    As noted in the post, refreshing the Builder installer is due. I don’t have a date yet, but it should be sometime in the current month.

    Updates are cumulative, so you would only need to apply the latest to apply them all.

  2. Will the ColdFusion 2016 support matrix be updated to reflect this change? Will ColdFusion 11 also support Windows Server 2016 soon?

  3. HariKrishna Kallae,

    Here is a link to one that has not be updated:

    This link can be found at the bottom of as “ColdFusion Support Matrix”.

    I also see it missing from the text at and

    By the way, the one you linked seems to have an issue where the first two tables are missing the line at the top that states “Standard” and “Enterprise”.

  4. Kama,

    Thanks for pointing it, we will get this updated.
    Regarding the issue of Standard and Enterprise not shown in the columns, doc team is working on it and would fix it in a couple of days.

  5. David,
    We can observe the issue noted in that bug report. Investigation and fix for the bug is targeted for the next update release.

  6. Yet another business day of May 22 coming. Still no CF Builder for Windows Server 2016. However runs on Windows 10 that makes most customers be satisfied. Ridiculous.

  7. Charlie, the answer is simple. It is convenient to me to develop, learn, and run both CF2016 and CFBuilder2016 on Win2k16 because it has a real IIS webserver within with all the true server tools and environment on board. Yes, a kind of desktop-like true Windows Server without emotional or novice user stuff. I love server edition a lot and use this branch for many years on a daily basis.

  8. Anyone else notice poor logging in IIS 10 and ColdFusion 2016?
    Specifically the fact that now EVERY .cfm request is being logged as /jakarta/isapi_redirect.dll in the cs-uri-stem field? Anyone have a fix?

    There is a thread here:

    I feel like I am the only one struggling with this. Let me know if you experience this too.


  9. @BeekerMD03: I see the same issue in my Windows 2016 logs. Every CFM request shows as “/jakarta/isapi_redirect.dll”, PNG and other stuff works as before. Have you already created a bugcase?

  10. Hi,
    As we are going to upgrade the Window server soon could piyush please confirm that
    we can use CF2016 on Windows Server 2016 without issues? Or otherwise, we have to use Windows Server 2012 for this stage?

  11. Joe, do you really need Piyush alone to confirm for you?

    I’m not really understanding why you are even asking for confirmation. The whole point of this blog post (from April 2017) was to tell us that YES, CF2016 (as of then, by way of the new installer released that day) does now support Windows 2016. So it’s not clear why you are wondering if you “have to use Windows Server 2012 for this stage”.

    Am I misunderstanding something? I see no prior comments from you to explain your question, nor any from others. To be clear, you MUST use the new installer that was released then (and is available now). If you may be trying (or read of others) trying to use the original installer, that came out in early 2016, that one DOES NOT support installation onto Windows 2016 (due to issues with the installer software, more than anything).

    Let us know if this clarifies things sufficiently for you, or not.

    • Thanks for reply.
      We just want to make sure when we upgrade to Windows Server 2016
      we can use CF2016 on the server. That’s it.
      So now we can go ahead to install Win2016 and CF2016.


Leave a Reply

Your email address will not be published. Required fields are marked *