Cumulative Update 1 for Microsoft Dynamics NAV 2016 has been released

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

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:

  •   AU – Australia
  •   AT – Austria
  •   BE – Belgium
  •   CH – Switzerland
  •   CZ – Czech Republic
  •   DE – Germany
  •   DK – Denmark
  •   ES – Spain
  •   FI  – Finland
  •   FR – France
  •   IS – Iceland
  •   IT – Italy
  •   NA – North America
  •   NL – Netherlands
  •   NO – Norway
  •   NZ – New Zealand
  •   RU – Russia
  •   SE – Sweden
  •   UK – United Kingdom

Where to find Cumulative Update 1

You can download the cumulative update from KB 3106089 – Cumulative Update 1 for Microsoft Dynamics NAV 2016 (Build 43402).


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.

Additional Information

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

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2016.


Comments (38)

  1. Are Modifies on temp variables still hitting GetDatabaseTableTriggerSetup in CDU1?
    That’s a massive perf regression for us.


    1. Just to clarify:

      For us every Modify on any temp record executes a call in GetDatabaseTableTriggerSetup in CDU1.
      Inside this trigger there is no way to detect if it was raised by temp record or real physical record.
      This makes it hard to skip normal Changelog behaviour and results in perf regression.

      If you have custom code inside this trigger then things become even worse. We have a feature where we track record changes in order to update external lucene search index.
      This code uses temp records and now guess what happens. … Yes these temp records are also triggering a call into GetDatabaseTableTriggerSetup and now you blow the stack.

      That’s a real issue for us and prevents us from upgrading our customers.


      1. Kamil Sacek says:

        Steffen, you can use the function IsTemporary to condition the code correctly… 😉 (it exists now even on the record type variables…)

        1. the signature is:
          GetDatabaseTableTriggerSetup(TableId : Integer;VAR OnDatabaseInsert : Boolean;VAR OnDatabaseModify : Boolean;VAR OnDatabaseDelete : Boolean;VAR OnDatabaseRename : Boolean)

          there is no reference to the original record inside this trigger.

          1. Kamil Sacek says:

            Ach, the setup, sorry, thought about the second triggers…

          2. I just wish someone from the team could comment on this.

          3. still noone from navteam here to comment on this`?

          4. says:

            Steffen, did you contact our support team about this?

          5. navteam says:

            @Steffen Forkmann: Sorry for the delay in getting back to you on this! The return value of the trigger GetDatabaseTableTriggerSetup is cached for each table ID in memory for each session, so you should only see one call to this C/AL method per table. Apparently you are seeing something different. In order to get your situation handled properly, please go through the standard support channel, and provide sample code showing the behavior you are seeing.

          6. Yes we reported the thing and the first support engineer was able to reproduce.
            It’s now escalating…

          7. says:

            Thanks Steffen

  2. AJ Ansari says:


    I can’t seem to locate “Copy-UpdateFilesToBatchDirectory.ps1” in the CU package (exploded the main .exe as well as the compressed NAV installation media). Am I missing something? I have a copy of this from NAV 2015. Can I safely use this, or has something changed in this PowerShell script between 2015 and 2016?


    1. Per Mogensen says:

      I used the script from NAV 2015 and did a search and replace for 80 -> 90, that seems to work.

  3. guido robben says:

    I see installing hotfixes has become even more complex now! Why not make it possible to to install the msi ans not give the error “another version jada jada jada”.

  4. guido robben says:

    Would be nice to have a Connect page also. NAV 2015 is the max.

  5. Gert Lynge says:

    Regarding AJ Ansaris questing about “Copy-UpdateFilesToBatchDirectory.ps1” – take one from NAV 2015 and replace 80 with 90 in it. Then it seems to work.

    Another problem – the Microsoft Dynamics NAV Server console: “The Microsoft Dynamics NAV Server.msc” from the Danish packet (I have not tried the other languages) does not load. If I copy the one from the RTM version it works. Does anybody else see this?

    Gert Lynge

    1. RadoA says:

      MMC: the same problem with W1 version (RTM version was installed, the files updated from CU1)

      1. RadoA says:

        P.S. we need to update registry because GUID has been changed for 90 version

        1. Gert Lynge says:

          RadoA: Can You clarify Your comment regarding registry?
          – Do You mean that something needs changing in the registry to make the MMC work? What should be changed? (I’ve also installed RTM and updated to CU1 using the Copy-UpdateFilesToBatchDirectory.ps1-method).
          – Or you mean that the Copy-UpdateFilesToBatchDirectory.ps1-method is not working for updating NAV 2015 to NAV 2016 (because I am aware of that :-). I only use it to update installation with CUs and within same major version)

          1. RadoA says:

            Sorry for unclear answer.
            I’ve changed the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{BA484C42-ED9A-4bc1-925F-23E64E686FCF} (last char from E to F).

    2. AJ Ansari says:

      Hi Greg,

      That’s what I ended up doing, and I too got the MMC error with NA. I tried using the Repair option, but forgot that it uses the files from the original installation folder. Long story short, my best luck with uninstalling and reinstalling NAV, while leaving the DB intact (and of course, importing and compiling the objects in the Application folder.

      1. Gert Lynge says:

        Ok – now I get it :-).
        I guess it was needed to fix the problem solved by platform hotfix id 375957: Dynamics NAV 2016 overwrites Dynamics NAV 2015 MMC controls.
        Luckily the MMC has its own install-setting in the setup, so it is quite easy to remove that component (with the RTM setup) and install it again (with the CU1 setup).
        That seems to solve the problem.
        My Christmas wish this year is that MS makes it easier and faster to platform upgrade using the installer. I wish for an platform upgrade-button 🙂

  6. guido robben says:

    PasteIsValid Bug is still present in this build

    1. guido robben says:

      Can the NAVTEAM confirm this?

      1. says:

        Hi Guido, not sure what you mean? Did you log a support case that still not is fixed or are you talking about something else?

  7. AJ Ansari says:

    PS, can you please confirm if the NAV 2016 image on the Azure gallery has been updated to CU1 as well?

    1. AJ Ansari says:

      For anyone wondering, the answer is ‘not yet.’ It’s still running the first RTW/RTM build.

      1. says:

        It is there, are you still having issues?

  8. Juanan says:

    Hi Nav Team Blog, cannot design objects in CU1 Spanish version because: “ShortCutKey value can’t be Ctrl+May+K. Enter a valid key combination’.
    It happen when click design any object or design table or report and press F9. If your language is English then there is no problem.
    Release version works right.
    Thank you

    1. navteam says:

      Hello Juanan,
      This issue was mentioned in the release notes for Dynamics NAV 2016. If you still see errors after upgrading to cumulative update 1, then use the same workaround: Delete the fin.zup file and then, in the development environment, change the language to English (United States). The default location of the fin.zup file is C:\users\\AppData\Roaming.

      In general, we recommend that you set the language to English (United States) when you work in the development environment, especially if you work in a multilanguage-enabled solution.

  9. olivier says:

    How can we know which files are needed for the ClickOnce/Windows Client or, similar, which files can be deleted from the RoleTailored Client folder (e.g. the files only needed for development) ? Do we need to install Windows Client seperately or are there other ways to know ?

    1. navteam says:


      There is a Windows PowerShell script for this on the product media for Cumulative Update 1 in the \WindowsPowerShellScripts\Cloud\NAVAdministration\ClickOnce\ folder. The file name of the script is Copy-ClientFilesToApplicationFilesDirectory.ps1.

      We hope this answers your question.

  10. Tino Ruijs says:

    Hi, I have this strange problems with the cu1-client. On some pc’s/servers it crashes before it opens.
    I’ve described the problem on mibuso in the following post:
    Does this problem sound familiar?

    1. navteam says:

      Hello Tino,
      This is a known issue for the Dynamics NAV Windows client and OneNote 2010. The next cumulative update will include a fix for the problem. Until then, we recommend that you uninstall OneNote 2010 from the client computer, or you can upgrade to a later version of OneNote, of course.

      1. Oli B says:

        I have the same problem. The NAV Client 2016 doesn´t start. Same if I try to run the tables via the Develepor Environment. No chance.
        But I have the OneNote Version 2013. I really need help here…

        1. navteam says:

          Hello Oli,

          Please contact our usual support channel so that you can get the right assistance.

      2. Tino Ruijs says:

        Thanks for the solution! It’s fixed now. Could you point me to the place where I can find the “known issues”?

        1. Tino Ruijs says:

          Sorry for using this site to test my gravatar. 🙂

Skip to main content