Lync 2013 Enabling the Conversation Translator

Some of you may be wondering how to get the conversation translator functionality working now that you have upgraded to Lync 2013. Until there is an official release here is a quick fix. Copy the following text into a text editor and save as a .reg file. Then merge it into your registry and you should have the functionality back up and working like before. Make sure to restart Lync to affect the registry changes.

Windows Registry Editor Version 5.00

"Name"="Lync Conversation Translator"


[HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\Security\Trusted Sites]

[HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\Security\Trusted Sites\]



  1. One thing to note - it requires Silverlight, which doesn't run in the 64 bit version of the Lync client.

  2. I notice code posted to MSDN for a Lync 2013 update to the Conversation Translator, which I assume would run on Lync 64-bit as well - anyone got a link to a compiled exe for this?

    1. Hi Mike,

      I don't have a exe for this. It should be coming over the next few months as Lync 2013 goes GA. Look for an official release sometime next year.

      This is just a workaround till then.

  3. Hi Norman,

    A big question in my organization: Is there an ability to do translations on an internal system, so that the conversation is not sent out over the internet and translated by an external source? Our main concern is the leakage of private data. Would love some insite on if this is possible!


    1. Hi Nate,

      Not that I know of today. This could be something that is custom developed using the Lync API's if you have a translator engine to drive it like IM an Expert for instance

      A couple of notes on the Bing service though. It doesn't store the data you send it and you can also alter the reg file to ensure it only uses https to communicate with the secure service by removing the "http"=dword:00000001". This then only allow the secure version into your trusted sites.

    2. Hi,
      Removing the http entry seems to break the add-in. I tried changing the internal and external URLs to use an https: address but that just fails completely. What else am I missing to ensure that it uses HTTPS?



Note: Only a member of this blog may post a comment.