Lync 2013 / SfB 2015 Client Update – July 2015

The latest client update is out: the July 14, 2015, update for Lync 2013 (Skype for Business) (KB3054946).

This one takes the Office 2013-based Lync/SfB client from 15.0.4727.1001 to 15.0.4737.1001.

What’s Fixed

  • Kb3076504 CPU usage is reduced by emoticon animations that are active in multiple conversations in Skype for Business or Lync 2013
  • Kb3072756 Update UI to better display presence information in Skype for Business when calendar is set to out of office
  • Kb3072755 Chinese Contact Group name is displayed in garbled characters in Skype for Business or Lync 2013
  • Kb3072754 Update user interface for group contact counts in contact lists in Skype for Business or Lync 2013
  • Kb3072753 Active Directory contact’s name is changed to the phone number in the contact list of Skype for Business or Lync 2013
  • Kb3072752 Typed characters take a long time to display in the message input box in Skype for Business or Lync 2013
  • Kb3072751 Add the click-to-call feature for RCC-enabled users from the contact card in Skype for Business or Lync 2013
  • Kb3072750 Update changes the text label from participant code to Conference ID in Skype for Business or Lync 2013

What’s New / Changed

The presence indications of a signed-in user with OOF active change with this update. (Thanks Jeff Schertz for highlighting that).

Known Issues

  • Kb3051158 “Help isn’t working” error occurs when you open the “Skype for Business Help” window in Skype for Business
  • Kb3051516 “Copy” and “Select All’ menu items are disabled for the first instant message in a conversation in Skype for Business
  • Kb3051160 Cannot join meetings by using Lync 2010 after you install OneDrive for Business
  • Kb3053998 Memory leak occurs when you transfer a file that is larger than 5 megabytes (MB) in a conversation in Skype for Business


A few people have found their recent updates haven’t delivered as expected. Don’t forget *all* of the pre-req’s. The Office 2013 SP1 requirement still applies if you’re using Office 2010. (Lync 2013 in all of its flavours – e.g. Lync Basic – is still a component of Office 2013).



Current Version


Office 2013 SP1 (KB2817430)


1.0 18 February 2014
Update for Office 2013 (KB3054853)


1.0 9 June 2015
LyncHelpLoc (kb2889853) 1.0 13 April 2015
Microsoft Office 2013 Language Pack Service Pack 1 (KB2817427) 1.0 13 February 2014

NOTE1: “Before you install this update, you must install Microsoft Office 2013 Service Pack 1 (KB2817430)”.

NOTE2: “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-kb3054946-fullfile-x86-glb.exe)
  • x64 (lync2013-kb3054946-fullfile-x64-glb.exe)


As always, Tom’s great Hotfix installer does the work here. I threw several pre-req’s in a folder (even though I’m already patched as per NOTE2) largely to see what would happen. As per NOTE1 though, you “must” have Office 2013 SP1 installed before you start.


The mandatory pre-req LyncHelpLoc is still reporting “no product installed”, and I’ve had several colleagues report they’ve *never* seen it install. If you’ve had it install and can shed some light on the variation, please share that with us in the comments, and if you can think of why…


I have all the pre-req’s already installed, so a reboot was not required. The further behind your current client version is, the greater the likelihood you’ll need to reboot.

Before / After

I started this post on the home PC and finished several hundred kilometers and 4 hours later on the corporate laptop. That is by way of explaining why astute readers might notice the tiniest differences between the “before” and “after” shots.



SfB 15.0.4727.1001 MSO 15.0.4727.1001 SfB 15.0.4737.1000 MSO 15.0.4737.1001
20150714ClientUpdate-Before ClientUpdate-After2


Revision History

19th July 2015: This is the initial (incomplete) post

19th July 2015: Additional content. Hello from Canberra!


– 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.