Cumulative Update 05 for Microsoft Dynamics NAV 2018 has been released


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

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 http://support.microsoft.com/contactus/.

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 KB4171921 – Cumulative Update 05 for Microsoft Dynamics NAV 2018.

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.

Microsoft Dynamics NAV 2018 is also available from containers. Containers are a way to wrap up an application into its own isolated box, you can pull the cumulative update container from the Docker Hub.

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

Warning

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 can require a database upgrade.

Additional Information

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

AL Development for Dynamics 365 Business Central

For information about how to develop extensions for Dynamics 365 Business Central see AL Development for Dynamics 365 Business Central

For download of the corrected ModernDev AL VSIX extension see the download link.

Comments (11)

  1. Olegs Vasilesnikovs says:

    There are lot of objects where changed only date and version. Is it OK or something wrong with this update?

  2. There are lot of objects where changed only date and version. Is it OK, or something wrong with this update?

  3. Todd Scott says:

    Cannot use ModernDev AL VSIX extension. Getting FileLoadException on NewtonSoft.JSON Version 10.0.0.0 error after opening an AL project. Any one else?

  4. I am unable to use the ModernDev VSIX for this CU. I am getting several FileLoadException errors trying to load NewtonSoft.JSON Version 10.0.0.0. Is this a known issue?

    1. Getting the same error as todd.Greatscott… really trying to stick to using the ModernDev for all new development work, but need the product to work properly when these CU’s are released please… The following is an extract from the Output terminal window when starting up Visual Studio Code with the new VSIX:

      Unhandled Exception: System.AggregateException: One or more errors occurred. —> System.IO.FileLoadException: Could not load file or assembly ‘Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) —> System.IO.FileLoadException: Could not load file or assembly ‘Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
      — End of inner exception stack trace —
      at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.MessageWriter..ctor(Stream outputStream, IMessageSerializer messageSerializer)
      at Microsoft.Dynamics.Nav.EditorServices.Protocol.Channel.StdioServerChannel.Initialize(IMessageSerializer messageSerializer) in C:\Agent\_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Channel\StdioServerChannel.cs:line 27
      at Microsoft.Dynamics.Nav.EditorServices.Protocol.Channel.ChannelBase.Start(MessageProtocolType messageProtocolType, ProtocolEndpointCompletionSource completionSource) in C:\Agent\_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Channel\ChannelBase.cs:line 40
      at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.ProtocolEndpoint.d__4.MoveNext() in C:\Agent\_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\MessageProtocol\ProtocolEndpoint.cs:line 27
      — End of inner exception stack trace —
      at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
      at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
      at Prod.EditorServices.Host.Program.Main(String[] args) in C:\Agent\_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Host\Program.cs:line 103
      [Info – 07:28:09] Connection to server got closed. Server will restart.

      1. We are working a hotfix for it. For now the workaround is to set binding redirect to newVersion=9.0.0.0 in the C:\Users\\.vscode\extensions\Microsoft.al-0.12.20065\bin\Microsoft.Dynamics.Nav.EditorServices.Host.exe.config

        1. Great that fixed thanks.

        2. Is there a Revision history (changelog) for the VSIX? Looking at the Extension in VS Code the latest is shows is December 2017.
          December Update (CURRENT)

          Welcome to another installment of our development updates. We have the pleasure of announcing the following great features.

          1. Stanislaw Stempin says:

            We are not maintaining the changelog for CU releases. The fixed bugs can be found in the KB article for each CU – KB4171921 for CU5 as linked above.

  5. When will the image be available on Docker? docker pull microsoft/dynamics-nav:2018-cu5-gb returns Error response from daemon: manifest for microsoft/dynamics-nav:2018-cu5-gb not found

    1. FreddyDK says:

      Docker images are ready on the Docker hub now.

Skip to main content