Lync 2013 / SfB 2015 Client Update – August 2018

Coming not a fortnight after our last update to the client, this one reeks of a “whoops” – and yes it does look like it could fix some amusing/embarrassing issues. The Office 2013-based client jumps 10 builds to 15.0.5059.1000 courtesy of Kb4032250.

What’s Fixed

  • Kb4346579 User’s display name that has special characters is shown with an emoticon in Skype for Business
  • Kb4346578 Can’t input messages until clicking participants list after taking control in screen sharing in Skype for Business 2015 (Lync 2013)
  • Kb4346577 The display name with an ampersand (&) is incorrectly shown in IM conversation window in Skype for Business 2015 (Lync 2013)

What’s New / Changed

Nothing documented.

Known Issues

Nothing documented.


It’s all good if you’ve been diligent in your patching.

If however your patching isn’t to current you’ll need to check you have *all* of these pre-req’s. The Office 2013 SP1 requirement still applies if you’re using Outlook 2010. (Lync 2013 in all of its flavours – e.g. Lync Basic – is still a component of Office 2013).



Current Version


Update for Office 2013 (KB3054853) (NOTE 1 BELOW) 1.0 9 June 2015
LyncHelpLoc (kb3191937) 1.0 22 May 2017
Microsoft Office 2013 Language Pack Service Pack 1 (KB2817427) 1.0 13 February 2014

NOTE1: “You do not have to apply update KB3054853 if you applied the April 14, 2015, update (KB2889923) or the May 12, 2015, security update (KB3039779) for Lync 2013 (Skype for Business)”


This is the client fix itself:

  • x86 (lync2013-kb4032250-fullfile-x86-glb.exe)
  • x64 (lync2013-kb4032250-fullfile-x64-glb.exe)


I have all the pre-req’s already installed, had exited the client before we started & was not prompted for a reboot.

Before / After



SfB 15.0.5049.1000 MSO 15.0.5031.1000 SfB 15.0.5059.1000 MSO 15.0.5031.1000
Before-15.0.5059.1000 After-15.0.5059.1000

Revision History

11th August 2018: This is the initial post.


– G.

Leave a Reply

Your email address will not be published.

... and please just confirm for me that you're not a bot first: Time limit is exhausted. Please reload the CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.