Exchange 2013 CU14 Released

Exchange 2013 CU14 has been released to the Microsoft download centre!  Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one.  Exchange 2013 SP1 was in effect CU4, and CU14 is the tenth post SP1 release.

Exchange 2013 CU14 Download

This is build 15.00.1236.003 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu14.exe.  Which is a great improvement over the initial CUs that all had the same file name!  Details for the release are contained in KB 3177670.

Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post.  There may be additional RBAC definitions, so PrepareAD should be executed prior to installing CU14.  If setup detects that PrepareAD is required it will be automatically executed if the account running setup has the necessary permissions.  This was an issue discussed in the MessageCopyForSentAsEnabled  post.

Updates Of Particular Note

Exchange 2013 CU14 contains the security fix for MS16-108- Security update for Microsoft Exchange.

In addition the latest time zone updates are also included with CU14.

Exchange 2013 servers are no longer unexpectedly marked as offline.  Using the setup wizard to upgrade an Exchange Server to a newer Cumulative Update causes an Exchange server to be marked offline in Exchange Active Monitoring during prerequisite analysis and prerequisite installation. If the setup wizard isn't advanced to continue the upgrade process, the server will remain in an offline state until the setup is allowed to proceed. Also, if any of the setup /Prepare* switches are used to update Active Directory on a functional Exchange Server, the server is marked offline in Exchange Active Monitoring.


Exchange 2013 CU14  has not changed the current support stance for .NET framework.  CU14 supports for .NET framework 4.6.1.

Issues Resolved

KB 3132513 "The Delegates settings were not saved correctly" when you try to add a user to Exchange Server 2013 from Microsoft Outlook

KB 3172017 "NotFound Export failed with error type: 'NotFound'" error occurs when you perform an eDiscovery search in Exchange Server 2013

KB 3176377 Links to access Exchange items in SharePoint eDiscovery search result fail with an HTTP error 500 in Exchange Server

KB 3176540 OWA error reporting responds with a HTTP error 500 in OwaSerializationException

KB 3176873 Can't create a new profile or connect to Exchange Server 2013 when an organization contains many address lists

KB 3061079 RPC Client Access service crashes and Event 4999 is logged in Exchange Server 2013

KB 3134918 An IRM-protected message sent to an external contact isn't returned in a search or discovery results when journaling is implemented in an Exchange Server 2013 environment

KB 3190887 Upgrading Exchange Server causes the server to go offline unexpectedly


Some Items For Consideration

As with previous CUs, CU14 follows the new servicing paradigm which was previously discussed on the blog.  The CU14 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU14.  You do not need to install Cumulative Update 4 or 5 for Exchange Server 2013 when you are installing CU14.  Cumulative Updates are well, cumulative.  What else can I say…

  • After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2013. If you uninstall this cumulative update package, Exchange 2013 is removed from the server.
  • Place the server into maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
  • Restart the server after installing the CU
  • Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, backup, mobility and management services.
  • Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter.
  • Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.  See KB981474.
  • Disable file system antivirus prior to installing.
  • Once server has been restarted, re-enable file system antivirus.
  • Note that customised configuration files are overwritten on installation.  Make sure you have any changes fully documented!
  • While CU14 does not add any new AD Schema changes, if you are on an out-dated CU currently then deploying CU14 may contain AD Schema updates for your organisation – please test and plan accordingly!  Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post.

Please enjoy the update responsibly!

What do I mean by that?  Well, you need to ensure that you are fully informed about the caveats with the CU  and are aware of all of the changes that it will make within your environment.  Additionally you will need to test the CU your lab which is representative of your production environment.




Comments (48)
  1. Kate Paulin says:

    If MS16-108- Security update for Microsoft Exchange patch has already been installed on the exchange server, do we need to uninstall it before installing CU14

    1. Hi Kate,

      No need to uninstall, setup should take care of this for you.


  2. Randy Lefebvre says:

    We had a client install patch, and Exchange pretty much died. OWA/ECP and the Exchange Management Shell all come up with a “500 – Internal server error.” and mail flow doesn’t work. At this moment, troubleshooting has failed, and we’re getting ready to restore a backup.

    1. PaulW says:

      Randy, was this only the CU14 patch? Or was it combined with regular security patches. I’m asking, as this sounds like MWF 5.0 may be installed. (PowerShell 5.0 does not play nice with Exchange (yet))

      1. Randy Lefebvre says:

        I believe they did the whole patch routine. I’ll see if we can dig in and find out. Thank you.

        1. Randy, are you able to open a case so we can take a look at what is happening?

          One of the MVPs posted this yesterday

          And in the 2016 forum, I see the below thread:

          Does that match your symptoms?


          1. Randy Lefebvre says:

            One of our techs has a case open with Microsoft (1160922147031773) and is muddling through it. It looks like KB3184736 was not installed.

            Both ECP and OWA are dead, and the Exchange management shell does not connect. Part of the error it throws is “The WinRM client received an HTTP server error status (500)”

            Mail flow is dead in the water. Fortunately, their spam filter service has an emergency mailbox, so there’s a silver lining.

          2. Randy Lefebvre says:

            Just an update. Microsoft fixed the problem after 2 days. It ended up being a corrupt XML file in IIS. Unfortunately, since this CU was installed, The Microsoft Exchange Search Service continues to fail every few minutes, and we appear to not be alone with this one:

  3. Young C says:

    Where do you have the information, that CU14 contains security patch MS16-108? Could you provide a link, please? I cannot find anything about MS16-108 containing in CU14 under this link:


      Note that only CU4, CU12 and CU13 are listed as updates for Exchange 2013.


  4. Adam says:

    Hi. I’m on CU9 still so if I update to this version do I still have to uninstall that KB update which slows the installation on Windows 2012 R2 servers? What I’m talking about was referred to in a couple updates prior. I’m just not sure if that was fixed for CU14. Thanks!

    1. Hi Adam,

      Good question. That is not specifically an Exchange issue, it is a .NET issue. The below are the note on this:

      Slow installations on Windows Server 2012 R2
      For customers who are running Exchange on Windows Server 2012 R2, we want to make certain you are aware of a condition which can substantially increase the amount of time it takes to install Exchange Updates on this OS. Working with the .Net team, we have discovered that systems which have applied Windows Update KB3097966 can take 50% more time to install Exchange. The .Net team is working on a resolution to this and will include a fix in a future product update. In the meantime, customers who have deployed this Windows update can take a one-time action on their server before installing Exchange or a Cumulative Update to bring installation time back to normal. This procedure needs to be done once on every Exchange server running Windows Server 2012 R2. The command to execute is:
      “%windir%\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update”


  5. Fred Proos says:

    After upgradeing our Exchange 2013 to CU14 we encounterd following problem:
    Messages that were sent to public folders after the upgrade are not indexed.
    Meaning if i perform search in public folder it only returns messages that were sent before the upgrade
    The problem occurs both in OWA and Outlook.
    When i check databasecopy status, it shows index as healthy. Ive tried to reseed the indexes but no results.
    There are no problems with regular user mailbox indexing. Problem appears to be only in public folders.

    1. J. Stefka says:

      Same problem here. Have you found any information how to fix this issue?

    2. Lars Lindberg says:

      Same problem here also. Users can´t search the new items in Public folders.
      Has anyone got a tips from MS how to fix this?


      1. laurie says:

        Also having same problem with public folder search after upgrade.
        Any news of a fix?

        1. Lars Lindberg says:

          Have anyone heard if MS is working on a solution?

          1. Fred Proos says:


            We have not found a solution yet. We have opened ticket to premier support. When we get solution i post it here


          2. PepC says:

            The Database Indexing issue is a real showstopper for us because we use Public Folders for project email archiving purposes so we frequently search them. We just migrated from Exchange 2010 to Exchange 2013 CU14. Does Microsoft release hot fixes between Exchange CUs or should we wait for Exchange 2013 CU15? Also, if our DB was created by Exchange 2013 CU14, is it an option to uninstall Exchange 2013 CU14 and then install Exchange 2013 CU13 using the same DB created with CU14 or such downgrade might corrupt the DB?

            1. I do not believe that there were DB schema changes in there, but not something I specifically have looked for.

              Can you please open up a case, as the support teams will need to gather data and to track this.


        2. bostjan cvelbar says:

          We have same issue. CU14 breakes search in public folders.
          Its 22th november today, no fixes yet?

          1. Johnathan Huettner says:

            Why in the world would the Exchange team leave CU14 online with this as a known issue?? Just getting ready to install CU14, lucky I saw this thread!

  6. Tomasz M says:


    what steps should be taken to install CU14 when the .net framework 4.6.1 is already installed on Windows Server 2012r2 and Exchange 2013 has CU11?


    1. Hi Tomasz,

      I doubt that will have been tested since it was Exchange 2013 CU13 which added support for .NET 4.6.1.

      It was recommended that the CU13 update was installed prior to installing .NET 4.6.1


      1. Tomasz M says:


        Thanks. So we need to uninstall .net framework 4.6.1 (rollback to 4.5.2), yes?


        1. Hi Tomasz,

          Again not officially tested/supported. You can try the upgrade to CU13, hopefully should go through. But not something that will have been validated.


          1. Tomasz M says:

            Hi Rhoderick,

            we went to CU13 on exchange servers. I have seen that the matrix been changed – now CU14 support .net framework 4.6.1? We got required hotfix + CU13. From time to time machines are freezing because of high cpu usage. How we can troubleshoot that?



            1. Hi Tomasz,

              I would ensure that you are all up to date.
              Check that AV exclusions are in place, and if this persists then we will likely need a case to review process dumps.


              1. Tomasz M says:

                Thank you for response. All servers have been updated. Our antivirus automatically excludes files and folder from scanning when he detects Exchange installation. I will monitor servers in future.


                1. Hi Tomasz, If that AV is from a vendor with lots of yellow on the webpage, then the autoexclude does not really work nowadays. That was Exchange 2003 based.

                  Always check, and pay particular attention to mount points. They require special configuration.


  7. Ronski admin says:

    After we Upgrade to CU 14 we could not able to access all our on prem shared mailbox.

    1. This is a hybrid deployment? Users in EXO and if so what permissions to the shared mailbox?


      1. Ronski admin says:

        Yes on our exchange server user permission are full access. We can still access the shared mailbox before the upgrade.

  8. JG says:

    I’m having the same issue. Single DB. Index will not work on any new items. Tried to reseed the catalogue and received cycling failures. This seems to be a pretty common issue. Microsoft?

  9. André Mieth says:

    “This is build 15.00.1236.003 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu14.exe. Which is a great improvement over the initial CUs that all had the same file name!”

    Yeah! And filenames for UM-LanguagePacks? 😉

    1. Erm, Not so much….

      2016 has the same format.

      Let me provide that feedback Andre.

      Thanks for the note.


  10. GeoffP says:

    When will this be posted tot he Microsoft Update Catalog (

  11. Andy Lee says:

    We installed CU14 seven days ago and our workstation estate was patched with the latest patches for Office 2013 & Windows 8.1 updates. Since then, random emails have converted into Chinese characters. There doesn’t seem to be a pattern to it – for example 1 user sent an email to 2 colleagues, they both received it fine, but when one of the users opened the email (by double clicking on it) it converted. We have about 20 people report the same thing with different emails. It isn’t all emails, just a few.
    Any ideas??

    1. bostjan cvelbar says:

      We have same issue. CU14 breakes search in public folders.
      Its 22th november today, no fixes yet?

      1. Shawn says:

        The PF index issue fix will be included in CU15. if you run into this problem and need quike fix, you can also request IU (Interim update) for this issue from MS Support team.

        1. Lee Summers says:

          Further to What Andy Lee mentioned, the body of the emails are being replaced with the following string 䠼䵔⁌浸湬㩳塥汣楡敭㵲栢瑴㩰⼯睷⹷硥汣楡敭 this continues throughout the message.

          We are using TITUS and McAfee DLP add-ins.

          Has anyone got any more details on this?

  12. Jerry Warner says:

    If our clients heavily use Public Folders, would it be best to wait for cu15? We currently run Exchange 2013 cu12 and I am trying to decide if I should upgrade to cu13, cu14 or wait for cu15.

    1. Review the security issues that have been addressed in the recent builds Jerry. That may steer you in a particular direction.

      You can wait for CU15, or deploy CU14 – you should be able to call into support and get an IU to install for this issue.


  13. Michael Astrosky says:

    I am on CU10, besides the .NET issues (KB3097966) and not being on .NET 4.6.1 are there any other issues from moving up 3 CU’s

    1. There is also the PF indexing issue. That would drive me to recommend updating to CU15 Andy

      And you want to start planning the .NET upgrade to 4.6.2…….


Comments are closed.

Skip to main content