This cumulative update package for Microsoft BizTalk Server 2016 contains hotfixes for the BizTalk Server 2016 issues that were resolved after the release of BizTalk Server 2016.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included in the previous BizTalk Server 2016 update release. We recommend that you consider applying the most recent BizTalk Server 2016 update release.

  • Each cumulative hotfix package includes all the component packages. However, a cumulative update package updates only those components that are installed on the system.

Note For more information about the latest service pack or cumulative update package for BizTalk Server, see the following article in the Microsoft Knowledge Base:

2555976 Service Pack and cumulative update list for BizTalk Server 

Note If you use the MQSeries adapter, MQSAgent.dll must be updated on the IBM WebSphere MQ server to the same cumulative update level that's on BizTalk Server. To do this, make sure that you run the same cumulative update setup on the IBM WebSphere MQ server. You may experience performance issues if you run mismatched versions.

This cumulative update package is a rollup update that contains the following items:

  • All new hotfixes that were released for BizTalk Server 2016

  • Other fixes that improve the product

For more information about the terminology that's used to describe Microsoft product updates, see the following article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Hotfixes that are included in cumulative update package 6 for BizTalk Server 2016

The Microsoft Knowledge Base articles that discuss these hotfixes are published as the hotfixes become available. For more information about the BizTalk Server issues, see the following articles in the Microsoft Knowledge Base. 

BizTalk Server Adapter

KB article number



FIX: Cumulative Update 5 for BizTalk Server 2016 breaks SAP NCo Receive Adapter functionality


Improvement: Add read-only download options for SFTP adapter in BizTalk server


FIX: Missing iDOCs or receiving duplicate iDOCs from multiple SAP servers in BizTalk Server


FIX: Changes to Key Exchange algorithm in receive locations, send ports and host handlers is not persistent in BizTalk Server SFTP adapter


FIX: SAP receive location will stop receiving subsequent incoming IDOCs after host instance receives wrong transactional IDOC


FIX: Exception error occurs when Dynamic SFTP port runtime uses '-1' instead of '22' as default port in BizTalk Server


FIX: SAP NCo new build 3.0.21 is supported by CU6 for BizTalk Server


FIX: E_INVALIDARG error occurs when POP3 adapter is used to receive mail that has part name >256 characters or attachment name is base64 encoded


FIX: Duplicate files received by SFTP adapter when long time is taken for message processing in BizTalk Server


FIX: BAPI transactions are not committed when using WCF-SAP NCo connector type in BizTalk Server

BizTalk Server Design Tools

KB article number



FIX: Error occurs when you open or create BizTalk project in Visual studio due to unsigned assembly in Biztalk server


FIX: Visual Studio is unable to deploy BizTalk project to SQL Server when there is unrelated database >2TB on the same SQL Server with BizTalk Server

BizTalk Server General

KB article number



FIX: Moving databases with UpdateDatabases.vbs script will fail in BizTalk server


FIX: Event view error occurs if separate users and groups are used for different roles after you upgrade BizTalk Server with Feature Pack along with CU 5 (or any previous CU)


FIX: Marklog rows are not cleaned in BizTalk Server by documented custom stored procedure


FIX: Support not available for BizTalk Server Feature packs on 32-bit machines

BizTalk Server Runtime, Pipelines, and Tracking

KB article number



Improvement: Configure DTD Processing inside XML Disassembler pipeline component

BizTalk Server Setup and Configuration

KB article number



FIX: BizTalk 2016 Cumulative Update fails as CU requires SQL Server 2012 Native Client to be installed in the server


FIX: Error occurs when Microsoft.BizTalk.Analytics.Common assembly is not available in the GAC of BizTalk Server

How to get cumulative update package 6 for BizTalk Server 2016

BizTalk Server uses a cumulative update (CU) model for providing fixes and updates. Each cumulative update includes new updates in addition to all the updates that were included in previous cumulative updates. We recommend testing and then applying the latest CU to all BizTalk environments.

All new fixes are publicly released in the upcoming cumulative update. Stand-alone fixes may be provided before the next cumulative update if the reported problem is very important, has a significant business effect, and doesn't have a workaround. If stand-alone fixes are provided, they require the latest released cumulative update as a prerequisite.

Download Center

The following file is available for download from the Microsoft Download Center:

Download Download Cumulative Update 6 for BizTalk Server 2016 now

Download Download BizTalk Server 2016 Feature Update 3 with CU6 now

Release Date: March 1, 2019 

For more information about how to download Microsoft support files, see how to obtain Microsoft support files from online services.

Microsoft scanned this file for viruses by using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!