Cumulative Update 05 for Microsoft Dynamics NAV 2017 has been released

Cumulative Update 05 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2017.

The cumulative update is intended mainly for solutions that are experiencing the problems described in the Knowledge Base article linked to below. However, you are advised to always keep your solution updated with the latest cumulative update. If you are in doubt about whether this cumulative update addresses your specific problem, or if you want to confirm whether any special compatibility, installation, or download issues are associated with this cumulative update, support professionals in Customer Support Services are ready to help you. For more information, see

The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

Where to find Cumulative Update 05

You can download the cumulative update from KB 4018437  – Cumulative Update 5 for Microsoft Dynamics NAV 2017.

You can press one of the countries in list above for a direct download or you can download the cumulative update from the Microsoft Download Center.

To learn more about other Cumulative Updates already released for Microsoft Dynamics NAV 2017 please see KB  3210255.


Before you install a cumulative update in a production environment, take the following precautions:

  1. Test the cumulative update in a non-production environment.
  2. Make a backup of the system or computer where the cumulative update is to be installed.
  3. This Cumulative Update will require a database upgrade.

Additional Information

For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2017 Cumulative Update.

Comments (13)

  1. Johannes Sebastian Nielsen says:

    But no news on the memory leak problem? A 2017 service easily consumes 1GB RAM upfront. This becomes a problem when you maintain a large number (Cumulative updates) services for ISV release purposes…

    1. Same here too. Yesterday one service alone took itself 1.7 GB used by a single developer doing nothing special, causing extremely slow response times and page build-up. Due to this massive consumption, even the debugger would not start anymore.

    2. Lasse Jensen says:

      By default the NST compiles and loads the entire business application to prevent the sluggishness when the first user connects to the NST.
      Thats what is causing the memory usage.

      You can change this by setting the key “CompileBusinessApplicationAtStartup” to false in the CustomSettings.config

    3. Arjan Hollebrandse says:

      You have to disable the setting ‘enable debugging’ as well, otherwise the application objects will be compiled and loaded anyway.

      1. Yes, but for ‘EnableDebugging’ false is the default setting (not to be confused with ‘DebuggingAllowed’ which is set to true) . ‘EnableDebugging’ was introduced in NAV 2009 which did not have a debugger for C/AL when used with the RTC, so debugging the C# source code was the only possibility.

  2. Dave Saman says:

    The CU bricked the ‘Create order’ functionality from a sales quote (BE version).

  3. NavAdmintool.ps1 on (at least DK, NL and DK) are the wrong version. Included is 10.0.15052.0, should be 10.0.16177.0

    1. Never mind.. Should not load ps1, but Microsoft.Dynamics.Nav.Management.dll for scripting…

  4. J Leite says:

    We noticed that installing CU3 in a O.S. previous to Windows Server 2016 (e.g. 2012) wasn’t that bad. When using Windows Server 2016 we also noticed that even with client services, SOAP, OData and NAS – all disabled in the NAV instance, the memory consumption tended to go dramatically up after starting the instance (zero users logged).

    1. In addition to the changes in NAV 2017, there is a known memory leakage issue in Windows Server 2016 (in KB3216755) which you might experience. Several hotfixes have been released after this issue was found so you should update Windows Server here just to be sure that you don’t run into this issue. Hotfixes can be found here: Also another memory leakage in SQL Server 2016 exist which might affect you, see:

  5. I posted something 11 days ago (April 13th at 12:00) in reply to Arjan which is still not showing up here due to a line indicating ‘Your comment is awaiting moderation.’

  6. Ewald Venter says:

    Suggested edits:

    Codeunit 448:
    + Allow indirect insert permission for “Job Queue Log Entry”
    Codeunit 1514:
    + Allow indirect insert permission for “Sent Notification Entry”
    + Remove indirect permission for table 1510 (doesn’t exist)

    1. To_Ewald says:

      Please report this on Microsoft Connect or on yammer. This might not be seen as the blog-post is “old”.

Skip to main content