Installing Microsoft Dynamics NAV 2013 R2 side-by-side with Microsoft Dynamics NAV 2013

A year after Microsoft Dynamics NAV 2013 released, we released a new version of it, Microsoft Dynamics NAV 2013 R2. They share common files, so if you install both versions on the same computer, then they will try to use the same resources, and so you run into problems. This really means that you cannot install the two versions side-by-side.

We resolved this issue with the fix in KB 2907588 for Microsoft Dynamics NAV 2013 R2 (build number higher than 35850). But there is some manual work that you have to do to apply the fix fully.
Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 use the same Windows registry entries to describe which interface and libraries to use. With the described fix, Microsoft Dynamics NAV 2013 R2 can use new registry entries, but simply installing the hotfix does not generate the registry entries. Windows registry settings are created by installation programs, but creating a new installer for every language is out of scope for hotfix releases.

To get Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 working side-by-side, you can choose to modify some of the existing entries in the Windows registry. But the easiest way is to delete the existing registry entries and create new entries in the registry.

Depending on the specific machine architecture, your registry settings can include the following entries:
" HKEY_CLASSES_ROOT\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.1"
" HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08}"
" HKEY_CLASSES_ROOT \Interface\{59521B62-D441-47E6-8224-A07203686BA2}"
" HKEY_CLASSES_ROOT \Wow6432Node\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.1"
" HKEY_CLASSES_ROOT \Wow6432Node\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08}"
" HKEY_CLASSES_ROOT \Wow6432Node\Interface\{59521B62-D441-47E6-8224-A07203686BA2}"

Remove the entries.

To create new correct windows registry entries, open the Command Prompt as an administrator, and then, run the RegAsm.exe /register Microsoft.Dynamics.Nav.Client.WinForms.dll /tlb command for each of the two products.

For example, for Microsoft Dynamics NAV 2013, enter the following command:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /register "C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Microsoft.Dynamics.Nav.Client.WinForms.dll" /tlb

And for Microsoft Dynamics NAV 2013 R2, enter the following command:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /register "C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.WinForms.dll" /tlb

When you have run those two commands on a 32-bit computer, the following entries exist in the registry:

Microsoft Dynamics NAV 2013:
HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)

Microsoft Dynamics NAV 2013 R2:
HKEY_CLASSES_ROOT\Interface\{59521B62-D441-47E6-8224-A07203686BA2} (where \TypeLib\Version == 7.1)

And for 64-bits computers:
Microsoft Dynamics NAV 2013:
HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)
HKEY_CLASSES_ROOT\Wow6432Node\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)

Microsoft Dynamics NAV 2013 R2:
HKEY_CLASSES_ROOT\Interface\{59521B62-D441-47E6-8224-A07203686BA2}(where \TypeLib\Version == 7.1)
HKEY_CLASSES_ROOT\Wow6432Node\Interface\{59521B62-D441-47E6-8224-A07203686BA2}(where \TypeLib\Version == 7.1)

If you have applied everything correctly, then Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 will now both be able to run on the computer.

If you have only Microsoft Dynamics NAV 2013 R2 installed and any object run from dev env opens new RTC instance, then you can apply the same registry modify (related to 7.1) and issue will be resolved.

Attached is PowerShell script does all job.
BTW: If Microsoft Dynamics NAV 2013 R2 is installed alone, you can also use script - it will fix registries. 


Best regards,

Gedas Busniauskas and Jorge Alberto Torres from the Dynamics NAV team

Comments (20)

  1. Johannes Sebastian at says:

    Very nice guide, all though a litte late.

    But please, let's learn something from this:

    As a NAV developer it is paramount that I'm able to work with all recent version of NAV.

    Having my Workstation partially disabled by a new NAV version, is not a proper way for MS to support the developers. Different NAV Development Environments should be able to exist side by side, because that really is how a NAV partner/ISV operates.

  2. Why not... says:

    With every new version of NAV, release a (hyper v) VM of the previous version and make it avaivale via partnersource UNTIL the side-by-side fix is working.  This will helps devs continue working without issue meanwhile giving the Dynamics NAV Team a reasonable amount of time to solve the side-by-side install woes…

  3. Sebastiaan Lubbers says:

    Hear, hear. Lets finally kill the need for HKEY_CLASSES_ROOTDYNAMICSNAVShellOpenCommand with

    (Default)   C:Program Files (x86)Microsoft Dynamics NAV60RoleTailored ClientMicrosoft.Dynamics.Nav.Client.exe "%1"

    (Default)   C:Program Files (x86)Microsoft Dynamics NAV70RoleTailored ClientMicrosoft.Dynamics.Nav.Client.exe -protocolhandler "%1"

    (Default)   C:Program Files (x86)Microsoft Dynamics NAV71RoleTailored ClientMicrosoft.Dynamics.Nav.Client.exe -protocolhandler "%1"

    P.S. I have been running 70 and 71 side-by-side on my machine from the first release and had no problems, except for not being able to use the 70 service-admin.

  4. Capone says:

    I agree with former speakers.

    I wish Microsoft could have a more partner perspective.

    These days we need have several installations of both different versions (2009|2009 R2|2013|2013 R2) and different builds.

    It would be great if you could write a tutorial on how to handle this. For instance if I develop in 2013 R2 build XXXX and press run in the developer I want it to be run with the client with the same build.  Especially now with all the update rollups

  5. Ryan Cairns says:

    I ran the powershell script and checked it updated all the relevant registry entries. The multiple instances of the 2013 R2 client opening is fixed. However when I run an object from the 2013 DEV environment it still tries to open 2013 R2.

    Any ideas how I proceed?

  6. Ryan Cairns says:

    I think my problem is something to do with having the Protocol Handler work around. What should I now have under




  7. Ryan Cairns says:

    Ignore my previous comments – I applied the latest Hotfix Rollup to 2013 which fixed the problem. I had previously only applied hotfix rollups to 2013 R2. You might want to update the article to reflect what build 2013 needs to be running with to get this fix working properly.

  8. Abram says:

    Still running into issues after installing the latest roll-ups for 2013 and 2013 R2, then applying the PowerShell script.  The admin tool, debugging, etc… is working – however we have the clients for 2013 and R2 on the same machine and now when we try to export to Excel (ie, print and send to Excel) we get the version mismatch error, then a blank Excel spreadsheet.  Is there another registry entry to fix the Excel interaction?  The print and send to Word still works, so it appears it is just the Excel interface that isn't working.

    Any suggestions?

  9. Procedure says:

    What is the right procedure.

    Install first the Dynamics NAV 2013 and then the Dynamics NAV 2013, or the opposite?

  10. Joerg Renz says:

    I have the same problem like Abram's post (send to excel).

    Is there any solution to fix this problem?

  11. Tomas Dissing says:

    I have the R2 installed and it Works OK with Visual Studio 2013 after the above fix – thanks. When I try to run the 2013(7.0) Setup.exe nothing happens. Nothing in the tasklist at all, nothing in the eventviewer. Any experience anyone ? (installing the 2013 after the 2013R2). Running Win8.1Pro

  12. Alexandros G. Papaspyridis says:

    Thanks for the post Dynamics NAV Team.I have tried it in a real implementation and it is working well.I would like to ask you if this solution is supported by Micrososft or it is provided as is? The client is public sector, so they have asked us.

    Kind Regards

  13. Anil Pardeshi says:


    Can you please post similar for Nav 2013 and Nav 2015 together. It has got same issue.



  14. Rafal says:

    The same mess with NAV 2015. I know Microsoft want force us to using separate Azure virtual machines for every NAV instance, but in development enviroment it's not possible.

    Microsoft! Please do something with that, and give us quick solution for this problem.

  15. Rafal says:

    If you have same issue with NAV 2015 and 2013 you can try following solution:…/viewtopic.php

    (it is not fully tested)

  16. Defiant701 says:

    Guess it's the same solution for 2015 & 2013R2. It's no problem to identify the GUID for the TypeLib with ORCA, but I wasn't able to identify the GUID of the interface entries. Could you please update this topic with the HKEY_CLASSES_ROOTInterface{GUID}(where TypeLibVersion == 8.0).

  17. Miguel Costa says:


    Thanks for the script.

    I had the 2013 R2 installed, but I needed 2013 to manage migrations from 2009 and nav4.

    After I run your script, I cannot export  objects .fob from older versions.


    Microsoft Dynamics NAV Classic


    The object file cannot be used with this version of the program.




    Do you know an easy way to undo your script?


  18. Miguel Costa says:


    Please ignore my last post.

    It is not happening anymore.It was some strange issue with the file itself that I was trying to write over.


  19. same issue with nav 2015 and nav 2016. is there a fix available (registry change) ?

    1. Geovanny says:

      Yes i’m running in to the same issue with UK CU1 and NA CU5 NAV 2016 version.
      Please advise, thank you.

Skip to main content