Cumulative Update 24 for Microsoft Dynamics NAV 2013 has been released


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

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
  • DE – Germany
  • DK – Denmark
  • ES – Spain
  • FI – Finland
  • FR – France
  • IS – Iceland
  • IT – Italy
  • NA – North America
  • NL – Netherlands
  • NO – Norway
  • NZ – New Zealand
  • SE – Sweden
  • UK – United Kingdom

Where to find Cumulative Update 24

You can download the cumulative update from KB 3039828 – Cumulative Update 24 for Microsoft Dynamics NAV 2013 (Build 40118).

Additional Information

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

For a list of all hotfixes included in cumulative updates for this version, see the following CustomerSource and PartnerSource pages:

CustomerSource:

PartnerSource:

Comments (6)

  1. I had a look around, but there doesn't seem to be an easy way to get hold of the Application updates. I'd like to do this so the VCS I'm using can properly help with the merging.

    The only way to do it appears to laboriously traipse from one KB article to another, repeatedly, reiterating the rigmarole of begging for each one individually. Then tediously waiting for huge dumps to wade though for tiny stones.

    All in all it's very different from a git clone … and not in a good way!!

    And NO just the most recent is NOT enough. A good VCS, and there are several, will use the changes individually to automatically resolve updates that simple 3-way merge will completely fail over. Of course, this would work even better with each individual change recorded by itself … but despite any hopes (to be proven wrong) I may have I know Microsoft will never be able to do that. So I'd like to make do with all of the Cumulative Updates in sequence, but even that isn't easy.  

    But that's what I'm doing, it's taking days, Anyone have a better idea ?

  2. Jens Glathe says:

    Hi Robert,

    I'm doing the CU and release chaining since two years now. It has helped me a great deal, although it is tedious work every month (now for 3 branches, times two localizations (DE and W1)). I have tried to start as far back in history as I could find (NAV2.60). This is great for analysis and merge jobs. I would prefer a git fetch (or whatever is actually used, we're still in the Microsoft pond) for all the official releases, though.

    with best regards

    Jens

  3. Marko Huetter says:

    I tried x times. After push the button "request hotfix" there is this "funny" upps, page not found error. Am I the only one with this problem?

  4. Pallea says:

    Here is what I did:

    Switch to Private browsing then go go

    mbs.microsoft.com/partnersource

    Upper right corner where it says "Search this site"

    Just type

    Released Cumulative Updates for Microsoft Dynamics NAV 2013 (2013 R2 or 2015) and click on search

    You will get a list of available updates, click on the one you need

    Then the rest is business as usual (i hope, at least it was for me).

    Thanks

    Palle

  5. Marko Huetter says:

    Thanks @Pallea –> it works..

  6. @jens, That's what I'm aiming for on V7/7.1 and 8 anyway. At the time a nice way of fetching the Hotfixes from Navision A/S would have been good for 2.6-3.60, but at the time I don't think I was having to work with as much inline modification as now. (and I didn't even save the 2.50! But I did managed to get some even earlier versions at some point)

    Anyway, Microsoft are active on "Github" ( https://github.com/Microsoft ) and Visual studio links into GIT repositories so it doesn't look like too much to ask for this to be available in GIT too. As for a direct export from their source control; I would not expect it to be "clean enough" (whatever that might mean) for them to be happy releasing it, but that doesn't stop us hoping.

Skip to main content